30121709 Alarm Clearing

OptiX OSN 9500 Alarms and Performance Events Reference Contents

Issue 01 (2007-12-31) Huawei Technologies Proprietary i

Contents

3 Alarm Clearing ...........................................................................................................................3-1 3.1 ALM_ALS ....................................................................................................................................................3-2 3.2 APS_FAIL.....................................................................................................................................................3-3 3.3 APS_INDI .....................................................................................................................................................3-4 3.4 APS_MANUAL_STOP ................................................................................................................................3-6 3.5 AU_AIS.........................................................................................................................................................3-7 3.6 AU_CMM .....................................................................................................................................................3-8 3.7 AU_LOP......................................................................................................................................................3-10 3.8 B1_EXC......................................................................................................................................................3-11 3.9 B1_SD.........................................................................................................................................................3-13 3.10 B1B_EXC .................................................................................................................................................3-15 3.11 B2_EXC ....................................................................................................................................................3-16 3.12 B2_SD.......................................................................................................................................................3-18 3.13 B3_EXC....................................................................................................................................................3-20 3.14 B3_EXC_VC3...........................................................................................................................................3-23 3.15 B3_SD.......................................................................................................................................................3-24 3.16 B3_SD_VC3 .............................................................................................................................................3-27 3.17 BD_NOT_INSTALLED ...........................................................................................................................3-29 3.18 BD_STATUS.............................................................................................................................................3-30 3.19 BDID_ERROR..........................................................................................................................................3-31 3.20 BIOS_STATUS .........................................................................................................................................3-32 3.21 BOOTROM_BAD ....................................................................................................................................3-33 3.22 BUS_ERR .................................................................................................................................................3-34 3.23 C2_VCAIS ................................................................................................................................................3-36 3.24 CAN_ALM ...............................................................................................................................................3-37 3.25 COM_EPLD_FAULT................................................................................................................................3-38 3.26 COMMUN_FAIL......................................................................................................................................3-39 3.27 CPLD_FAIL..............................................................................................................................................3-40 3.28 DBMS_ERROR ........................................................................................................................................3-41 3.29 DBMS_PROTECT_MODE ......................................................................................................................3-42 3.30 DLAG_PROTECT_FAIL .........................................................................................................................3-43 3.31 DUPLEX_ERROR....................................................................................................................................3-46

Contents OptiX OSN 9500

Alarms and Performance Events Reference

ii Huawei Technologies Proprietary Issue 01 (2007-12-31)

3.32 ETH_LOS .................................................................................................................................................3-47 3.33 EX_ETHOAM_CC_LOS..........................................................................................................................3-48 3.34 EX_ETHOAM_MPID_CNFLCT .............................................................................................................3-50 3.35 EXT_SYNC_LOS.....................................................................................................................................3-51 3.36 FAN_FAIL ................................................................................................................................................3-53 3.37 FAN_PWR_ALM......................................................................................................................................3-54 3.38 FIFO_OVERFLOW..................................................................................................................................3-55 3.39 FPGA_ABN ..............................................................................................................................................3-56 3.40 HARD_BAD.............................................................................................................................................3-57 3.41 HP_CROSSTR..........................................................................................................................................3-58 3.42 HDLC_FAIL .............................................................................................................................................3-60 3.43 HP_CDI.....................................................................................................................................................3-61 3.44 HP_LOM...................................................................................................................................................3-62 3.45 HP_PDI .....................................................................................................................................................3-63 3.46 HP_RDI.....................................................................................................................................................3-64 3.47 HP_REI .....................................................................................................................................................3-66 3.48 HP_SDI .....................................................................................................................................................3-67 3.49 HP_SLM ...................................................................................................................................................3-68 3.50 HP_TIM ....................................................................................................................................................3-69 3.51 HP_UNEQ.................................................................................................................................................3-70 3.52 HPAD_CROSSTR.....................................................................................................................................3-72 3.53 IN_PWR_ABN .........................................................................................................................................3-73 3.54 IN_PWR_FAIL .........................................................................................................................................3-74 3.55 IN_PWR_HIGH........................................................................................................................................3-76 3.56 IN_PWR_LOW.........................................................................................................................................3-77 3.57 INIT_FAILURE ........................................................................................................................................3-78 3.58 J0_MM......................................................................................................................................................3-79 3.59 K1_K2_M .................................................................................................................................................3-80 3.60 K2_M ........................................................................................................................................................3-81 3.61 L_S_ERROR.............................................................................................................................................3-82 3.62 LASER_MOD_ERR .................................................................................................................................3-83 3.63 LASER_NOT_EXIST...............................................................................................................................3-84 3.64 LAG_PORT_FAIL ....................................................................................................................................3-85 3.65 LAG_VC_PORT_FAIL.............................................................................................................................3-87 3.66 LCAS_FOPR.............................................................................................................................................3-89 3.67 LCAS_FOPT.............................................................................................................................................3-90 3.68 LCAS_PLCR.............................................................................................................................................3-91 3.69 LCAS_ PLCT............................................................................................................................................3-93 3.70 LCAS_TLCR ............................................................................................................................................3-94 3.71 LCAS_TLCT.............................................................................................................................................3-96 3.72 LINK_ERR ...............................................................................................................................................3-97 3.73 LASER_SHUT..........................................................................................................................................3-98


Issue 01 (2007-12-31) Huawei Technologies Proprietary iii

3.74 LOOP_ALM .............................................................................................................................................3-99 3.75 LP_UNEQ_VC3 .....................................................................................................................................3-101 3.76 LP_RDI_VC3..........................................................................................................................................3-102 3.77 LP_SLM_VC3 ........................................................................................................................................3-103 3.78 LP_TIM_VC3 .........................................................................................................................................3-104 3.79 LSR_COOL_ALM..................................................................................................................................3-106 3.80 LSR_NO_FITED ....................................................................................................................................3-107 3.81 LSR_WILL_DIE.....................................................................................................................................3-108 3.82 LTI...........................................................................................................................................................3-109 3.83 M_S_SW.................................................................................................................................................3-110 3.84 MASTER_ERR....................................................................................................................................... 3-111 3.85 MBUS_OFFLINE ...................................................................................................................................3-112 3.86 MBUS_SERIAL .....................................................................................................................................3-113 3.87 MBUS_UPDATE_FAIL..........................................................................................................................3-114 3.88 MS_AIS ..................................................................................................................................................3-115 3.89 MS_APS_INDI_EX................................................................................................................................3-116 3.90 MS_CROSSTR .......................................................................................................................................3-118 3.91 MS_RDI ..................................................................................................................................................3-119 3.92 MS_REI ..................................................................................................................................................3-121 3.93 MSAD_CROSSTR .................................................................................................................................3-122 3.94 MSSW_DIFFERENT..............................................................................................................................3-123 3.95 NEBD_XC_DIF......................................................................................................................................3-125 3.96 NESF_LOST...........................................................................................................................................3-126 3.97 NESTATE_INSTALL..............................................................................................................................3-127 3.98 NO_BD_PARA .......................................................................................................................................3-128 3.99 NO_BD_SOFT........................................................................................................................................3-129 3.100 NO_LSR_PARA_FILE .........................................................................................................................3-130 3.101 NODEID_MM ......................................................................................................................................3-131 3.102 OH_ERR ...............................................................................................................................................3-132 3.103 OH_LOOP.............................................................................................................................................3-133 3.104 OOL ......................................................................................................................................................3-134 3.105 OTH_BD_STATUS...............................................................................................................................3-135 3.106 OTH_HARD_FAIL...............................................................................................................................3-136 3.107 OUT_PWR_ABN .................................................................................................................................3-137 3.108 PATCH_ERR.........................................................................................................................................3-138 3.109 PATCH_NOT_CONFIRM ....................................................................................................................3-138 3.110 PATCHFILE_NOTEXIST.....................................................................................................................3-139 3.111 PAUSE_ERROR ...................................................................................................................................3-140 3.112 POWER_ALM ......................................................................................................................................3-141 3.113 POWER_FAIL ......................................................................................................................................3-142 3.114 POWER_SWITCH................................................................................................................................3-143 3.115 PUM_BCM_ALM.................................................................................................................................3-144

Contents OptiX OSN 9500


iv Huawei Technologies Proprietary Issue 01 (2007-12-31)

3.116 PUM_TEM_ALM.................................................................................................................................3-146 3.117 PUMP_COOL_EXC .............................................................................................................................3-147 3.118 PWR_LOW ...........................................................................................................................................3-148 3.119 PWR_LOW_PROTECTED ..................................................................................................................3-149 3.120 PWR_MAJ_ALM .................................................................................................................................3-149 3.121 PWR_OVER .........................................................................................................................................3-151 3.122 R_LOC..................................................................................................................................................3-152 3.123 R_LOF ..................................................................................................................................................3-153 3.124 R_LOS ..................................................................................................................................................3-154 3.125 R_OOF..................................................................................................................................................3-156 3.126 RELAY_ALARM .................................................................................................................................3-157 3.127 RELAY_ALARM_CRITICAL .............................................................................................................3-158 3.128 RELAY_ALARM_IGNORE ................................................................................................................3-159 3.129 RELAY_ALARM_MAJOR..................................................................................................................3-160 3.130 RELAY_ALARM_MINOR ..................................................................................................................3-161 3.131 RS_CROSSTR ......................................................................................................................................3-162 3.132 RTC_FAIL.............................................................................................................................................3-164 3.133 S1_SYN_CHANGE..............................................................................................................................3-165 3.134 SCC_CHANGE.....................................................................................................................................3-166 3.135 SECU_ALM..........................................................................................................................................3-167 3.136 SLAVE_BAD........................................................................................................................................3-168 3.137 SLAVE_WORKING .............................................................................................................................3-169 3.138 SNCP_FAIL ..........................................................................................................................................3-171 3.139 SPEED_ERROR ...................................................................................................................................3-172 3.140 SWITCH_DISABLE.............................................................................................................................3-172 3.141 SYN_BAD ............................................................................................................................................3-173 3.142 SYNC_C_LOS......................................................................................................................................3-174 3.143 SYNC_F_M_SWITCH .........................................................................................................................3-175 3.144 SYNC_FAIL .........................................................................................................................................3-177 3.145 SYNC_LOCKOFF................................................................................................................................3-178 3.146 T_LOSEX .............................................................................................................................................3-179 3.147 TEM_HA...............................................................................................................................................3-180 3.148 TEM_LA...............................................................................................................................................3-181 3.149 TEMP_ALARM....................................................................................................................................3-182 3.150 TEMP_MAJ_ALM ...............................................................................................................................3-183 3.151 TEMP_MIN_ALM................................................................................................................................3-184 3.152 TEMP_OVER .......................................................................................................................................3-185 3.153 TEST_STATUS.....................................................................................................................................3-187 3.154 TF ..........................................................................................................................................................3-187 3.155 TMP_DIFF_OVER ...............................................................................................................................3-188 3.156 TR_LOC................................................................................................................................................3-189 3.157 TU_AIS_VC3........................................................................................................................................3-190


Issue 01 (2007-12-31) Huawei Technologies Proprietary v

3.158 TU_LOP_VC3 ......................................................................................................................................3-192 3.159 W_OFFLINE.........................................................................................................................................3-194 3.160 W_R_FAIL............................................................................................................................................3-195 3.161 WRG_BD_TYPE..................................................................................................................................3-196 3.162 XC_UNSWITCH ..................................................................................................................................3-197

Tables OptiX OSN 9500


vi Huawei Technologies Proprietary Issue 01 (2007-12-31)

Tables

Table 3-1 Alarms that may cause the AU_AIS alarm .........................................................................................3-8

OptiX OSN 9500 Alarms and Performance Events Reference 3 Alarm Clearing

Issue 01 (2007-12-31) Huawei Technologies Proprietary 3-1

3 Alarm Clearing

About This Chapter

Alarm handling is essential for the maintenance of the OptiX OSN 9500. An effective analysis of alarms is the key to clear them. Therefore, you need to locate the causes of the alarms first and then clear them.

Based on the generation and handling methods, the alarms are classified into equipment alarm, communication alarm, QoS alarm, processing alarm, environment alarm and security alarm.

This chapter describes the causes and handling methods of common alarms.

The alarm level is the default one.

3 Alarm Clearing OptiX OSN 9500


3-2 Huawei Technologies Proprietary Issue 01 (2007-12-31)

3.1 ALM_ALS

Description The ALM_ALS is an alarm of automatic laser shutdown (ALS). If the ALS function is enabled, the system automatically shuts down the laser in the transmit direction of the optical interface that receives an R_LOS alarm, and at the same time reports the ALM_AIS alarm. When the R_LOS alarm is cleared, the system automatically turns on the laser in the transmit direction of the optical interface, and at the same time the ALM_ALS alarm is cleared.

Attribute

Alarm Severity Alarm Type

Minor Equipment alarm

Parameters When you view an alarm on the T2000, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table.

Name Meaning

Parameter 1 Indicates the optical interface number.

Impact on System For the optical interface that reports the ALM_ALS alarm, the laser in the transmit direction is shut down, and the services in this direction fail.

Possible Causes When the ALS function is enabled, an R_LOS alarm occurs in the receive direction of the optical interface.

Handling Procedure Step 1 Confirm the relevant optical interface according to the alarm parameters.

Step 2 Confirm whether the ALS function should be enabled for the optical interface. If the ALS function need not be enabled for the optical interface, manually disable the ALS function. In this case, the laser in the transmit direction of the optical interface is automatically turned on, and the ALM_ALS alarm is cleared.



Step 3 If the ALS function should be enabled for the optical interface, handle the R_LOS alarm first. When the R_LOS alarm of the optical interface is cleared, the laser in the transmit direction of the optical interface is automatically turned on, and the ALM_ALS alarm is cleared.

----End

Related Information By default, the ALS function is disabled for the OptiX OSN 9500.

3.2 APS_FAIL

Description The APS_FAIL is an indication alarm of APS protection switching failure. This alarm occurs when the MSP switching fails.

Attribute


Major Communication alarm


Name Meaning

Parameter 1 Indicates the type of the MSP group in which protection switching occurs.

0x01: Linear MSP group 0x02: Ring MSP group

Parameter 2 Indicates the MSP group ID.

Impact on System When the APS_FAIL alarm occurs, the MSP switching fails. For a linear MSP or a two-fiber ring MSP, if a fiber cut or another fault occurs at this time, the services are interrupted.

Possible Causes The possible causes of the APS_FAIL alarm are as follows:




The MSP configuration parameters are incorrect. The MSP configuration is lost.

Handling Procedure Step 1 Make sure that the networkwide MSP configuration is correct. For a ring MSP, check the

fiber connections in the east and west directions. For a linear MSP, check the working and protection fiber connections, or check the MSP switching modes at the two ends. After modifying the incorrect configuration, check whether the alarm is cleared.

Step 2 Make sure that the networkwide APS protocol works properly. Stop the protocol, and then restart it to check whether the alarm is cleared.

----End

Related Information None

3.3 APS_INDI

Description The APS_INDI is an alarm indicating the APS state. This alarm occurs when the MSP is in the switching state.

Attribute




Name Meaning






Impact on System The APS_INDI alarm indicates the occurrence of a fiber cut or a terminal node failure,

which triggers the MSP switching. For a two-fiber ring MSP or a linear MSP, if a fiber cut or another fault occurs after the

occurrence of this alarm, the services are interrupted.

Possible Causes The possible causes of the APS_INDI alarm are as follows:

An external command, including manual switching, forced switching, and exercise switching, is issued.

After the R_LOS, R_LOF, MS_AIS, B2_EXC, or B2_SD alarm occurs, the MSP group changes to the switching state.

The service board is faulty. The cross-connect board is faulty.

Handling Procedure Step 1 On the T2000, view Parameter 1 and Parameter 2 of this alarm to confirm the type and ID of

the protection group in which this alarm is generated.

Step 2 Check whether the MSP is in a state of manual switching, forced switching, or lockout of switching. If the MSP is in a switching state, clear the switching and then observe whether the alarm is cleared.

Step 3 To check whether the MSP is in the automatic switching state, do as follows:

Handle the R_LOS, R_LOF, MS_AIS, B2_EXC or B2_SD alarm reported by the equipment. When these alarms are cleared, wait for the MSP switching to be automatically restored to the normal state, and then check whether the APS_INDI alarm is cleared.

Make sure that the service board of the MSP is not faulty. Replace the relevant service board and then check whether the alarm is cleared.

Make sure that the cross-connect board of the MSP is not faulty. Replace the relevant cross-connect board and then check whether the alarm is cleared.

----End

Related Information For the 1+1 single-ended non-revertive linear MSP, the APS_INDI alarm is generated when the protection switching occurs. When the optical path returns to normal, the service is not automatically switched back to the working path, and the APS_INDI alarm persists. In this case, manually switch the service from the protection path to the working path. After successful manual switching, the APS_INDI alarm is cleared.




3.4 APS_MANUAL_STOP

Description The APS_MANU_STOP is an alarm indicating that the MSP protocol is manually stopped.

Attribute


Minor Processing alarm


Name Meaning

Parameter 1 Indicates the MSP group type. 0x01: Linear MSP group 0x02: Ring MSP group


Impact on System The MSP switching protocol of the corresponding MSP group fails to function. Accordingly, the MSP fails.

Possible Causes The MSP protocol of the corresponding MSP group is manually stopped.

Handling Procedure Step 1 View on the T2000 and confirm the MSP subnet where the protocol is stopped.

Step 2 Restart the MSP protocol of the protection group, and the APS_MANI_STOP alarm is cleared.

----End




3.5 AU_AIS

Description The AU_AIS is the administrative unit (AU) alarm indication. When the pointer value received on the receive side of the local optical interface is all "1"s, the AU_AIS alarm is reported.

Attribute




Name Meaning

Parameter 1 Indicates the actual optical interface number of the board.

Parameter 2, Parameter 3

Indicates the AU-4 path number. Parameter 2 is the higher byte, and Parameter 3 is the lower byte. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the AU_AIS alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System When the AU_AIS alarm occurs, the path-level services are interrupted if the network is

not protected. In this case, the AU-AIS alarm occurs at the downstream station.

Possible Causes The possible causes of the AU_AIS alarm are as follows:

A higher-level alarm, such as the R_LOS, R_LOF, R_OOF, B1_EXC or B2_EXC, occurs in the system.

The alarms shown in Table 3-1 occur at the upstream station. The AIS signal is transmitted at the opposite station. The transmit unit (such as cross-connect boards or line boards) at the opposite station is

faulty. The receive unit at the local station is faulty.




Handling Procedure Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, R_OOF, B1_EXC or

B2_EXC, is detected on the T2000 at the local station. If yes, take priority to clear it, and then check whether the AU_AIS alarm is cleared.

Step 2 If the alarm persists, check whether any alarm shown in Table 3-1 occurs at the upstream station. If yes, clear it, and then check whether the AU_AIS alarm is cleared.

Step 3 Perform optical interface inloop on the relevant line board at the opposite station.

Step 4 After the inloop operation, if the AU_AIS alarm occurs at the opposite station, the AU_AIS alarm at the local station comes from the opposite station.

Repeat step 3 to locate the upstream station that first generates and transmits the AU-AIS alarm. Check whether any alarm shown in Table 3-1 occurs on the service source board of the local station. If yes, clear it, and then check whether the AU-AIS alarm is cleared at the local station.

If the alarm persists, replace the transmit board at the station that first generates the AU_AIS alarm.

Step 5 After the inloop operation, if the AU-AIS alarm does not occurs at the opposite station, the receive board at the local station is faulty. In this case, replace the receive board at the local station.

----End

Related Information

Table 3-1 Alarms that may cause the AU_AIS alarm

R_LOS R_LOF R_OOF

MS_AIS B1_EXC B1_SD

B2_EXC B2_SD AU_LOP

B3_EXC B3_SD HP_TIM

HP_LOM HP_SLM HP_UNEQ

3.6 AU_CMM

Description The AU_CMM is an alarm of pointer concatenation mismatch. This alarm indicates that the rates of the configured services and the actual services are the same but the service types are different.



Attribute


Major Processing alarm


Name Meaning



Indicates the AU-4 path number. Parameter 2 is the higher byte, and Parameter 3 is the lower byte. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the AU_CMM alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System If the configured services are concatenation services and the actually transmitted services

are non-concatenation services, performance of paths except path 1 cannot be monitored. The services, however, are not affected.

If the configured services are non-concatenation services and the actually transmitted services are concatenation services, the services are interrupted.

Possible Causes The type of services transmitted from the opposite station is incorrect. The type of services configured at the local station is incorrect. Fibers are incorrectly connected.

Handling Procedure Step 1 According to the alarm parameters, confirm the optical interface that reports the AU_CMM

alarm and the corresponding AU-4 path.

Step 2 Check whether the service type configured in the AU-4 path is consistent with the planned service type. If not, reconfigure the services at the local station.

Step 3 Modify the type of services transmitted from the upstream, and then check whether the AU_CMM alarm is cleared.

Step 4 If the alarm persists, check whether the corresponding fibers are incorrectly connected.

----End





3.7 AU_LOP

Description The AU_LOP is an alarm indicating the loss of AU pointer. This alarm occurs when the local optical interface receives the NDF or invalid pointers in eight consecutive frames.

Attribute




Name Meaning



Indicates the AU-4 path number. Parameter 2 is the higher byte, and Parameter 3 is the lower byte. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, and Parameter 3 = 0x01. In this case, the AU_LOP alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System If the SNCP is provided, the AU_LOP alarm triggers the SNCP switching. If the SNCP is not provided, the payload position cannot be determined, and as a result

the services are interrupted.

Possible Causes The local station receives too many bit errors. The transmit part of the opposite station is faulty. The alarmed board itself is faulty. The configuration of services at the local or opposite station is incorrect.



Handling Procedure Step 1 Confirm the alarmed optical interface and AU-4 path according to the alarm parameters.

Step 2 On the T2000, check whether the relevant optical interface has the B1_EXC or B1_SD alarm. If yes, clear the B1_EXC or B1_SD alarm.

Step 3 If the AU_LOP alarm persists after the B1_EXC or B1_SD alarm is cleared, check whether the services in the relevant path of the local and opposite stations are consistent with the service planning. If not, reconfigure the services.

Step 4 If the AU_LOP alarm persists, check whether the clock board and the cross-connect board of the opposite station are working properly, according to the alarm information of the opposite station. If any of the mentioned boards is faulty, replace the faulty board.

Step 5 If the alarm persists, contact Huawei technical support engineers to handle the problem.

----End

Related Information The handling method for the AU_LOP alarm of the OptiX OSN 9500 is different from

the handling method for the AU_LOP alarm of the OptiX OSN 1500/2500/3500/7500. Hence, handle the AU_LOP alarms separately for the OptiX OSN 9500 and the OptiX OSN 1500/2500/3500/7500.

If the AU_LOP alarm occurs when the equipment runs in the existing network, you need to contact Huawei technical support engineers and report the alarm although you have cleared it by adopting the mentioned methods.

3.8 B1_EXC

Description The B1_EXC is an alarm indicating that the number of regenerator section B1 bit errors in the signals received over the line crosses the threshold.

Attribute


Minor Service alarm





Name Meaning


Impact on System When the B1_EXC occurs, the quality of the transmitted services is heavily degraded.

Possible Causes The received signals are heavily attenuated. The fiber connector is dirty. The fiber connector is loose. The attenuation value specified in the fiber attenuator is extremely high or low. The transmit unit at the opposite station is faulty. The receive unit at the local station is faulty.

Handling Procedure Step 1 Check whether any higher-level alarm, such as the R_LOS or R_LOF, is detected on the

T2000. If yes, take priority to clear it, and then check whether the B1_EXC alarm is cleared.

Step 2 Check whether the ambient temperature in the equipment room is higher than 45ºC. If yes, decrease the working temperature of the equipment, and then check whether the B1_EXC alarm is cleared.

Step 3 Check whether the clock source setting of the local station is correct. If the clock source setting is inconsistent with the design, modify the clock source setting, and then check whether the B1_EXC alarm is cleared.

Step 4 Check whether the received optical power of the alarm board is within the specified value range.

If yes, go to Step 5. If not, follow the steps:

1. Insert the fiber connector firmly, and then check whether the alarm is cleared. 2. Check whether the attenuation value specified in the fiber attenuator is proper. If not,

adjust it to a proper value, and then check whether the alarm is cleared. 3. Clean the fiber connector at the local station and the receive optical interface on the line

board, and then check whether the alarm is cleared. 4. Check whether the flange is correctly connected to the optical attenuator at the local

station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared.

5. Check whether the launched optical power at the opposite station is within the specified value range.

6. If the launched optical power is beyond the specified value range, replace the optical module, and then check whether the alarm is cleared. If not, replace the line board at the opposite end, and then check whether the alarm is cleared.



7. If the launched optical power is within the specified value range, clean the fiber connector at the opposite station, and then check whether the alarm is cleared.

8. Check whether the flange is correctly connected to the optical attenuator at the opposite station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared.

Step 5 If the alarm persists, check whether the fiber cable is faulty. If yes, remove the fault, and then check whether the B1_EXC alarm is cleared.

Step 6 If the alarm persists, check whether the receive board at the local station is faulty. If yes, replace it, and then check whether the B1_EXC alarm is cleared.

Step 7 If the alarm persists, replace the relevant line board at the opposite station, and then check whether the B1_EXC alarm is cleared.


----End


3.9 B1_SD

Description The B1_SD is an alarm indicating that regenerator section B1 signals received over the line are degraded. When a line board has detected the B1 byte, showing that the bit error ratio of the regenerator section signals exceeds the specified threshold value (default value: 1 x 10–6), the B1_SD alarm is reported.

Attribute


Minor Service alarm


Name Meaning





Impact on System When the B1_SD occurs, the quality of the transmitted services is heavily degraded.



T2000. If yes, take priority to clear it, and then check whether the B1_SD alarm is cleared.

Step 2 Check whether the ambient temperature in the equipment room is higher than 45ºC. If yes, decrease the working temperature of the equipment, and then check whether the B1_SD alarm is cleared.

Step 3 Check whether the clock source setting of the local station is correct. If the clock source setting is inconsistent with the design, modify the clock source setting, and then check whether the B1_SD alarm is cleared.













Step 5 If the alarm persists, check whether the fiber cable is faulty. If yes, remove the fault, and then check whether the B1_SD alarm is cleared.

Step 6 If the alarm persists, check whether the receive board at the local station is faulty. If yes, replace it, and then check whether the B1_SD alarm is cleared.

Step 7 If the alarm persists, replace the relevant line board at the opposite station, and then check whether the B1_SD alarm is cleared.


----End


3.10 B1B_EXC

Description The B1B_EXC is an alarm indicating that the higher order cross-connect board detects the threshold-crossing of bit errors in the services received from the backplane bus.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the slot number of the board connected to the faulty bus (the board can be a line board or a lower order cross-connect board).

Parameter 2 Indicates the number of the faulty bus in the slot. The starting number is 1.

Impact on System When the B1B_EXC alarm occurs, the services that pass through the relevant bus have bit errors or are even interrupted. This alarm triggers the active/standby switching of the higher order cross-connect boards.




Possible Causes The higher order cross-connect board is not securely inserted. The board in the corresponding line slot is not securely inserted. The higher order cross-connect has a hardware failure. The line board in the corresponding line slot has a hardware failure. The backplane bus that connects the board in the line slot and the higher order

cross-connect board is faulty.

Handling Procedure Step 1 On the T2000, confirm the slot number of the board connected to the faulty bus.

Step 2 Perform a cold reset for the higher order cross-connect board that reports the B1B_EXC alarm, or remove the board and insert it again.

Step 3 If the alarm persists, perform a cold reset for the board in the corresponding line slot, or remove the board and insert it again. Check whether the alarm is cleared.

Step 4 Replace the board in the corresponding line slot, and then check whether the alarm is cleared.

Step 5 Replace the relevant higher order cross-connect board, and then check whether the alarm is cleared.

Step 6 If the alarm persists after the board replacement, the backplane bus of the equipment might be abnormal. Contact Huawei technical support engineers to handle the problem.

----End

Related Information Before resetting or replacing a lower order or higher order cross-connect board, check

whether the cross-connect board is in the standby status. If yes, you can directly reset or replace the cross-connect board. If not, the direct reset or replacement is a dangerous operation that will cause service interruption. In this case, perform the active/standby switching so that the relevant cross-connect board changes to the standby status before you reset or replace it.

If the B1B_EXC alarm occurs when the equipment runs in the existing network, you need to contact Huawei technical support engineers and report the alarm although you have cleared it by adopting the mentioned methods.

3.11 B2_EXC

Description The B2_EXC is an alarm indicating that the number of multiplex section B2 bit errors in the signals received over the line exceeds the specified value. When a line board has detected the B2 byte, showing that the bit error ratio of the multiplex section signals exceeds the value 1 x 10-3, the B2_EXC alarm is reported.



Attribute


Minor Service alarm


Name Meaning


Impact on System When the B2_EXC occurs, the quality of the transmitted services is heavily degraded. When the B2_EXC occurs, by default, the system inserts the AU_AIS alarm in the

cross-connection direction.



T2000. If yes, take priority to clear it, and then check whether the B2_EXC alarm is cleared.


Step 3 Check whether the clock source setting of the local station is correct. If the clock source setting is inconsistent with the design, modify the clock source setting, and then check whether the B2_EXC alarm is cleared.


















----End


3.12 B2_SD

Description The B2_SD is an alarm indicating that the number of multiplex section B2 bit errors in the signals received over the line exceeds the specified value. When a line board has detected the B2 byte, showing that the bit error ratio of the multiplex section signals exceeds the value 1 x 10-6, the B2_SD alarm is reported.



Attribute


Minor Service alarm


Name Meaning


Impact on System When the B2_SD alarm occurs, the quality of the transmitted services is heavily

degraded. When the B2_SD alarm occurs, the system returns the M1 byte to the opposite end,

showing the MS_REI alarm. Consequently, the remote station reports the MS_REI alarm.

Possible Causes The number of B1 bit errors is extremely high. The received signals are heavily attenuated. The fiber connector is dirty. The fiber connector is loose. The attenuation value specified in the fiber attenuator is extremely high or low. The transmit unit at the opposite station is faulty. The receive unit at the local station is faulty.


T2000. If yes, take priority to clear it, and then check whether the B2_SD alarm is cleared.


Step 3 Check whether the clock source setting of the local station is correct. If the clock source setting is inconsistent with the design, modify the clock source setting, and then check whether the B2_SD alarm is cleared.


















----End


3.13 B3_EXC

Description The B3_EXC is an alarm indicating that the number of multiplex section B3 bit errors in the signals received over the line exceeds the specified value. When a line board has detected the B3 byte, showing that the bit error ratio of the multiplex section signals exceeds the value 1 x 10-3, the B3_EXC alarm is reported.



Attribute


Minor Service alarm


Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the B3_EXC alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System When the B3_EXC alarm occurs, bit errors occur in the path-level services. When the B3_EXC alarm occurs, the system returns the G1 byte to the opposite end,

showing the HP_REI alarm. Consequently, the opposite station reports the HP_REI alarm. If the AU_AIS alarm is inserted when the B3_EXC alarm occurs, the system returns the G1 byte to the opposite end, showing the HP_RDI alarm. Consequently, the remote station generates the HP_RDI alarm.


Handling Procedure Step 1 Check whether any higher-level alarm, such as the R_LOS , R_LOF , B1_EXC or B2_EXC,

is detected on the T2000. If yes, take priority to clear it, and then check whether the B3_EXC alarm is cleared.





Step 3 If the B3_EXC alarm is not cleared, check whether the configuration of the AU-4 path that reports the alarm is consistent with the planned configuration. If not, reconfigure the service according to the planned configuration.















----End




3.14 B3_EXC_VC3

Description The B3_EXC_VC3 is an alarm indicating that the number of B3 bit errors in the lower order path VC-3 crosses the threshold. If a board has detected that the number of B3 bit errors exceeds the specified threshold value (default value: 1 x 10-3), the B3_EXC_VC3 alarm is reported.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the service mode of the board.


Indicates the number of the path in which the alarm occurs. Parameter 2 is the higher byte, and Parameter 3 is the lower byte. For example, Parameter 2 = 0x00, Parameter 3= 0x01. In this case, the B3_EXC_VC3 alarm is reported from path 1 of the board.

Parameter 4 Indicates the number of the lower order path. For a line board, it indicates the number of the VC-3 lower order path. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01, Parameter 4 = 0x01. In this case, the B3_EXC_VC3 alarm is reported from VC-3 lower order path 1 of AU-4 path 1 for optical interface 1 on the board.

Impact on System When the B3_EXC_VC3 alarm occurs, a great number of bit errors occur in the VC-3 service.

Possible Causes A higher-level bit error alarm occurs in the system. The received signals are heavily attenuated. The fiber connector is dirty. The fiber connector is loose.




The transmit unit at the opposite station is faulty. The receive unit at the local station is faulty.

Handling Procedure Step 1 Check whether any higher-level alarm, such as the B1_EXC, B1_SD, B2_EXC, B2_SD,

B3_EXC or B3_SD, is detected at the local station and at the upstream station. If yes, take priority to clear it, and then check whether the B3_EXC_VC3 alarm is cleared.

Step 2 If the alarm persists, check whether the received optical power of the alarm board is within the specified value range.










Step 3 If the alarm persists, replace the board that generates the B3_EXC_VC3 alarm.

----End


3.15 B3_SD

Description The B3_SD is an alarm indicating that the number of multiplex section B3 bit errors in the signals received over the line exceeds the specified value. When a line board has detected the



B3 byte, showing that the bit error ratio of the multiplex section signals exceeds the value 1 x 10-6, the B3_SD alarm is reported.

Attribute


Minor Service alarm


Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the B3_SD alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System When the B3_SD alarm occurs, bit errors occur in the path-level services. When the B3_SD alarm occurs, the system returns the G1 byte to the opposite end,

showing the HP_REI alarm. Consequently, the opposite station reports the HP_REI alarm. If the AU_AIS alarm is inserted when the B3_SD alarm occurs, the system returns the G1 byte to the opposite station, showing the HP_RDI alarm. Consequently, the opposite station generates the HP_RDI alarm.

Possible Causes The number of B1 or B2 bit errors is extremely high. The received signals are heavily attenuated. The fiber connector is dirty. The fiber connector is loose. The attenuation value specified in the fiber attenuator is extremely high or low. The transmit unit at the opposite station is faulty. The receive unit at the local station is faulty.

Handling Procedure Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, B1_EXC or B2_EXC, is

detected on the T2000. If yes, take priority to clear it, and then check whether the B3_SD alarm is cleared.





Step 3 If the B3_SD alarm is not cleared, check whether the configuration of the AU-4 path that reports the alarm is consistent with the planned configuration. If not, reconfigure the service according to the planned configuration.















----End




3.16 B3_SD_VC3

Description The B3_SD_VC3 is an alarm indicating that the number of B3 bit errors in the lower order path VC-3 crosses the threshold. If a board has detected that the number of B3 bit errors exceeds the specified threshold value (default value: 1 x 10-6), the B3_SD_VC3 alarm is reported.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the service mode of the board.


Indicates the number of the path in which the alarm occurs. Parameter 2 is the higher byte, and Parameter 3 is the lower byte. For example, Parameter 2 = 0x00, Parameter 3= 0x01. In this case, the B3_SD_VC3 alarm is reported from path 1 of the board.

Parameter 4 Indicates the number of the lower order path. For a line board, it indicates the number of the VC-3 lower order path. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01, Parameter 4 = 0x01. In this case, the B3_SD_VC3 alarm is reported from VC-3 lower order path 1 of AU-4 path 1 for optical interface 1 on the board.

Impact on System When the B3_SD_VC3 alarm occurs, the service transmission quality in the VC-3 service channel is degraded.

Possible Causes Higher-level bit alarms occur in the system. The received signals are heavily attenuated. The fiber connector is dirty.




The fiber connector is loose. The receive unit at the opposite station is faulty. The transmit unit at the local station is faulty.

Handling Procedure Step 1 Check whether any higher-level alarm, such as the B1_EXC, B1_SD, B2_EXC, B2_SD,

B3_EXC or B3_SD, is detected at the local station and at the upstream station. If yes, take priority to clear it, and then check whether the B3_SD_VC3 alarm is cleared.

Step 2 If the alarm persists, check whether the received optical power of the alarm board is within the specified value range.










Step 3 If the alarm persists, replace the board that generates the B3_SD_VC3 alarm.

----End




3.17 BD_NOT_INSTALLED

Description The BD_NOT_INSTALLED is an alarm indicating that the logical board is not installed in the corresponding slot. This alarm occurs when a physical board is installed but no logical board is created on the T2000.

Attribute




Name Meaning

Parameter 1 Indicates the number of the slot that generates this alarm.

Impact on System When the BD_NOT_INSTALLED alarm occurs, the corresponding slot cannot be configured with services. This alarm, however, does not affect the operation of the system.

Possible Causes The possible cause of the BD_NOT_INSTALLED is as follows:

A physical board is installed in the slot, but the corresponding logical board is not created on the T2000.

Handling Procedure Step 1 View the BD_NOT_INSTALLED alarm on the T2000, and then confirm the slot number

according to Parameter 1.

Step 2 This alarm is cleared when the logical board is added to the corresponding slot on the T2000. If the physical board is not in use, remove the board from the equipment to clear this alarm.

----End





3.18 BD_STATUS

Description The BD_STATUS is an alarm indicating that the physical board is offline. This alarm occurs when the logical board is created on the T2000 but the physical board is not inserted in the subrack.

Attribute


Major Equipment alarm


Name Meaning

Parameter 1 Indicates the slot number of the out-of-position board.

Parameter 2 Indicates the specific out-of-position status of the board. 0x01: The board is not in position.

Impact on System Since the physical board is not inserted in the equipment, the data that is configured on the NE cannot be issued to this board. Thus, configuration of services fails.

Possible Causes The possible causes of the BD_STATUS alarm are as follows:

The board is not inserted. The board software is faulty and thus cannot communicate with the NE. The board is not properly inserted. The board is faulty. The board is cold reset or warm reset.

Handling Procedure Step 1 View the BD_STATUS alarm on the T2000 to confirm the relevant board.

Step 2 Check whether the board is cold/warm reset. If yes, wait for several minutes and then check whether the alarm is cleared.



Step 3 Check whether the board is inserted in the corresponding slot.

If not, insert the board and check whether the alarm is cleared. For details, refer to "Removing and Inserting a Board."

If yes, check whether the board is in good contact with the backplane or whether the board is properly inserted. Perform a remove-and-insert operation to the board. Then, check whether this alarm is cleared. For details, refer to "Removing and Inserting a Board."

Step 4 If the alarm persists, replace the board that reports the alarm, and then check whether the BD_STATUS alarm is cleared. For details, refer to "Replacing a Board."

----End

Related Information To check whether the board is under reset, observe the indicators on the front panel of the board to determine the board status.

If the RUN indicator flashes once every two seconds, the board is in the normal status. If the RUN indicator flashed five times every two seconds, the board is under reset, and

the board software is starting up.

3.19 BDID_ERROR

Description The BDID_ERROR is an alarm of slot verification error. This alarm occurs when the board parity check fails or when the board is not properly secured in its slot.

Attribute



Parameters None

Impact on System When the BDID_ERROR alarm occurs, the board may fail to get online and as a result

the services are interrupted. In this case, you cannot configure and monitor the services for the board.

Possible Causes The board is not properly secured in the slot. The board hardware fails.




Pins on the backplane are twisted.

Handling Procedure Step 1 View the BDID_ERROR alarm on the T2000 to confirm the relevant board.

Step 2 Remove the board to check whether there are any twisted pins on the backplane. If any pins are twisted, fix them and then insert the board. Check whether the alarm is cleared.

Step 3 If the alarm persists, replace the board.

----End


3.20 BIOS_STATUS

Description The BIOS_STATUS is an alarm indicating that the board cannot reach a normal software running status.

Attribute




Name Meaning

Parameter 1 Indicates the slot number of the out-of-position board.

Impact on System The services on the alarmed board are interrupted.

Possible Causes The board is reset for three consecutive times.



The board software is lost. The board software has an error.

Handling Procedure Step 1 Reset the board, and check whether the BIOS_STATUS alarm is still generated.

Step 2 If the alarm is still generated after the board reset, contact Huawei engineers to re-load the board software.

Step 3 If the alarm is still generated after the board software is re-loaded, replace the alarmed board.

----End


3.21 BOOTROM_BAD

Description The BOOTROM_BAD is an alarm indicating the BOOTROM data check failure. During the running of board software, the system periodically checks whether the BOOTROM data is damaged. This alarm occurs when the BOOTROM data is detected damaged.

Attribute


Major Environment alarm


Name Meaning

Parameter 1 Indicates the type of the BIOS damage. 0x01: Basic BIOS damaged 0x02: Extended BIOS damaged




Impact on System If the board has been started, the BOOTROM_BAD alarm does not affect the system or

the services. If you perform a cold reset for the board when there is the BOOTROM_BAD alarm, the

board fails to load BIOS and cannot be started.

Possible Causes The basic BIOS is damaged. The extended BIOS is damaged. The BOOTROM data area is damaged.

Handling Procedure Step 1 View the BOOTROM_BAD alarm on the T2000 and confirm the relevant board.

Step 2 Replace the board. If the board has been started, do not replace the board. Replacing the board can interrupt services, whereas the BOOTROM_BAD alarm does not affect the system or the services.

----End


3.22 BUS_ERR

Description The BUS_ERR is an alarm indicating that the cross-connect board detects bit errors in the backplane bus.

Attribute


Critical Equipment alarm




Name Meaning

Parameter 1 If the higher order cross-connect board reports the BUS_ERR alarm, Parameter 1 indicates the slot number of the board connected to the faulty bus (the board can be a line board or a lower order cross-connect board). If the lower order cross-connect board reports the BUS_ERR alarm, Parameter 1 indicates the number of the faulty bus in the slot. The starting number is 1.

Parameter 2 If the higher order cross-connect board reports the BUS_ERR alarm, Parameter 2 indicates the number of the faulty bus in the slot. The starting number is 1. If the lower order cross-connect board reports the BUS_ERR alarm, Parameter 2 is always 0xff.

Parameter 3 If the higher order cross-connect board reports the BUS_ERR alarm, Parameter 3 indicates the type of the bus error. 0x01: LOS alarm of the bus 0x02: OOF alarm of the bus 0x03: LOF alarm of the bus 0x04: OOA alarm of the bus If the lower order cross-connect board reports the BUS_ERR alarm, Parameter 3 is always 0xff.

Impact on System Bit errors in the backplane bus cause impairment and even interruption of the services. The active/standby switching occurs on the cross-connect board that reports the BUS_ERR alarm.

Possible Causes The possible causes of the BUS_ERR alarm are as follows: The cross-connect board is not securely inserted. The board in the corresponding line slot is not securely inserted. The cross-connect board has a hardware failure. The board in the corresponding line slot has a hardware failure. The backplane bus that connects the board in the line slot and the cross-connect board is

faulty.

Handling Procedure Step 1 Perform a cold reset for the cross-connect board that reports the BUS_ERR alarm, or remove

the cross-connect board and then insert it again. Check whether the alarm is cleared.

Step 2 On the T2000, confirm the slot number of the board connected to the faulty bus.

Step 3 Perform a cold reset for the board in the corresponding line slot, or remove the board and insert it again. Check whether the alarm is cleared.




Step 4 Replace the board in the corresponding line slot, and then check whether the alarm is cleared.

Step 5 Replace the relevant cross-connect board, and then check whether the alarm is cleared.

Step 6 If the alarm persists after the board replacement, the backplane bus of the equipment might be abnormal. Contact Huawei technical support engineers to handle the problem.

----End

Related Information If the BUS_ERR alarm occurs when the equipment runs in the existing network, you need to contact Huawei technical support engineers and report the alarm although you have cleared it by adopting the mentioned methods.

3.23 C2_VCAIS

Description The C2_VCAIS is a C2 byte alarm indication. If a board has detected that the value of the received C2 byte is all "1"s, the C2_VCAIS alarm is reported.

Attribute


Minor Communication alarm


Name Meaning



Indicates the number of the path in which the alarm occurs. Parameter 2 indicates the higher byte, and Parameter 3 indicates the lower byte. It indicates the VC-3 path number. For example, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the C2_VCAIS alarm is reported from path 1 of the board.



Impact on System If the value of the C2 byte is correct, the services are interrupted.

Possible Causes The possible causes of the C2_VCAIS alarm are as follows: The value of the C2 byte to be transmitted is incorrectly configured at the remote end.

Handling Procedure Step 1 Check whether the value of the C2 byte to be transmitted is correctly configured at the remote

end. If not, modify it, and then check whether the C2_VCAIS alarm is cleared.

Step 2 If the alarm persists, replace the transmit board at the remote end.

----End


3.24 CAN_ALM

Description The CAN_ALM is an alarm indicating that the board detects a fault of the CAN bus.

Attribute


Warning Equipment alarm


Name Meaning

Parameter 1 0x01: The active/standby switching of CAN buses occur. 0x02: The active and standby CAN buses are both faulty.




Name Meaning

Parameter 2 0x01: The CAN_ALM alarm is detected by the first MBUS module of the board. 0x02: The CAN_ALM alarm is detected by the second MBUS module of the board.

Impact on System If the active CAN bus is faulty, the switching to the standby bus occurs. If the active and standby CAN buses are both faulty (including the generation of bit

errors), the MBUS communication failure might occur. As a result, the EMPU board cannot monitor the electromechanical features of the alarmed board, such as the temperature and the voltage, and you cannot use the EMPU board to control the power-on and power-off of the alarmed board.

Possible Causes The CAN bus of the alarmed board is faulty.

Handling Procedure Step 1 Replace the board that reports the CAN_ALM alarm.

----End


3.25 COM_EPLD_FAULT

Description The COM_EPLD_FAULT is an alarm indicating that the JCOM board detects a hardware failure of itself.

Attribute



Parameters When you view an alarm on the T2000, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm



Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each parameter, refer to the following table.

Name Meaning

Parameter 1 This parameter is reserved.

Impact on System The JCOM board is the system communication board. If the JCOM board has a hardware failure, the Ethernet communication of the system fails. The COM_EPLD_FAULT alarm does not affect existing services, but affects system functions such as the monitoring for the entire NE and the update of service configuration.

Possible Causes The JCOM board has a hardware failure.

Handling Procedure Step 1 Replace the faulty JCOM board.

----End


3.26 COMMUN_FAIL

Description The COMMUN_FAIL is an alarm of inter-board communication failure. This alarm occurs when the communication between the SCC and other boards is interrupted.

Attribute







Name Meaning

Parameter 1 The value is always 0x01, indicates the DMM communication failure.

Parameter 2 The value is always 0xff.

Impact on System When this alarm occurs, the NE configuration cannot be issued to the board. Thus, the newly-added services go faulty.

Possible Causes The board is faulty. The board is reset.

Handling Procedure Step 1 View the board that generates this alarm on the T2000.

If the COMMUN_FAIL alarm is reported by a single board, do as follows: − Check whether the board is just reset. If yes, wait for several minutes and then check

whether the alarm is cleared. − If the alarm persists, replace the board that reports the alarm, and then check whether

the COMMUN_FAIL alarm is cleared. If this alarm is reported by multiple boards, do as follows:

− Check whether the NEs are connected through switches or Hubs. If yes, troubleshoot the loss of the network VLAN.

− If the alarm persists, perform a remove-and-insert operation to the JEOW. Then, check whether the COMMUN_FAIL alarm is cleared. If the alarm persists, replace the faulty board.

----End


3.27 CPLD_FAIL

Description The CPLD_FAIL is an alarm indicating the complex programmable logical device (CPLD) chip failure in the SCC board.



Attribute



Parameters None

Impact on System The SCC board fails, and the active/standby switching of SCC boards occurs.

Possible Causes The SCC board has a hardware failure.

Handling Procedure Step 1 Replace the SCC board that reports the CPLD_FAIL alarm.

----End

Related Information If the CPLD_FAIL alarm occurs when the equipment runs in the existing network, you need to contact Huawei technical support engineers and report the alarm although you have cleared it by adopting the mentioned methods.

3.28 DBMS_ERROR

Description The DBMS_ERROR is an alarm of database file check failure.

Attribute








Name Meaning

Parameter 1 Indicates the alarm type. The value is the error code that causes the DBMS_ERROR alarm.

Parameter 2 Indicates the database storage area that has errors. 0x00: FDB0 0x01: FDB1 0x02: DRDB

Parameter 3 Indicates the ID of the database that has errors. Currently, the value can only be 0–255 (0x00–0xff).

0x00: Entire storage area 0x01–0xff: Specific database


0xff

Impact on System The backup of the active and standby databases fails. The database cannot be restored by itself.

Possible Causes The software is abnormal. The hardware medium is abnormal.

Handling Procedure Step 1 When the DBMS_ERR alarm occurs, contact the engineers of Huawei.

----End

Related Information The DBMS_ERR alarm is used for the R&D personnel to locate the system abnormality. When the DBMS_ERR alarm occurs, contact the engineers of Huawei.

3.29 DBMS_PROTECT_MODE

Description The DBMS_PROTECT_MODE is an alarm indicating that the NE database enters the protection mode.



Attribute


Critical Processing alarm

Parameters None

Impact on System When the NE database is in the protection mode, the database cannot be performed the backup.

Possible Causes The NE software is repeatedly reset in a certain period.

Handling Procedure Step 1 Find out the cause for the repeated resetting of the NE software and handle it.

Step 2 After the fault is removed, reset the NE software. Accordingly, the database exits the protection mode.

----End


3.30 DLAG_PROTECT_FAIL

Description DLAG_PROTECT_FAIL is an alarm indicating the DLAG protection failure. If negotiation fails or any anomaly occurs during the DLAG protection, the DLAG_PROTECT_FAIL alarm is reported.

Attribute







Name Meaning

Parameter 1 It is always 0x01, and this parameter is meaningless.

Parameter 2, parameter 3

Indicate the ID of the LAG for which the protection fails. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.

Parameter 4 Indicates the protection failure cause. 0x01: Both the working and protection links fail. 0x02: The active and standby ports fail to receive the LACP packets.

0x03: The equipment at the opposite end does not enter the LACP synchronization status.

0x04: The active or standby port detects the self-loop. Alternatively, the active or standby port may form a loop with other ports on the board.

0x05: The communication between the active and standby boards times out.

0x06: The communication between the board and cross-connect board times out.

0x07: The active port selected by LACP is inconsistent with the one selected by cross-connect board.

Parameter 5 It is always 0xFF, and the two parameters are meaningless.

Impact on System When all the protocols at the DLAG port fails, or when the board fails to normally communicate with other boards, the DLAG_PROTECT_FAIL alarm is reported. In the case of the DLAG_PROTECT_FAIL alarm, services cannot be received or transmitted in the LAG, or the user cannot check whether services are normally working.

Possible Causes The possible causes of the DLAG_PROTECT_FAIL alarm are as follows:

Both the active and standby links fail. The active and standby ports fail to receive the LACP packets. The equipment at the opposite end does not enter the LACP synchronization status. The active or standby port detects the self-loop. Alternatively, the active or standby port

may form a loop with other ports on the board. The communication between the active and standby boards times out.



The communication between the board and the cross-connect board or SCC board times out.

The active port selected by LACP is inconsistent with the one selected by cross-connect board.

Handling Procedure Step 1 View the DLAG_PROTECT_FAIL alarm on the T2000, and confirm the board where the

DLAG_PROTECT_FAIL alarm is generated. Confirm the ID of the LAG where the DLAG_PROTECT_FAIL alarm is generated according to Parameter 1, and confirm the cause of the DLAG_PROTECT_FAIL alarm at the port according to Parameter 4.

Step 2 If the value of Parameter 4 is 0x01, it indicates that the link becomes faulty or fails.

On the T2000, check whether the port in the LAG is enabled. If not enabled, enable the port and then check whether the DLAG_PROTECT_FAIL alarm is cleared.

If the DLAG_PROTECT_FAIL alarm persists, check the link state of all the ports. Rectify the fault of the port link, then check whether the DLAG_PROTECT_FAIL alarm is cleared.

Step 3 If the value of Parameter 4 is 0x02, it indicates that the port fails to receive the LACP packets.

On the T2000, check whether the LAG is configured at the opposite end, and check whether the port connected to the faulty port is added to the LAG at the opposite end. Make sure the LAG is correctly configured, and then check whether the DLAG_PROTECT_FAIL alarm is cleared.

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 4 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 4 is 0x04, it indicates the port is in the self-loop status. Release the loop and then check whether the DLAG_PROTECT_FAIL alarm is cleared.

Step 6 If the value of Parameter 4 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 4 is 0x06, it indicates that the communication between the board and the cross-connect board, or SCC board, times out. Make sure the software of the cross-connect board and the SCC is normal. If the board normally communicates with the cross-connect board or SCC board, check whether the DLAG_PROTECT_FAIL alarm is cleared.

Step 8 If the value of Parameter 4 is 0x07, it indicates that the active port selected by LACP is inconsistent with the one selected by cross-connect board. Make sure the active port selected by LACP is consistent with the one selected by cross-connect board, and then check whether the DLAG_PROTECT_FAIL alarm is cleared.

----End





3.31 DUPLEX_ERROR

Description The DUPLEX_ERROR is an alarm indicating that the JCOM board detects the incorrect working mode of its internal chip.

Attribute



Parameters None

Impact on System The JCOM board is the system communication board. If the JCOM board has a hardware failure, the Ethernet communication of the system fails. The DUPLEX_ERROR alarm does not affect existing services, but affects system functions such as the monitoring for the entire NE and the update of service configuration.



----End




3.32 ETH_LOS

Description The ETH_LOS is an alarm indicating loss of network port connection. This alarm occurs when the Ethernet network port cannot receive Ethernet signals.

Attribute


Critical Communication alarm


Name Meaning

Parameter 1 Indicates the number of the port where the ETH_LOS alarm occurs. The value ranges are different from board to board.


Parameter 2 is always 0x00, and Parameter 3 is always 0x01. These parameters are meaningless.

Impact on System When the ETH_LOS alarm occurs, the network port cannot receive data and the services are interrupted.

Possible Causes The port is enabled, but the network cable or fiber of the network port is improperly

connected. The network cable or fiber is faulty. The remote transmit end is faulty. The local receive end is faulty.

Handling Procedure Step 1 View the ETH_LOS alarm on the T2000, and confirm the relevant board and port number

according to Parameter 1.

Step 2 Check whether the network cable or fiber of the port is loose. Re-connect the network cable. Then check whether the alarm is cleared.




Step 3 If the alarm persists, check whether the network cable of fiber is faulty. If yes, replace the network cable or fiber. Then check whether the alarm is cleared.

Step 4 If the alarm persists, query the transmit optical power of the remote station on the T2000. If the transmit optical power is abnormal, replace the corresponding board at the remote station.

Step 5 If the alarm persists, check whether the receive board at the local station is faulty. If yes, replace the faulty board.

----End


3.33 EX_ETHOAM_CC_LOS

Description The EX_ETHOAM_CC_LOS is an alarm indicating the 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 occurs.

Attribute




Name Meaning

Parameter 1(4 bytes)

Indicates the ID of the maintenance point where the alarm occurs. The value range is 0x00000001–0xffffff00. The maintenance point should be unique networkwide. Each node supports up to 1024 maintenance points (each data board supports up to 32 maintenance points).


Indicates the number of the Ethernet port where the alarm occurs.



Name Meaning

Parameter 3 (2 bytes)

Indicates the VLAN ID. 0x0000–0x0fff: Services with VLAN tags 0xffff: Services without VLAN tags

Parameter 4 Indicates the level of the maintenance domain. Level of message: 0x00–0x07

Parameter 5 Indicates the ID of the source maintenance point. The value range is 0x00000001–0xffffff00. The maintenance point should be unique networkwide. Each node supports up to 1024 maintenance points (each data board supports up to 32 maintenance points). Note: The source maintenance point refers to the point that sends the CC message.


Indicates the ID of the sink maintenance point. The value range is 0x00000001–0xffffff00. A maintenance point must be unique in the entire network. Up to 1024 maintenance points can be created at each NE. Each data board supports up to 32 maintenance points. Note: The sink maintenance point refers to the point that reports the EX_ETHOAM_CC_LOS alarm.

Impact on System When the EX_ETHOAM_CC_LOS alarm occurs, it indicates that a unidirectional connectivity failure is detected on the link between the source and the sink maintenance points.

Possible Causes The possible causes of the EX_ETHOAM_CC_LOS alarm are as follows:

A software or hardware failure occurs to the services from the source maintenance point to the sink maintenance point.

Service congestion or service interruption occurs between the source maintenance point and the sink maintenance point.

Handling Procedure Step 1 View the EX_ETHOAM_CC_LOS alarm on the T2000 and confirm the ID of the relevant

maintenance point according to the alarm parameters.

Step 2 Query the information of the maintenance point.

Step 3 Perform loopback (LB) and link trace (LT) test for the source and sink maintenance points, to locate the fault in the services between the source maintenance point and the sink maintenance point.




Step 4 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 also perform LB to confirm that the alarm is cleared.

----End


3.34 EX_ETHOAM_MPID_CNFLCT

Description The EX_ETHOAM_MPID_CNFLCT is an alarm indicating the maintenance point ID conflict. When a maintenance point receives the message sent by another maintenance point with the same MPID in a maintenance domain, this alarm occurs.

Attribute




Name Meaning


Indicates the ID of the maintenance point where the alarm occurs. The value range is 0x00000001–0xffffff00. The maintenance point should be unique networkwide. Each node supports up to 1024 maintenance points (each data board supports up to 32 maintenance points).


Indicates the number of the Ethernet port where the alarm occurs.


Indicates the VLAN ID. 0x0000–0x0fff: Services with VLAN tags 0xffff: Services without VLAN tags

Parameter 4 Indicates the level of the maintenance domain. Level of message: 0x00–0x07



Name Meaning

Parameter 5 Indicates the ID of the source maintenance point. The value range is 0x00000001–0xffffff00. The maintenance point should be unique networkwide. Each node supports up to 1024 maintenance points (each data board supports up to 32 maintenance points). Note: The source maintenance point refers to the point that sends the CC message.

Impact on System The maintenance point should be unique networkwide. The maintenance point conflict can affect the protocol and cause the LB and LT tests to become abnormal. The services may be wrongly received.

Possible Causes The possible cause of the EX_ETHOAM_MPID_CNFLCT alarm is as follows:

Multiple maintenance points with the same MPID are created in a maintenance domain.

Handling Procedure Step 1 View the EX_ETHOAM_MPID_CNFLCT alarm on the T2000 and confirm the ID of the

relevant maintenance point according to the alarm parameters.

Step 2 Query the information of the maintenance point. Delete all the maintenance points with the same MPID, then the alarm is automatically cleared.

----End


3.35 EXT_SYNC_LOS

Description The EXT_SYNC_LOS is an alarm indicating the loss of external clock source. This alarm occurs when the system detects the loss of the external clock source traced by the equipment.

Attribute







Name Meaning

Parameter 1 Indicates which external clock source is lost. 0x01: The first external clock source is lost. 0x02: The second external clock source is lost.

Impact on System When the EXT_SYNC_LOS alarm occurs, the external clock source of the system is lost and cannot be traced by the equipment. Because the clock quality is lowered, the service quality may be affected, and pointer justifications and even bit errors may be generated.

Possible Causes The physical interface for the external clock source loses signals. The input and output modes of the external clock source are inconsistent. The clock input cable is incorrectly connected.

Handling Procedure Step 1 Make sure that the external clock equipment properly transmits signals. Replace the external

clock equipment with a normal one, and then check whether the EXT_SYNC_LOS alarm is cleared.

Step 2 If the alarm persists, check whether the input and output modes of the external clock source are consistent. After the input and output of the external clock source are set to the same mode (either 2 MHz or 2 Mbit/s), check whether the alarm is cleared.

Step 3 If the alarm persists, check whether the clock input cable is correctly connected. After ensuring the correct connection of the clock input cable, check whether the alarm is cleared.

Step 4 If the alarm persists, or multiple boards report the alarm, contact Huawei technical support engineers to handle the problem.

----End




3.36 FAN_FAIL

Description The FAN_FAIL is an alarm of fan faults. This alarm occurs when the fan is faulty.

Attribute




Name Meaning

Parameter 1 Indicates the fan number: 1-6

Impact on System If the FAN_FAIL alarm is not cleared in time, the NE may be damaged due to overheat. Then, the services on the entire equipment are interrupted.

Possible Causes The fan is not switched on. The fan fails.

Handling Procedure Step 1 Check whether the fan tray assembly is tightly inserted. Perform a remove-and-insert

operation to the fan tray assembly. Then, check whether the FAN_FAIL alarm is cleared.

Step 2 If the alarm persists, the fan tray assembly may be faulty. In this case, replace the faulty fan tray assembly.

----End





3.37 FAN_PWR_ALM

Description The FAN_PWR_ALM is an alarm indicating that the voltage of the fan power module is abnormal and the fan might be functioning improperly.

Attribute




Name Meaning

Parameter 1 Indicates the fan power number.

Parameter 2 0x01: Undervoltage 0x02: Overvoltage

Impact on System The fan power module is on the JPIU board, and supplies power for the fan on the OptiX OSN 9500 subrack. The abnormal voltage of the fan power module might cause fan instability, an over high working temperature of the NE, or even NE damage that will result in service interruption.

Possible Causes The input voltage for the equipment is abnormal. The alarmed JPIU board is faulty.

Handling Procedure Step 1 Check whether the voltage of the two groups of 63 A output terminals on the left and right of

the DC power distribution box is normal.

If the power supply voltage is –48 V DC, the normal voltage range is –38.4 V DC to –57.6 V DC.


Step 2 If the measured voltage is beyond the normal range, locate and handle the problem.



Step 3 If the alarm is generated even in the case of normal external input voltage, the JPIU board is faulty. Replace the faulty JPIU board.

----End

Related Information Before replacing the JPIU board, confirm whether the input power capacity of one single JPIU board is enough to supply power for the entire subrack. Be very cautious because the replacement of the JPIU board is a dangerous operation.

3.38 FIFO_OVERFLOW

Description The FIFO_OVERFLOW is an alarm indicating that the board has a hardware failure.

Attribute




Name Meaning



Parameter 3 The value is always 0xff, and this parameter is meaningless.

Impact on System When the FIFO_OVERFLOW alarm occurs, the board cannot correctly lock on the clock of the clock board. In this case, the service quality might be degraded, or the services might even be interrupted.

Possible Causes The crystal oscillator of the board is damaged.




Handling Procedure Step 1 View the FIFO_OVERFLOW alarm on the T2000 to confirm the relevant board.

Step 2 Perform a cold reset for the board, or remove the board and insert it again. Check whether the alarm is cleared.

Step 3 If the alarm persists, replace the faulty board.

Step 4 If the alarm persists after the faulty board is replaced, contact Huawei technical support engineers to handle the problem.

----End


3.39 FPGA_ABN

Description The FPGA_ABN is an alarm indicating the failure of reading and writing the FPGA.

Attribute




Name Meaning

Parameter 1 The value is always 0x01.


The value is always 0x01. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.


The value is 0xff. Currently, these parameters are not used.



Impact on System When the alarm occurs, the board fails to function. If the board is reset, the services may be interrupted.

Possible Causes The FPGA of the board is lost or damaged.

Handling Procedure Step 1 Download the FPGA of the board again and then check whether the FPGA_ABN alarm is

cleared.


----End


3.40 HARD_BAD

Description The HARD_BAD is an alarm indicating that the alarmed board has a hardware failure.

Attribute




Name Meaning







Impact on System The board detects that its hardware is abnormal. In this case, the board might function improperly. As a result, the services might have bit errors and might even be interrupted.

Possible Causes The alarmed board has a hardware failure.

Handling Procedure Step 1 Replace the alarmed board.

----End


3.41 HP_CROSSTR

Description The HP_CROSSTR is an alarm indicating that the number of the higher order path bit errors crosses the threshold.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the optical interface number where the excessive higher order path bit errors occur.


Indicates the path number where the excessive higher order path bit errors occur.



Name Meaning

Parameter 4 The higher two bits indicate the performance monitoring period. 0x01: 15-minute performance monitoring 0x02: 24-hour performance monitoring

The lower six bits together with Parameter 5 indicate the performance event ID.

Parameter 5 Indicates the performance event ID.

Impact on System The service quality of the board that reports the alarm is lowered. The services of the board that reports the alarm are interrupted.

Possible Causes The laser performance at the opposite station is degraded. The received optical power at the local station is too high or too low. The clock performance at the local station or the opposite station is degraded. The fiber performance is degraded.

Handling Procedure Step 1 Perform an inloop on the board that reports the HP_CROSSTR alarm at the local station.

The loopback causes service interruption.

If the alarm is cleared, go to Step 2. If the alarm persists, it indicates that the fault occurs to the local station. Go to Step 4.

Step 2 Perform an outloop at the opposite station.


If the alarm is cleared, it indicates that the fault occurs to the local station. Go to Step 3. If the alarm persists, it indicates that the fiber performance is degraded or the fiber

jumper connector is dirty. Go to Step 5.

Step 3 Replace the line board at the opposite station.

If the alarm is cleared, the fault is removed. The alarm handling ends.




If the alarm persists, replace the cross-connect and timing board at the opposite station. The alarm handling ends.

Step 4 Replace the board that reports the HP_CROSSTR alarm at the local station.

If the alarm is cleared, the fault is removed. The alarm handling ends. If the alarm persists, replace the cross-connect and timing board at the local station. The

alarm handling ends.

Step 5 Clean the fiber jumper connectors at both the local and opposite stations.

If the alarm is cleared, the fault is removed. The alarm handling ends. If the alarm persists, it indicates that the fault occurs to the fiber cables. Remove the fault,

and the alarm handling ends.

----End

Related Information None.

3.42 HDLC_FAIL

Description The HDLC_FAIL is an alarm indicating the high-level data link control (HDLC) communication failure between boards.

Attribute




Name Meaning

Parameter 1 Indicates the number of the slot whose board has the communication failure with the alarmed board.

Parameter 2 Indicates the faulty HDLC path number.



Impact on System MSP and SNCP Service downloading SSM protocol processing

Possible Causes The HDLC communication between boards fails.

Handling Procedure Step 1 Check whether the JPBU board is in position. If not, properly insert the JPBU board in

position.

Step 2 If only one board reports the HDLC_FAIL alarm, perform a cold reset for the alarmed board, or replace the alarmed board.

Step 3 If the alarm persists, or multiple boards report the alarm, contact Huawei technical support engineers to handle the problem.

----End


3.43 HP_CDI

Description The HP_CDI is a higher order path connection defect indication.

Attribute




Name Meaning





Name Meaning


Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_CDI alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System The HP_CDI alarm does not affect services.

Possible Causes At the opposite station, the access point identifier of the path that receives signals is incorrect.

Handling Procedure Step 1 Check the service configuration and alarms of the opposite equipment. If the service

configuration is incorrect, modify the configuration and then check whether the HP_CDI alarm is cleared.

----End


3.44 HP_LOM

Description The HP_LOM is an alarm indicating loss of multiframe in the higher order path.

Attribute






Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_LOM alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System None.

Possible Causes The service configuration is incorrect. The H4 byte is lost or incorrect.

Handling Procedure Step 1 Check whether the service configuration of the upstream NE is consistent with the service

planning, and whether the accessed services are consistent with the planned services. After modifying the incorrect service configuration, check whether the HP_LOM alarm is cleared.

Step 2 If the alarm persists, reset or replace the alarmed line board of the local station, and then check whether the alarm is cleared.


----End


3.45 HP_PDI

Description The HP_PDI is a higher order path payload defect indication. The HP_PDI alarm is an accompanying alarm. When the HP_SLM alarm is generated in the corresponding path on the line board of the opposite station, the opposite station returns the HP_PDI alarm to the local station. The HP_PDI alarm is reported by an opposite NE and detected by the local NE.

Attribute







Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_PDI alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System The HP_PDI alarm indicates the fault of the opposite NE, and does not affect the local NE. The opposite NE might have the HP_SLM alarm.

Possible Causes The HP_SLM alarm is generated at the opposite station. The receive unit at the local station is faulty.

Handling Procedure Step 1 Handle the HP_SLM alarm in the relevant path of the opposite station.

Step 2 If the HP_PDI alarm exists even in case the HP_SLM alarm is not generated in the relevant path of the opposite station, the board of the local station is faulty. Replace the board that reports the HP_PDI alarm.

----End


3.46 HP_RDI

Description The HP_RDI is an alarm indicating a remote defect in the higher order path.



Attribute




Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_RDI alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System When the HP_RDI alarm occurs, the local station is not affected. This alarm just shows that the path-level services at the remote end are interrupted.

Possible Causes The HP_RDI alarm is an accompanying alarm. When the opposite station reports an alarm (such as the AU_AIS, AU_LOP, HP_TIM or HP_SLM) from the relevant path of the line board, the opposite station returns the HP_RDI alarm to the local station.

Handling Procedure Step 1 After you clear the AU_AIS, AU_LOP, HP_TIM or HP_SLM alarm reported from the path of

the line board at the opposite station, the HP_RDI alarm is automatically cleared.

----End





3.47 HP_REI

Description The HP_REI is a remote error indication in the higher order path.

Attribute


Warning Communication alarm


Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_REI alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System When the HP_REI alarm occurs, the local station is not affected. This alarm just shows that bit errors are received at an intermediate station, and the quality of the transmitted higher order services is degraded.

Possible Causes The HP_REI alarm is an accompanying alarm. When an intermediate station has detected an alarm (such as the B3_EXC or B3_SD) of B3 bit errors, it returns an HP_REI alarm to the local station.

Handling Procedure Step 1 After you clear the B3_EXC or B3_SD alarm that occurs at an intermediate station, the

HP_REI alarm is automatically cleared.

----End




3.48 HP_SDI

Description The HP_SDI is a higher order path service defect indication.

Attribute




Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_SDI alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System When the HP_SDI alarm occurs, the opposite station detects a service failure.

Possible Causes The opposite station receives the AU_AIS or AU_LOP alarm. The receive unit at the opposite station is faulty. The transmit unit at the local station is faulty.

Handling Procedure Step 1 If the opposite station reports the AU_AIS or AU_LOP alarm, handle these alarms.

Step 2 If the HP_SDI alarm persists after the AU_AIS or AU_LOP alarm is cleared, replace the line board of the opposite station.




Step 3 If the HP_SDI alarm persists after the line board of the opposite station is replaced, replace the alarmed line board of the local station.

----End


3.49 HP_SLM

Description The HP_SLM is a signal label mismatch alarm in the higher order path. When a line board has detected that the received C2 byte is inconsistent with the C2 byte to be received, the HP_SLM alarm is reported.

Attribute




Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_SLM alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System If the AU-AIS alarm is inserted when the HP_SLM alarm occurs, the path service is interrupted. Moreover, the HP-RDI alarm is returned to the opposite station.

Possible Causes The service type is incorrectly configured.



The signal identification overhead (C2 byte) to be received in the higher order path does not match the received signal identification overhead (C2 byte) at the local station. Moreover, the received C2 byte is not 0x00.

Handling Procedure Step 1 Trace back to the upstream station, and find the station at which lower order services are

provided for the board. The source board at the station is the source of transmitting the C2 byte, and all the intermediate nodes transmit the C2 byte transparently. In this way, you can find the station from which the value of the C2 byte is received at the local station, and this station is regarded as the termination station.

Step 2 Check whether the service types configured at the termination station map the value of the C2 byte to be transmitted. If not, modify the value of the C2 byte to be transmitted, check whether the HP_SLM alarm is cleared.

Step 3 Check whether the service types configured at the local station map the value of the C2 byte to be received. If not, modify the value of the C2 byte to be received, and then check whether the HP_SLM alarm is cleared.

Step 4 If the alarm persists, check whether the service types configured at the termination station are consistent with those at the local station. If not, modify the configured services as required, and then check whether the HP_SLM alarm is cleared.


----End


3.50 HP_TIM

Description The HP_TIM is a trace identifier mismatch alarm in the higher order path.

Attribute







Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_TIM alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System This alarm does not affect services. If the HP_TIM alarm is set as a switching trigger condition in the case of SNCP, and no

higher level alarms occur on other nodes in the network, the HP_TIM alarm triggers the SNCP switching.

Possible Causes The service cross-connections are incorrectly configured. The J1 byte is incorrectly configured.

Handling Procedure Step 1 Check whether the service cross-connections are correctly configured. If not, configure the

correct service cross-connections, and then check whether the HP_TIM alarm is cleared.

Step 2 If the alarm persists, trace back to the upstream station, and find the station at which lower order services are provided. The source board at the station is the source of transmitting the J1 byte, and all the intermediate nodes transmit the J1 byte transparently. In this way, you can find the station from which the value of the J1 byte is received at the local station, and this station is regarded as the termination station.

Step 3 Check whether the value of the J1 byte to be transmitted from the line board of the termination station is consistent with that of the J1 byte to be received at the line board of the local station. If not, modify the value of the J1 byte as required. After modification, the HP_TIM alarm is automatically cleared.

----End


3.51 HP_UNEQ

Description The HP_UNEQ is an alarm indicating that no signals are loaded in the higher order path.



Attribute




Name Meaning



Indicates the AU-4 path number. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01. In this case, the HP_UNEQ alarm is reported from AU-4 path 1 of optical interface 1 on the board.

Impact on System If the AU-AIS alarm is inserted when the HP_UNEQ alarm occurs, the path service is interrupted. Moreover, the HP-RDI alarm is returned to the opposite station.

Possible Causes No services are configured at the opposite station. No services are configured at the upstream station. The received C2 byte is 0.

Handling Procedure Step 1 Check whether the relevant path is configured with services at the opposite station.

Step 2 If the relevant path is not configured with services, the opposite station transmits the services that are not loaded. After configuring correct services, check whether the HP_UNEQ alarm is cleared.

Step 3 If the opposite station is configured with services, check whether the HP_UNEQ alarm occurs in the relevant path of the upstream station. If yes, the upstream station transparently transmits the services that are not loaded to the local station. In this case, clear the HP_UNEQ alarm at the upstream station.

Step 4 If the alarm persists, trace back to the upstream station, and find the station at which lower order services are provided. The source board at the station is the source of transmitting the C2 byte, and all the intermediate nodes transmit the C2 byte transparently. In this way, you can find the station from which the value of the C2 byte is received at the local station, and this station is regarded as the termination station.




Step 5 Check whether the C2 byte to be transmitted from the termination station is configured with the value 0x00. If yes, modify the value according to the actual service type.

----End


3.52 HPAD_CROSSTR

Description The HPAD_CROSSTR is an alarm indicating that the performance of the higher order path adaptation crosses the threshold.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the number of the optical interface where the performance of the higher order path adaptation crosses the threshold.


Indicates the number of the path where the performance of the higher order path adaptation crosses the threshold.




Impact on System The service quality of the board that reports the alarm is degraded.



The services of the board that reports the alarm are interrupted.

Possible Causes The clock loses locking.

Handling Procedure Step 1 Re-set a clock source to clear the fault.

----End


3.53 IN_PWR_ABN

Description The IN_PWR_ABN is an alarm indicating that the input optical power is abnormal.

Attribute




Name Meaning


Impact on System When the IN_PWR_ABN alarm occurs, the service transmission performance is affected. In the case of severe alarm, the services are interrupted.

Possible Causes The fiber is bent heavily.




The fiber head is dirty. The fiber connector is loose. The transmit unit at the opposite station is faulty. The receive unit at the local station is faulty.

Handling Procedure Step 1 Check the received optical power at the local station on the T2000.

1. If the received optical power is extremely low, clean the fiber connector at the local station and the receive optical interface on the line board. After confirming that the fiber connector is inserted firmly, check whether the IN_PWR_ABN alarm is cleared.

2. If the alarm persists, check whether the bending radius of the fiber is less than 6 cm. If yes, spool the fiber jumper again, and then check whether the IN_PWR_ABN alarm is cleared.

3. If the received optical power is extremely high, provide more optical attenuators at the receive optical interface, and then check whether the IN_PWR_ABN alarm is cleared.

Step 2 If the alarm persists, check whether the flange at the local station is correctly connected. After making sure that the flange is correctly connected and cleaned, check whether the IN_PWR_ABN alarm is cleared.

Step 3 If the alarm persists, check whether the launched optical power at the opposite station is proper on the T2000.

If the launched power is improper, replace the board at the opposite station. Then check whether the IN_PWR_ABN alarm is cleared.

If the launched optical power is proper, go to the next step.

Step 4 If the alarm persists, clean the fiber connector at the opposite station. After confirming that the fiber connector is inserted firmly, check whether the IN_PWR_ABN alarm is cleared.

Step 5 If the alarm persists, check whether the flange at the opposite station is correctly connected. After making sure that the flange is correctly connected and cleaned, check whether the IN_PWR_ABN alarm is cleared.

Step 6 If the alarm persists, the receive unit of the board at the local station is faulty. In this case, replace the board at the local station.

----End


3.54 IN_PWR_FAIL

Description The IN_PWR_FAIL is an alarm indicating that the optical amplifier board detects no input power at its input optical interface.



Attribute




Name Meaning


Impact on System The optical amplifier board detects no input power.

If any optical signals that carry services must be amplified through this optical interface, and the service path is protected by MSP or SNCP, the MSP or SNCP switching is triggered.

If any optical signals that carry services must be amplified through this optical interface, and the service path is not protected by MSP or SNCP, the relevant services are interrupted.

Possible Causes There is a fiber cut. The optical module is faulty.

Handling Procedure Step 1 Use the OTDR to test whether the optical cable is cut.

Step 2 Clean the fiber jumper connector at the local station and the receive optical interface on the line board, and then check whether the IN_PWR_FAIL alarm is cleared.

Step 3 Make sure that the flange of the local station is correctly connected, and then check whether the alarm is cleared.

Step 4 Check whether the optical power transmitted by the opposite station is normal. If the optical power transmitted by the opposite station is normal, the receive module of the board at the local station is faulty. Replace the board of the local station.

Step 5 If the optical power transmitted by the opposite station is abnormal, clean the fiber jumper connector at the opposite station, and then check whether the alarm is cleared.

Step 6 Make sure that the flange of the opposite station is correctly connected, and then check whether the alarm is cleared.




Step 7 If the optical power transmitted by the opposite station is still abnormal, the transmit optical module of the board at the opposite station is faulty. Replace the board of the opposite station.

----End


3.55 IN_PWR_HIGH

Description The IN_PWR_HIGH is an alarm of too high input optical power.

Attribute




Name Meaning

Parameter 1 Indicates the actual number of the optical interface on a board where the alarm occurs. For example, 0x01 indicates that the alarm is reported from optical interface 1 of the board.

Impact on System After the IN_PWR_HIGH alarm occurs, the services at the optical interface contain bit errors. Too high input power also causes damages to the laser.

Possible Causes The launched optical power at the opposite station is too high. The type of the selected optical module is not proper.



Handling Procedure Step 1 View the IN_PWR_HIGH alarm on the T2000, and then confirm the optical interface that

reports the alarm according to the alarm parameters.

Step 2 Query the received optical power at the local station on the T2000. Add more optical attenuators and decrease the received optical power according to the queried value. Then, check whether the alarm is cleared.

Step 3 If the alarm persists, query whether the OUT_PWR_HIGH exists at the opposite station. If yes, the received optical power at the opposite station is not proper. Replace the board at the opposite station and check whether the alarm is cleared.

Step 4 If the alarm persists, check whether the types of optical modules that the receive and transmit ends use are proper according to the transmission distance. If the type of either optical module is not proper, replace it with a proper board.

----End


3.56 IN_PWR_LOW

Description The IN_PWR_LOW is an alarm of too low input optical power.

Attribute




Name Meaning





Impact on System After the IN_PWR_LOW alarm occurs, the services at the optical interface contain bit errors.

Possible Causes The launched optical power at the opposite station is too low. The fiber performance is degraded. The type of the selected optical module is not proper.

Handling Procedure Step 1 View the IN_PWR_LOW alarm on the T2000, and then confirm the optical interface where

the alarm occurs according to the alarm parameters.

Step 2 Check whether the types of optical modules that the receive and transmit ends use are proper according to the transmission distance. If the type of either optical module is not proper, replace it with a proper board. Then, check whether the alarm is cleared.

Step 3 If the alarm persists, query the launched optical power at the opposite station. If the launched optical power is not proper, replace it with a proper board. Then, check whether the alarm is cleared.

Step 4 If the alarm persists, clean the fiber connector, and then check whether the IN_PWR_LOW alarm is cleared.

Step 5 If the alarm persists, check whether the fiber is damaged or oppressed. If yes, replace the fiber and then check whether the IN_PWR_LOW alarm is cleared.

Step 6 If the alarm persists, add more optical amplifiers and increase the received optical power. The alarm is automatically cleared.

----End


3.57 INIT_FAILURE

Description The INIT_FAILURE is an alarm indicating that the JCOM board detects the initialization failure of the internal chip.

Attribute





Parameters None.

Impact on System The JCOM board is the system communication board. If the JCOM board has a hardware failure, the Ethernet communication of the system fails. The INIT_FAILURE alarm does not affect existing services, but affects system functions such as the monitoring for the entire NE and the update of service configuration.



----End


3.58 J0_MM

Description The J0_MM is a trace identifier mismatch alarm. When a line board has detected that the received J0 byte at the relevant optical interface is inconsistent with the J0 byte to be received, the J0_MM alarm is reported.

Attribute




Name Meaning





Impact on System When the J0_MM alarm occurs, the services are not affected.

Possible Causes The J0 byte to be transmitted at the opposite end is inconsistent with the J0 byte to be received at the local end.

Handling Procedure Step 1 On the T2000, check whether the expected J0 byte of the board is consistent with that to be

transmitted from the board at the opposite station. If not, modify it as required. Then the J0_MM alarm is automatically cleared.

----End


3.59 K1_K2_M

Description The K1_K2_M is an alarm indicating the mismatch between the K1 and K2 bytes.

Attribute




Name Meaning

Parameter 1 The 0x01 value indicates a linear MSP group.

Parameter 2 Indicates the linear MSP group ID.



Impact on System When the K1_K2_M alarm occurs, the MSP becomes unavailable. If a fiber cut or another fault occurs at this time, the services are interrupted.

Possible Causes Fibers are misconnected. The service board is faulty.

Handling Procedure Step 1 View the K1_K2_M alarm on the T2000, and then confirm the linear MSP group ID

according to the alarm parameters.

Step 2 Make sure that the fibers of the MSP are correctly connected, and that the logical and physical configurations of fibers are consistent. Check whether the alarm is cleared.

Step 3 If the alarm persists, check whether the service boards configured with the MSP at the local and opposite ends are faulty. After replacing faulty service boards, check whether the alarm is cleared.

Step 4 If the alarm persists, check whether the cross-connect boards at the local and opposite ends are faulty. After replacing faulty cross-connect boards, check whether the alarm is cleared.


----End


3.60 K2_M

Description The K2_M is an alarm indicating the K2 byte mismatch. The fifth bit (counted from the highest bit to the lowest bit) of the received K2 byte is mismatched with the configured linear MSP mode.

Attribute








Name Meaning

Parameter 1 The value is always 0x01, which indicates a linear MSP group.


Impact on System If the K2_M alarm is generated during the configuration of linear MSP, there is a mismatch of protection modes between the two stations. The alarm can be cleared after the user corrects the configuration of the MSP group. The alarm has no impact on the system.

Possible Causes Fibers are misconnected. The board is faulty.

Handling Procedure Step 1 View the K2_M alarm on the T2000, and then confirm the MSP group ID according to the

alarm parameters.

Step 2 Make sure that the fibers of the MSP are correctly connected, and that the logical and physical configurations of fibers are consistent. Check whether the alarm is cleared.

Step 3 If the alarm persists, stop the APS protocol and start it again.

Step 4 If the alarm persists, check whether the local board configured with the linear MSP is faulty. Replace the faulty board, and then check whether the K2_M alarm is cleared. For details, refer to "Replacing a Board."


----End


3.61 L_S_ERROR

Description The L_S_ERROR is an alarm indicating that the JCOM board detects the abnormal working status of its internal chip.



Attribute



Parameters None.

Impact on System The JCOM board is the system communication board. If the JCOM board has a hardware failure, the Ethernet communication of the system fails. The L_S_ERROR alarm does not affect existing services, but affects system functions such as the monitoring for the entire NE and the update of service configuration.



----End


3.62 LASER_MOD_ERR

Description The LASER_MOD_ERR is an alarm indicating that the rate set for the optical interface is inconsistent with the actual rate of the optical module.

Attribute







Name Meaning

Parameter 1 Indicates the optical interface number of the board.

Impact on System The alarmed optical interface cannot function.

Possible Causes A wrong optical module is inserted in the alarmed optical interface. The optical module is faulty.

Handling Procedure Step 1 According to the alarm parameters, confirm the relevant line board and optical interface.

Step 2 Use a spare optical module that matches the line board to replace the original optical module in the optical interface.

----End


3.63 LASER_NOT_EXIST

Description The LASER_NOT_EXIST is an alarm indicating that the optical module is not in position.

Attribute






Name Meaning

Parameter 1 Indicates the number of the optical interface where the optical module is not in position.

Impact on System The alarmed optical interface is unavailable.

Possible Causes The optical module is not installed. The optical module is faulty.

Handling Procedure Step 1 Check whether the optical module is installed.

Step 2 If the optical module is installed but the alarm persists, replace the optical module.

Step 3 If the optical module cannot be replaced, replace the entire alarmed board.

----End


3.64 LAG_PORT_FAIL

Description The LAG_PORT_FAIL is an alarm indicating that a port in the LAG fails. If a port in the LAG is unavailable, the LAG_PORT_FAIL alarm is reported.

Attribute






Parameters When you view an alarm on the T2000, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08…. For details about each parameter, refer to the following table.

Name Meaning

Parameter 1 Indicates the MAC port number.


The values are always 0x01, and the two parameters are meaningless.

Parameter 4 Indicates the protection failure cause. 0x01: The link of the port is faulty or fails. 0x02: The port is in the half-duplex mode. 0x03: The port fails to receive the LACP packets. 0x04: The port detects the self-loop. 0x05: Other unknown reasons.

Parameter 5 The value is always 0xFF, and this parameter is meaningless.

Impact on System The port in the LAG cannot balance the service load, and the port does not transmit or receive any services.

Possible Causes The possible causes of the LAG_PORT_FAIL alarm are as follows:

The port is not enabled. The network cable or fiber connected to the port is faulty. The port is in the half-duplex mode. The port fails to receive the LCAP packets. The port detects the self-loop. Other known reasons.

Handling Procedure Step 1 View the alarm on the T2000, and confirm the board where the LAG_PORT_FAIL alarm is

generated. Confirm the number of the MAC port where the LAG_PORT_FAIL alarm is generated according to Parameter 1, and confirm the cause of the LAG_PORT_FAIL alarm at the port according to Parameter 4.

Step 2 If the value of Parameter 4 is 0x01, it indicates that the link becomes faulty or fails.

On the T2000, check whether the port in the LAG is enabled. If not, enable the port and then check whether the LAG_PORT_FAIL alarm is cleared.



If the LAG_PORT_FAIL alarm persists, check the link state of all the ports. Rectify the fault of the port link, and then check whether the LAG_PORT_FAIL alarm is cleared.

Step 3 If the value of Parameter 4 is 0x02, check the working mode of the port in the LAG on the T2000. If the port is in the half-duplex mode, change the working mode of the port to full-duplex, and then check whether the LAG_PORT_FAIL alarm is cleared.


On the T2000, check whether the LAG is configured at the opposite end, and check whether the port connected to the faulty port is added to the LAG at the opposite end. Make sure the LAG is correctly configured, and then check whether the LAG_PORT_FAIL alarm is cleared.

If the LAG_PORT_FAIL alarm persists, check whether the local port transmits packets. If both ends can normally transmit and receive packets, check whether the LAG_PORT_FAIL alarm is cleared.

Step 5 If the value of Parameter 4 is 0x04, it indicates that the port is in the self-loop status. Release the loop and then check whether the LAG_PORT_FAIL alarm is cleared.

Step 6 If the value of Parameter 4 is 0x05, find out the cause according to the networking environment, and then check whether the LAG_PORT_FAIL alarm is cleared.

----End


3.65 LAG_VC_PORT_FAIL

Description The LAG_VC_PORT_FAIL is an alarm indicating that a VCG port in the LAG fails. If the VCTRUNK is unavailable, the LAG_VC_PORT_FAIL alarm is reported.

Attribute



Parameters When you view an alarm on the T2000, select the alarm. In the Alarm Details field display the related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex): parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08…. For details about each parameter, refer to the following table.




Name Meaning

Parameter 1 The value is always 0x01, and this parameter is meaningless.


Indicate the number of the faulty VCG port in the LAG. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.

Parameter 4 Indicates the cause of the protection failure. 0x01: The link of the port is faulty or fails. 0x02: The port is in the half-duplex mode. 0x03: The port fails to receive the LACP packets. 0x04: The port is in the self-loop state. 0x05: Other unknown reasons.

Parameter 5 0xFF

Impact on System The port in the LAG fails to share the service load. When the port is in the LAG, it does not transmit or receive services.

Possible Causes The possible causes of the LAG_VC_PORT_FAIL alarm are as follows:

The port is in the linkdown or disable state. The port fails to receive the LCAP packets. The port is in the self-loop state. Other known reasons.

Handling Procedure Step 1 View the LAG_VC_PORT_FAIL alarm on the T2000, and confirm the board where the

LAG_VC_PORT_FAIL alarm is generated. Confirm the number of the VCG port where the LAG_VC_PORT_FAIL alarm is generated according to Parameter 2 and Parameter 3, and confirm the cause of the LAG_VC_PORT_FAIL alarm at the port according to Parameter 4.

Step 2 If the value of Parameter 4 is 0x01, it indicates that the link becomes faulty or fails. Check the link state of all the ports. Rectify the link fault of the port, and then check whether the LAG_VC_PORT_FAIL alarm is cleared.


On the T2000, check whether the LAG is configured at the opposite end, and check whether the port connected to the faulty VCG port is added to the LAG at the opposite end. Make sure the LAG is correctly configured, and then check whether the LAG_VC_PORT_FAIL alarm is cleared.

If the LAG_VC_PORT_FAIL alarm persists, check whether the local port transmits packets. If both ends can normally transmit and receive packets, check whether the LAG_VC_PORT_FAIL alarm is cleared.



Step 4 If the value of Parameter 4 is 0x04, it indicates that the link of the port is configured into a loop. Modify the link configuration, and then check if the LAG_VC_PORT_FAIL alarm is cleared.

Step 5 If the value of Parameter 4 is 0x05, find out the cause according to the networking environment, and then check whether the LAG_VC_PORT_FAIL alarm is cleared.

----End


3.66 LCAS_FOPR

Description The LCAS_FOPR is an alarm indicating the failure of the LCAS protocol in the receive direction. When the sink end of the LCAS module detects abnormalities, the LCAS negotiation is unavailable or incorrect and this alarm occurs.

Attribute




Name Meaning



Indicates the number of the VCTRUNK where the alarm occurs. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.

Impact on System When the LCAS_FOPR alarm occurs, it indicates that the protocol state machine in the receive direction is in confusion. The negotiation may be abnormal.




Possible Causes The downstream VCG receives repeated sequence numbers due to wrong configurations

or link bit errors. The LCAS function of the opposite VCG is disabled. The downstream VCG simultaneously receives the FIXED and other LCAS control

bytes due to wrong configurations or link bit errors. The cross-connection is incorrectly bound.

Handling Procedure Step 1 View the LCAS_FOPR alarm on the T2000 and confirm the relevant VCTRUNK according

to the alarm parameters.

Step 2 Check whether the LCAS protocol is enabled at the opposite end. If not, enable the LCAS protocol at the opposite end. Check whether the alarm is cleared.

Step 3 If the alarm persists, check whether the configurations are correct. Especially, check whether the cross-connection is bound correctly. If not, modify the wrong configurations. Check whether the alarm is cleared.

Step 4 If the alarm persists, disable and then enable the LCAS function at both ends. Check whether the alarm is cleared.

----End


3.67 LCAS_FOPT

Description The LCAS_FOPT is an alarm indicating the failure of the LCAS protocol in the transmit direction. When the source end of the LCAS module detects abnormalities, the LCAS negotiation is unavailable or incorrect.

Attribute






Name Meaning




Impact on System When the LCAS_FOPT alarm occurs, it indicates that the protocol state machine in the transmit direction is in confusion. The negotiation may be abnormal.

Possible Causes There is the persistent and unexpected MST due to wrong configurations or link bit errors. For example, the member that transmits IDLE always receives MST=OK.

Handling Procedure Step 1 View the LCAS_FOPT alarm on the T2000 and confirm the relevant VCTRUNK according


Step 2 Check whether the service cross-connection of the VCTRUNK is bound correctly. If not, modify the wrong configurations. Check whether the alarm is cleared.

----End


3.68 LCAS_PLCR

Description The LCAS_PLCR is an alarm indicating partial loss of capacity in the LCAS receive direction. When the LCAS function of the VCTRUNK is enabled, in the receive direction, the number of paths that carry load is less than the number of paths configured and is not zero.

Attribute


Minor Service alarm





Name Meaning




Impact on System When the LCAS_PLCR alarm occurs, it indicates that the available bandwidth in the receive direction is reduced. The services are not interrupted.

Possible Causes Bidirectional services are not configured. The number of members in the upstream of the opposite end is less than that in the

downstream of the local end. The path communication fails because the cross-connection is wrong or the physical link

is improperly connected.

Handling Procedure Step 1 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear

these alarms first. Check whether the alarm is cleared.

Step 2 Ensure that the physical link is available. Check whether bidirectional services are configured. If not, configure bidirectional services.

Step 3 If the alarm persists, check on the T2000 whether the number of downstream timeslots bound with the VCTRUNK at the local end is consistent with that of upstream timeslots bound with the VCTRUNK at the opposite end. If not, increase or reduce the timeslots to make the number of the timeslots at both ends consistent. Check whether the alarm is cleared.

Step 4 If the alarm persists, check whether the cross-connection is bound from the transmit direction to the opposite end. If not, re-bind the cross-connection. Check whether the alarm is cleared.

Step 5 If the alarm persists, maybe the wait-to-restore (WTR) time is too long and the members are still not restored. Check the WTR time. Wait for the WTR time, and then check whether the alarm is cleared.

Step 6 If the alarm persists, disable and then enable the LCAS function of the VCTRUNK. Check whether the alarm is cleared.

Step 7 If the alarm persists, delete and then re-bind all the physical paths of the VCTRUNK. Check whether the alarm is cleared.

Step 8 If the alarm persists, perform a cold reset for the board, or remove and insert the board.



----End


3.69 LCAS_ PLCT

Description The LCAS_PLCT is an alarm indicating partial loss of capacity in the LCAS transmit direction. When the LCAS function of the VCTRUNK is enabled, in the transmit direction, the number of paths that carry load is less than the number of paths configured and is not zero.

Attribute


Minor Service alarm


Name Meaning




Impact on System When the LCAS_PLCT alarm occurs, it indicates that the available bandwidth in the transmit direction is reduced. The services will lose packets when the actual service traffic is larger than the available bandwidth in the transmit direction.

Possible Causes Bidirectional services are not configured. The number of members in the downstream of the opposite end is less than that in the

upstream of the local end. The path communication fails because the cross-connection is wrong or the physical link

is improperly connected.




Handling Procedure Step 1 View the LCAS_PLCT alarm on the T2000 and confirm the relevant VCTRUNK according


Step 2 Check whether the LCAS_PLCR alarm is present at the opposite station. If yes, clear the LCAS_PLCR alarm first. Check whether the alarm is cleared.

Step 3 If the alarm persists, check whether bidirectional services are configured. If not, configure bidirectional services. Check whether the alarm is cleared.

Step 4 If the alarm persists, check on the T2000 whether the number of upstream timeslots bound with the VCTRUNK at the local end is consistent with that of downstream timeslots bound with the VCTRUNK at the opposite end. If not, increase or reduce the timeslots to make the number of the timeslots at both ends consistent. Check whether the alarm is cleared.

Step 5 If the alarm persists, the cross-connection is not bound from the transmit direction to the opposite end. Re-bind the cross-connection. The alarm is automatically cleared.

Step 6 If the alarm persists, maybe the wait-to-restore (WTR) time is too long and the members are still not restored. Check the WTR time. Wait for the WTR time, and then check whether the alarm is cleared.



Step 9 If the alarm persists, perform a cold reset for the board.

----End


3.70 LCAS_TLCR

Description The LCAS_TLCR is an alarm indicating the total loss of capacity in the LCAS receive direction. When the LCAS function of the VCTRUNK is enabled, in the receive direction, the number of paths that carry load is zero, whereas the number of paths configured is not zero.

Attribute


Minor Service alarm




Name Meaning




Impact on System When the LCAS_TLCR alarm occurs, it indicates that the available bandwidth in the receive direction is reduced to zero. The services in the receive direction are interrupted.

Possible Causes Bidirectional services are not configured. The upstream of the opposite end is not bound with members. The path communication fails because the cross-connection is wrong or other alarms are

present.

Handling Procedure Step 1 View the LCAS_TLCR alarm on the T2000 and confirm the relevant VCTRUNK according


Step 2 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear these alarms first. Check whether the alarm is cleared.

Step 3 Check whether bidirectional services are configured. If not, configure bidirectional services. Check whether the alarm is cleared.

Step 4 If the alarm persists, check whether the upstream of the opposite end is bound with timeslots. If not, bind the timeslots in the corresponding direction. Check whether the alarm is cleared.

Step 5 If the alarm persists, the cross-connection is not bound from the transmit direction to the local end. Re-bind the cross-connection. The alarm is automatically cleared.



Step 8 If the alarm persists, perform a cold reset for the board, or remove and insert the board.

----End





3.71 LCAS_TLCT

Description The LCAS_TLCT is an alarm indicating total loss of capacity in the LCAS transmit direction. When the LCAS function of the VCTRUNK is enabled, in the transmit direction, the number of paths that carry load is zero, whereas the number of paths configured is not zero.

Attribute


Minor Service alarm


Name Meaning




Impact on System When the LCAS_TLCT alarm occurs, it indicates that the available bandwidth in the transmit direction is reduced to zero. The services in the transmit direction are interrupted.

Possible Causes The downstream of the opposite end is not bound with members. The path communication fails because the cross-connection is wrong or other alarms are

present.

Handling Procedure Step 1 View the LCAS_TLCT alarm on the T2000 and confirm the relevant VCTRUNK according




Step 2 Check whether the LCAS_TLCR alarm is present at the opposite station. If yes, clear the LCAS_TLCR alarm first. Check whether the alarm is cleared.

Step 3 Check whether there are other alarms such as the AIS, LOP, UNEQ, and LOM. If yes, clear these alarms first. Check whether the alarm is cleared.

Step 4 If the alarm persists, check whether the downstream of the opposite end is bound with timeslots. If not, bind the timeslots in the corresponding direction. Check whether the alarm is cleared.

Step 5 If the alarm persists, check whether the cross-connection is correctly bound from the transmit direction to the opposite end. If not, re-bind the cross-connection. Check whether the alarm is cleared.



Step 8 If the alarm persists, perform a cold reset for the board.

----End


3.72 LINK_ERR

Description The LINK_ERR is an alarm of incorrect data link. This alarm occurs when the Ethernet connection is incorrect and the port negotiation fails.

Attribute




Name Meaning





Name Meaning


Indicates the port number of the board. Parameter 2 is higher byte, and Parameter 3 is the lower byte.

Impact on System When the LINK_ERR alarm occurs during the data transmission, the network port negotiation fails. The data cannot be received and the services are interrupted.

Possible Causes The working modes of optical interfaces at the transmit and receive ends are inconsistent.

Hence, the negotiation fails. The link is faulty. The electrical cable, fiber connection, or opposite equipment is faulty.

Handling Procedure Step 1 View the LINK_ERR alarm on the T2000 to confirm the relevant board. According to

Parameter 1, confirm the specific portnumber of the board.

Step 2 Check whether the working mode of the local port is consistent with that of the port at the opposite station. If not, modify it and then check whether the LINK_ERR alarm is cleared.

Step 3 If the alarm persists, check whether the electrical cable or fiber connection is faulty. If yes, fix the electrical 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 board at the opposite station, and then check whether the alarm is cleared.

Step 5 If the alarm persists, replace the board that generates the alarm. After you make sure that the working modes of the ports at the local and opposite stations are consistent, the LINK_ERR alarm is automatically cleared.

----End


3.73 LASER_SHUT

Description The LASER_SHUT is an alarm indicating that the laser of the board is shut down.



Attribute




Name Meaning


Impact on System When the LASER_SHUT alarm occurs, the services are interrupted.

Possible Causes The automatic laser shutdown (ALS) function is enabled on the T2000 or the Navigator.

Handling Procedure Step 1 After the ALS function is disabled, the LASER_SHUT alarm is automatically cleared.

----End


3.74 LOOP_ALM

Description The LOOP_ALM is a loopback alarm. This alarm occurs when service loopback is set.

Attribute







Name Meaning



Indicates the AU-4 path number. For example, Parameter 2 = 0x00 and Parameter 3 = 0x01. In this case, the LOOP_ALM alarm is reported from AU-4 path 1 of the board.

Parameter 4 Indicates the loopback type. The values are as follows:

0x00: Optical interface inloop 0x01: Optical interface outloop 0x02: Path inloop 0x03: Path outloop

Impact on System When the LOOP_ALM alarm occurs, it indicates that the system loopback is performed. In this case, if services are running in the optical interface or channel, the services are interrupted.

Possible Causes The line board loopback or the tributary board loopback is manually configured.

Handling Procedure Step 1 After you manually cancel the loopback configuration, the LOOP_ALM alarm is

automatically cleared.

----End




3.75 LP_UNEQ_VC3

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

Attribute




Name Meaning



Indicates the AU-4 path number.

Parameter 4 Indicates the number of the VC-3 lower order path. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01, Parameter 4 = 0x01. In this case, the LP_UNEQ_VC3 alarm is reported from VC-3 lower order path 1 of AU-4 path 1 for optical interface 1 on the board.

Impact on System The LP_UNEQ_VC3 alarm shows that no path services are loaded. If the service configuration is incorrect, and if the services on the PDH side are not accessed, the services may be interrupted.

Possible Causes The service type is incorrectly configured. The services on the PDH side are not accessed.

Handling Procedure Step 1 View the LP_UNEQ_VC3 alarm on the T2000, and then confirm the path number according





Step 2 Check whether the service type configuration is correct. After modifying the incorrect configuration and making sure that the services are correctly accessed on the PDH side, check whether the LP_UNEQ_VC3 alarm is cleared.

Step 3 If the alarm persists, check whether the property configuration of the relevant tributary board is correct. After you modify the incorrect configuration, the LP_UNEQ_VC3 alarm is automatically cleared.

----End


3.76 LP_RDI_VC3

Description The LP_RDI_VC3 is a remote defect indication in the VC-3 lower order path. If a board has detected that bit 5 of the G1 byte in the VC-3 lower order path is 1, the LP_RDI_VC3 alarm is reported.

Attribute




Name Meaning



Indicates the AU-4 path number. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.

Parameter 4 Indicates the number of the VC-3 lower order path. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01, Parameter 4 = 0x01. In this case, the LP_RDI_VC3 alarm is reported from VC-3 lower order path 1 of AU-4 path 1 for optical interface 1 on the board.



Impact on System When the LP_RDI_VC3 alarm occurs, the services at the local station are not affected. This alarm just shows that the services at the opposite end are interrupted.

Possible Causes The LP_RDI_VC3 alarm is an accompanying alarm. When the relevant path of a tributary board at the opposite station reports TU_AIS or TU_LOP alarm, it returns the LP_RDI_VC3 alarm to the local station, showing the TU_AIS or TU_LOP alarm is received at the opposite station.

Handling Procedure Step 1 After you clear the TU_AIS or TU_LOP alarm reported from the relevant path of a tributary

board at the opposite station, the LP_RDI_VC3 alarm is automatically cleared.

----End


3.77 LP_SLM_VC3

Description The LP_SLM_VC3 is a signal label mismatch alarm in the VC-3 lower order path. If a board has detected that the signal label mismatch event occurs in the C2 byte, the LP_SLM_VC3 alarm is reported.

Attribute




Name Meaning







Name Meaning

Parameter 4 Indicates the number of the VC-3 lower order path. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01, Parameter 4 = 0x01. In this case, the LP_SLM_VC3 alarm is reported from VC-3 lower order path 1 of AU-4 path 1 for optical interface 1 on the board.

Impact on System The system is not affected.

Possible Causes The type of the received signals does not match that of the signals to be received. That is,

the signal label byte C2 in the lower order path is inconsistent with the received C2 byte. The service type is incorrectly configured.

Handling Procedure Step 1 View the LP_SLM_VC3 alarm on the T2000, and then confirm the path number according to

the alarm parameters.

Step 2 Check whether the signal label byte in the lower order path of the tributary board at the opposite station is consistent with that in the lower order path of the line board at the local station. If not, modify it, and then check whether the LP_SLM_VC3 alarm is cleared.

Step 3 If the alarm persists, check whether the service configuration of the path is correct. After modifying the incorrect configuration, check whether the LP_SLM_VC3 alarm is cleared.

Step 4 If the alarm persists, replace the line board at the local station.

Step 5 If the alarm persists, replace the tributary board at the opposite station.

----End


3.78 LP_TIM_VC3

Description The LP_TIM_VC3 is a trace identifier mismatch alarm in the VC-3 lower order path. If a board has detected that the J1 byte does not match, the LP_TIM_VC3 alarm is reported.



Attribute




Name Meaning




Parameter 4 Indicates the number of the VC-3 lower order path. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01, Parameter 4 = 0x01. In this case, the LP_TIM_VC3 alarm is reported from VC-3 lower order path 1 of AU-4 path 1 for optical interface 1 on the board.

Impact on System The system is not affected.

Possible Causes The received J1 byte does not match that to be received. The service cross-connection configuration is incorrect.

Handling Procedure Step 1 Check whether the trace identifier configuration in the lower order path of the tributary board

at the opposite station is consistent with that in the lower order path of the line board at the local station. If not, modify the configuration, and then check whether the LP_TIM_VC3 alarm is cleared.

Step 2 Check whether the service cross-connection configuration is correct. After modifying the incorrect configuration, check whether the LP_TIM_VC3 alarm is cleared.

Step 3 If the alarm persists, replace the line board at the local station.

Step 4 If the alarm persists, replace the tributary board at the opposite station.

----End





3.79 LSR_COOL_ALM

Description The LSR_COOL_ALM is an alarm indicating that the cooling current of the laser crosses the threshold.

Attribute




Name Meaning


Impact on System When the LSR_COOL_ALM alarm occurs, the laser is faulty. Consequently, the services are interrupted.

Possible Causes The ambient temperature is extremely high. The laser is faulty.

Handling Procedure Step 1 Check whether the ambient temperature is extremely high. If yes, decrease it to a proper value

for the equipment to work well, and then check whether the LSR_COOL_ALM alarm is cleared.

Step 2 If the alarm persists, the laser may be faulty. Replace the board that generates the alarm, and then check whether the LSR_COOL_ALM alarm is cleared.

----End




3.80 LSR_NO_FITED

Description The LSR_NO_FITED is an alarm indicating that the laser is not installed.

Attribute




Name Meaning




Impact on System When the optical interface is not installed with the optical module, the data cannot be transmitted.

Possible Causes The enabled optical interface is not installed with the optical module. The optical module is faulty.

Handling Procedure Step 1 View the LSR_NO_FITED alarm on the T2000 to confirm the relevant board.

Step 2 After you replace the board, the LSR_NO_FITED alarm is automatically cleared.

----End





3.81 LSR_WILL_DIE

Description The LSR_WILL_DIE is an alarm indicating that the laser is going to stop working. This alarm occurs when the laser is unavailable.

Attribute




Name Meaning

Parameter 1 Indicates the optical interface number or the port number of the board that generates the alarm.



Impact on System When the LSR_WILL_DIE alarm occurs, bit errors occur in the services. If the board is not replaced in a timely manner, the services are interrupted after the laser is damaged.

Possible Causes The laser is aged. The detection circuit of the board is faulty.

Handling Procedure Step 1 View the LSR_WILL_DIE alarm on the T2000 to confirm the relevant board.

Step 2 Replace the board that generates the LSR_WILL_DIE alarm.

----End




3.82 LTI

Description The LTI is an alarm indicating that all clock sources, except the internal clock of the equipment, are lost.

Attribute



Parameters None.

Impact on System When all clock sources are lost, the equipment uses its own clock as the working clock. A large quantity of pointer justifications and even a few bit errors might be generated, due to the degrade of clock quality. In this case, the service quality is affected.

Possible Causes The configuration of clock tracing relations is incorrect. All configured clock sources fail. The clock board is faulty.

Handling Procedure Step 1 Check the clock synchronization configuration to confirm whether a clock source that does

not exist is configured to be traced. If the configuration is incorrect, modify the configuration and download it again.

Step 2 If the configuration is correct, check whether the traced clock source is functioning properly. If not, handle the relevant problem. If a line clock source is configured to be traced but the line has a loss-of-signal alarm, handle the loss-of-signal alarm. If an external clock source is configured to be traced, check whether the external clock source is normal, and whether the external clock cable is well connected.

Step 3 If the traced clock source is normal, the clock board is faulty. In this case, contact Huawei technical support engineers to handle the problem.

----End





3.83 M_S_SW

Description The M_S_SW is an alarm indicating that the active/standby switching occurs on the cross-connect boards or on the clock boards.

Attribute



Parameters None.

Impact on System The cross-connect boards and the clock boards adopt the 1+1 protection scheme. If the active/standby switching is caused by the board out-of-position status or by a board fault, further 1+1 protection becomes unavailable. As a result, the automatic switching of clock boards or cross-connect boards is affected, and the system stability is affected.

Possible Causes The cross-connect board or the clock board is removed and inserted again. The cross-connect board or the clock board is faulty. A command is manually issued to force the active/standby switching.

Handling Procedure Step 1 On the T2000, check whether the alarmed cross-connect board or clock board is out of

position, or whether the alarmed board is faulty. If yes, properly insert the board or replace the faulty board.

Step 2 On the T2000, check whether a forced switching command is manually issued. If yes, release the forced switching for the cross-connect boards or for the clock boards.

Step 3 If the active/standby switching is not caused by any of the previously mentioned problems, contact Huawei technical support engineers.

----End




3.84 MASTER_ERR

Description The MASTER_ERR is an alarm indicating that the alarmed board detects a fault of the active cross-connect board, active clock board, or active SCC board.

Attribute




Name Meaning

Parameter 1 Indicates the type of the faulty active board. 0x00: Active higher order cross-connect board 0x01: Active clock board 0x02: Active SCC board

Parameter 2 When the value of Parameter 1 is 0x00, Parameter 2 indicates the faulty bus number. When the value of Parameter 1 is 0x01 or 0x02, the value of Parameter 2 is always 0x01.

Parameter 3 Indicates the slot number of the active board.

Impact on System Every service board of the OptiX OSN 9500 can select its own cross-connect board, clock board, and SCC board. When the MASTER_ERR alarm occurs, therefore, the active/standby protection of the cross-connect board, clock board, or SCC board is lost.

If the alarmed board also reports the SLAVE_BAD alarm, and the value of MASTER_ERR Parameter 3 is equal to the value of SLAVE_BAD Parameter 3, the services on the alarmed board are interrupted.




If the alarmed board does not report the SLAVE_BAD alarm, or if the alarmed board does report the SLAVE_BAD alarm at the same time but the slot number parameters of the MASTER_ERR and SLAVE_BAD alarms are different, the services are not affected. In this case, the alarmed board only loses the active/standby protection options of the cross-connect boards, clock boards, or SCC boards.

Possible Causes Bit errors are generated in the bus of the active cross-connect board from which the

alarmed board receives signals. The active clock board, from which the alarmed board receives signals, has a bad clock

quality or has an overhead bus fault. The alarmed board detects a fault of the active SCC board.

Handling Procedure Step 1 Locate the faulty board according to the alarm parameters.

Step 2 Replace the faulty board.

Step 3 If the MASTER_ERR alarm persists, contact Huawei technical support engineers.

----End

Related Information Even if the MASTER_ERR alarm is cleared after the board replacement, you need to report this alarm to Huawei technical support engineers.

3.85 MBUS_OFFLINE

Description The MBUS_OFFLINE is an alarm indicating that the MBUS module on the board is faulty.

Attribute






Name Meaning

Parameter 1 0x01: The MBUS_OFFLINE alarm is detected by the first MBUS module of the board.

0x02: The MBUS_OFFLINE alarm is detected by the second MBUS module of the board.

Impact on System When the MBUS module is faulty, the EMPU board cannot monitor the electromechanical features (such as temperature and voltage) of the alarmed board.

Possible Causes The MBUS module is faulty.

Handling Procedure Step 1 Acknowledge the MBUS_OFFLINE alarm in the alarm management window of the T2000. If

the alarm persists, contact Huawei technical support engineers to replace the faulty board.

----End


3.86 MBUS_SERIAL

Description The MBUS_SERIAL is an alarm indicating that the alarmed board detects the serial port communication failure of its own MBUS module.

Attribute







Name Meaning

Parameter 1 If the MBUS_SERIAL alarm is reported by the EMPU board, Parameter 1 is meaningless. If the MBUS_SERIAL alarm is reported by another board, the meanings of Parameter 1 are as follows.

0x01: The MBUS_SERIAL alarm is detected by the first MBUS module of the board.

0x02: The MBUS_SERIAL alarm is detected by the second MBUS module of the board.

Impact on System If the MBUS_SERIAL alarm is reported by the EMPU board, the EMPU board cannot

monitor the electromechanical features (such as temperature and voltage) of other boards.

If the MBUS_SERIAL alarm is not reported by the EMPU board, the EMPU board cannot monitor the electromechanical features (such as temperature and voltage) of the alarmed board.

Possible Causes The alarmed board has a hardware failure.

Handling Procedure Step 1 Replace the faulty board.

----End


3.87 MBUS_UPDATE_FAIL

Description The MBUS_UPDATE_FAIL is an alarm indicating that the MBUS module software of the alarmed board fails to be upgraded.

Attribute






Name Meaning


Impact on System Currently the MBUS module can be upgraded in two ways: broadcast upgrade and point-to-point upgrade. If the broadcast upgrade fails, perform the point-to-point upgrade for the alarmed board. If the point-to-point upgrade also fails, the EMPU board cannot monitor the electromechanical features (such as temperature and voltage) of other boards, and the power-on and power-off of other boards cannot be controlled through the EMPU board.

Possible Causes The MBUS software upgrade fails.

Handling Procedure Step 1 If the broadcast upgrade fails, perform the point-to-point upgrade for the alarmed board.

Step 2 If the point-to-point upgrade also fails, contact Huawei technical support engineers to handle the problem. Replace the board that reports the MBUS_UPDATE_FAIL alarm.

----End


3.88 MS_AIS

Description The MS_AIS is an indication alarm in the multiplex section. When the last three bits of the K2 byte are 111 in five frames consecutively received on the receive side of the local optical interface, the MS_AIS alarm is reported. This alarm shows that the signals in the multiplex section corresponding to the optical interface that reports the alarm are useless.

Attribute







Name Meaning

Parameter 1 Indicates the optical interface at which the alarm occurs.


Parameter 3 The value is always 0x01 and this parameter is meaningless.

Impact on System When the MS_AIS alarm occurs, the services are interrupted.

After the MS_AIS occurs, the board automatically returns the MS_RDI alarm to the opposite station. Consequently, the opposite station reports the MS_RDI alarm.

Possible Causes The transmit unit at the opposite station is faulty.

Handling Procedure Step 1 According to the alarm information of the opposite station, check whether the line system,

clock system and cross-connect system of the opposite station are faulty. If yes, remove the fault of the opposite station.

Step 2 If the MS_AIS alarm persists, contact Huawei technical support engineers.

----End


3.89 MS_APS_INDI_EX

Description The MS_APS_INDI_EX is an extended indication alarm of the MSP switching state. This alarm occurs when the service is in the switching state.



Attribute




Name Meaning



Parameter 2 Indicates the MSP group ID. For a linear MSP, the value range is 0x01–0x38 (1–40). For a ring MSP, the value range is 0x01–0x0C (1–12).

Parameter 3 Indicates the number of the board slot where the protection switching occurs.

Parameter 4 Indicates the number of the optical interface where the protection switching occurs.

Impact on System If a fiber cut or another fault occurs after the MS_APS_INDI_EX alarm, the services are interrupted.

Possible Causes The possible causes of the MS_APS_INDI_EX alarm are as follows:

An external switching command is issued. There is a fiber cut. The board is faulty.

Handling Procedure Step 1 View the MS_APS_INDI_EX alarm on the T2000. According to the alarm parameters,

confirm the slot number and optical interface number related to the MSP board where the protection switching occurs.




Step 2 Check whether the MSP is in a state of manual switching, forced switching, or lockout of switching. If the MSP is in a switching state, clear the switching, and then the alarm is automatically cleared. For details, refer to "Performing Protection Switching for an MSP Ring."

Step 3 If the MSP is in an automatic switching state, do as follows:

Make sure that the fibers connected to the service board of the MSP are not broken. Fix the broken fibers and then check whether the alarm is cleared.

Make sure that the service board of the MSP is not faulty. Replace the relevant service board and then check whether the alarm is cleared.

Make sure that the cross-connect board of the MSP is not faulty. Replace the relevant cross-connect board and then check whether the alarm is cleared.

----End


3.90 MS_CROSSTR

Description The MSAD_CROSSTR is an alarm indicating that the MS adaptation performance crosses the threshold.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the number of the optical interface at which the MS adaptation performance crosses the threshold.

Parameter 2 , Parameter 3

Indicates the number of the path in which the MS adaptation performance crosses the threshold.



Name Meaning


The lower six bits together with Parameter 5 indicate the performance event ID


Impact on System The service quality of the board that generates the alarm declines. The services on the board that generates the alarm are interrupted.

Possible Causes The ring clock fails.

Handling Procedure Step 1 Reset a clock source to clear the fault.

----End


3.91 MS_RDI

Description The MS_RDI is a remote defect indication in the multiplex section. When the last three bits of the K2 byte are 110 in five frames consecutively received on the receive side of the local optical station, the MS_RDI alarm is reported. When the opposite station generates the MS_AIS alarm, it returns the alarm to the local station.

Attribute







Name Meaning

Parameter 1 Indicates the actual optical interface number of the board at the local station.



Impact on System When the MS_RDI alarm occurs, the local station is not affected. This alarm just shows that the services at the opposite station are interrupted.

Possible Causes The opposite station has received an alarm, such as the R_LOS, R_LOC, R_LOF,

MS_AIS, B2_EXC or B2_SD. The receive unit at the opposite station is faulty. The transmit unit at the local station is faulty.

Handling Procedure Step 1 On the T2000, check whether any alarm, such as the R_LOS, R_LOC, R_LOF, MS_AIS,

B2_EXC or B2_SD, is detected for the relevant line board at the opposite station. If yes, take priority to clear it, and then check whether the MS_RDI alarm is cleared.

Step 2 If the alarm persists, check whether any board at the local station is faulty. If yes, perform a cold reset on the relevant line board. Then check whether the MS_RDI alarm is cleared.

If the services travel through the board are not configured with protection, the services are interrupted after the cold reset of the board.

Step 3 If the alarm persists, replace the relevant line board at the local station, and then check whether the MS_RDI alarm is cleared.

Step 4 If the alarm persists, check whether any board at the opposite station is faulty. If yes, perform a cold reset on the relevant line board, and then check whether the MS_RDI alarm is cleared.




Step 5 If the alarm persists, replace the relevant board at the opposite station, and then check whether the MS_RDI alarm is cleared.

----End


3.92 MS_REI

Description The MS_REI is an indication alarm that indicates bit errors occur at the remote end of the multiplex section. When the receive side of the local optical station receives the M1 byte, which shows that the number of block bit errors detected by BIP-N x 24 (B2) at the opposite station, the MS_REI alarm is reported.

Attribute


Warning Communication alarm


Name Meaning







Impact on System When the MS_REI alarm occurs, the number of B2 bit errors received at the opposite station is beyond the specified value range. The services at the local station are not affected, but the service quality at the opposite station is degraded.

Possible Causes The number of B2 bit errors received at the opposite station is beyond the specified value range.

Handling 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


3.93 MSAD_CROSSTR

Description The MSAD_CROSSTR is an alarm indicating that the MS adaptation performance crosses the threshold.

Attribute


Minor Service alarm


Name Meaning

Parameter 1 Indicates the number of the optical interface at which the MS adaptation performance crosses the threshold.


Indicates the number of the path in which the MS adaptation performance crosses the threshold.



Name Meaning




Impact on System The service quality of the board that generates the alarm declines. The services on the board that generates the alarm are interrupted.

Possible Causes The ring clock fails.

Handling Procedure Step 1 Reset a clock source to clear the fault.

----End


3.94 MSSW_DIFFERENT

Description The MSSW_DIFFERENT is an alarm indicating that the NE software versions on the working and protection SCC boards are inconsistent.

Attribute








Name Meaning

Parameter 1 0x01: Files in the FLASH 0x02: Software that is running currently


Indicates the number of the inconsistent file on the SCC boards.

Parameter 4 Indicates the alarm causes. 0x04: The versions of the files in the working and the protection areas of a single SCC board are inconsistent.

0x08: The file versions of the working SCC and those of the protection SCC are inconsistent.

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

Parameter 5 0xff: This parameter is currently not used.

Impact on System If the software versions of the working SCC and the protection SCC are inconsistent, the

active/standby switching of the system is affected. If no NE software exists on the FLASH, the system cannot reboot after the system is

powered off or reset.

Possible Causes The version of the software that is currently running on the working SCC is inconsistent

with hat on the protection SCC. The software versions in the working and the protection areas (OFS1 and OFS2) are

inconsistent. On the working and protection SCC boards, no file named after the board exists under

the peer board directory.

Handling Procedure Step 1 Contact Huawei engineers to reload the mapping software.

----End




3.95 NEBD_XC_DIF

Description The NEBD_XC_DIF is an alarm indicating that the cross-connection data on the SCC board is inconsistent with the cross-connection data on the cross-connect board and the line board.

Attribute




Name Meaning

Parameter 1 Indicates the number of the slot where the cross-connection data is inconsistent.

Parameter 2 Indicates the type of inconsistent services. 0x01: Higher order services 0x02: Lower order services

Parameter 3 0xff: The chip number needs not be specified. 0x01–0x16: Each value indicates a chip number.


The values are always 0xff, and these parameters are meaningless.

Impact on System The NEBD_XC_DIF alarm causes service interruption.

Possible Causes The NE itself has an error in implementing the cross-connections.

Handling Procedure Step 1 Contact Huawei technical support engineers to handle the problem.

----End





3.96 NESF_LOST

Description The NESF_LOST is an alarm indicating that the NE software is lost.

Attribute




Name Meaning

Parameter 1 Indicates the software file that is lost.

Impact on System If the NE software is not reset, the services are not affected. If the NE software is reset, the services on the entire NE are interrupted, and the user

cannot perform any operations on the NE.

Possible Causes The software on the SCC board is lost or damaged.

Handling Procedure Step 1 If the NESF_LOST occurs, contact Huawei technical support engineers to load the software.

Step 2 If the NESF_LOST alarm persists, replace the alarmed SCC board.

----End




3.97 NESTATE_INSTALL

Description The NESTATE_INSTALL is an alarm indicating that the NE is in the installing state.

Attribute



Parameters None.

Impact on System When the NESTATE_INSTALL alarm occurs, the configuration data of the NE is unavailable, and the NE cannot function.

Possible Causes The NE is in the initializing state, and thus is configured with no data. During the data downloading from the T2000 to the NE, the update of the NE database is

unsuccessful. If only one SCC exists, replace the SCC. The database on the SCC is faulty.

Handling Procedure Step 1 If the NESTATE_INSTALL alarm occurs during a new deployment, the alarm will be cleared

after the NE is properly configured.

Step 2 If the alarm occurs in other cases, contact Huawei technical support engineers to handle the problem.

----End





3.98 NO_BD_PARA

Description The NO_BD_PARA is an alarm indicating that the board parameters are not set. This alarm occurs when the system cannot detect the parameter file of the board, that is, when the system cannot detect the optical module parameters.

Attribute




Name Meaning




Impact on System After the NO_BD_PARA alarm occurs, the services are interrupted if the laser fails to be initialized.

Possible Causes The laser parameter list is not downloaded. The board parameters are not set. The set board parameter is lost.

Handling Procedure Step 1 View the NO_BD_PARA alarm on the T2000 to confirm the relevant board.

Step 2 Perform a cold reset on the board. Then, check whether the NO_BD_PARA alarm is cleared.




----End


3.99 NO_BD_SOFT

Description The NO_BD_SOFT is an alarm indicating that the board has no software.

Attribute




Name Meaning

Parameter 1 Indicates the type of the software loss.

Impact on System If a warm reset occurs on the board, the board enters the BIOS state. In this case, the

existing services on the board are not interrupted, but the board cannot receive any information from the SCC.

If a cold reset occurs on the board, the existing services (if any) on the board are interrupted.

Possible Causes The software of the alarmed board is lost. The alarmed board has a hardware failure.

Handling Procedure Step 1 If the NO_BD_SOFT alarm occurs, contact Huawei technical support engineers to load the

software.

Step 2 If the alarm persists after the software is loaded, replace the alarmed board.




----End


3.100 NO_LSR_PARA_FILE

Description The NO_LSR_PARA_FILE is an alarm indicating that the laser parameter file of the line board does not exist or is damaged.

Attribute




Name Meaning

Parameter 1 Indicates the optical interface number of the faulty laser.

Impact on System When the laser parameter file of the line board does not exist or is damaged, the detected laser performance is incorrect. On the one hand, laser performance alarms might be mistakenly reported. On the other hand, alarms that should be reported might actually fail to be generated and reported.

Possible Causes The laser parameter file does not exist or is damaged.


----End




3.101 NODEID_MM

Description The NODEID_MM is an alarm indicating that the MSP node ID mismatch.

Attribute




Name Meaning


Parameter 2 to Parameter 5

0xff: reserved.

Impact on System When the NODEID_MM alarm occurs, the MSP switching fails. If the squelching is enabled, the squelching function also fails.

Possible Causes The possible cause of the NODEID_MM alarm is as follows:

The east and west node IDs configured for each node on the MSP ring do not match.

Handling Procedure Step 1 Check whether the data configuration of the MSP meets the following requirements:

The configured node IDs configured for any two NEs are not repeated. If node A is to the west of its adjacent node B, the local node ID of node A must be the

same as the west node ID of node B, and the local node ID of node B must be the same as the east node ID of node A.




Step 2 If the data configuration does not meet the above mentioned requirements, configure the data again according to the requirements.

Step 3 Restart the MSP protocol. View alarm on the T2000 to check whether the NODEID_MM alarm is cleared.

Step 4 If the alarm persists, contact Huawei engineers for troubleshooting.

----End


3.102 OH_ERR

Description The OH_ERR is an alarm indicating that bit errors are detected in the overhead bus between boards.

Attribute




Name Meaning

Parameter 1 If the OH_ERR alarm is reported by a service board, the meanings of Parameter 1 are as follows.

0x01: Bit errors are detected between the service board and the clock board in slot 45.

0x02: Bit errors are detected between the service board and the clock board in slot 46.

0x04: Bit errors are detected between the service board and the SCC board in slot 47.

0x08: Bit errors are detected between the service board and the SCC board in slot 48.

If the OH_ERR alarm is reported by the ESCC/JSCC/JSTG board, Parameter 1 indicates the slot number of the line board that has the communication failure.



Impact on System The OH_ERR alarm affects the communication of various system protocols. Consequently, the system is unavailable.

Possible Causes The line board, clock board, or SCC board is abnormal. The communication fails between the line board and the clock board, or between the line

board and the SCC board.


----End


3.103 OH_LOOP

Description The OH_LOOP is an alarm indicating that the overhead bytes of the equipment are looped back.

Attribute




Name Meaning

Parameter 1 Indicates the loopback mode. 0x01: Outloop 0x02: Clock board loopback 0x03: SCC board loopback

Parameter 2 Indicates the loopback type.




Impact on System The alarmed board or the SCC board loops back the overhead bytes related to communication and orderwire.

Possible Causes The overhead bytes are looped back at the line board. The overhead bytes are looped back at the SCC board.

Handling Procedure Step 1 Check whether overhead bytes are looped back. If yes, release the loopback.

----End


3.104 OOL

Description The OOL is an alarm indicating that the phase-locked loop is out of lock.

Attribute




Name Meaning

Parameter 1 Indicates the failed phase-locked loop.

Impact on System When the OOL alarm occurs, the phase-locked loop cannot lock on the input signals, and as a result the output clock signals are affected. This alarm may lower the quality of services or interrupt the services.



Possible Causes The board hardware of the phase-locked loop is damaged.


----End


3.105 OTH_BD_STATUS

Description The OTH_BD_STATUS is an alarm indicating that the higher order cross-connect board or clock board detects the out-of-position status of its paired board.

Attribute



Parameters None.

Impact on System The OTH_BD_STATUS alarm affects the active/standby switching function of the cross-connect boards or of the clock boards.

Possible Causes The paired board of the alarmed board is not in position.

Handling Procedure Step 1 Confirm the slot of the paired board, according to the alarmed board. Remove the paired

board and insert it again, and then check whether the alarm is cleared.

Step 2 If the alarm persists, replace the paired board.

----End




Related Information The OptiX OSN 9500 provides the 1+1 protection for the higher order cross-connect boards and for the clock boards.

The higher order cross-connect boards in slots 41 and 42 are paired boards.


The clock boards in slots 45 and 46 are paired boards.

3.106 OTH_HARD_FAIL

Description The OTH_HARD_FAIL is an alarm indicating that the higher order cross-connect board or clock board detects the failure of its paired board.

Attribute



Parameters None.

Impact on System When the paired board of the cross-connect board or clock board is faulty, the system uses the board that reports the OTH_HARD_FAIL alarm. This alarm does not affect services. However, the 1+1 protection of the higher order cross-connect boards or clock boards is affected, and the system stability is affected.

Possible Causes The paired board of the alarmed board is faulty.

Handling Procedure Step 1 Confirm the slot of the paired board, according to the alarmed board.

Step 2 Check whether the ejector levers on the front panel of the paired board are open. If yes, close the ejector levers.

Step 3 Contact Huawei technical support engineers to handle the problem.

----End



Related Information The OptiX OSN 9500 provides the 1+1 protection for the higher order cross-connect boards and for the clock boards.



The clock boards in slots 45 and 46 are paired boards.

3.107 OUT_PWR_ABN

Description The OUT_PWR_ABN is an alarm indicating that the output optical power is abnormal.

Attribute




Name Meaning


Impact on System When the OUT_PWR_ABN alarm occurs, the service transmission performance is affected. In the case of severe alarm, the services are interrupted.

Possible Causes The output optical power is extremely high or low. The board is faulty.

Handling Procedure Step 1 Replace the board that generates the OUT_PWR_ABN alarm.

----End





3.108 PATCH_ERR

Description The PATCH_ERR is an alarm indicating that the automatic patch loading fails.

Attribute



Parameters None.

Impact on System The functions of the patch does not exist or the bug corrected by the patch appears again.

Possible Causes If a patch is running before the system reboots, the NE automatically loads and runs this patch after the reboot. If any anomaly occurs at this time and thus the loading is failed, the PATCH_ERR alarm is reported.

Handling Procedure Step 1 Reload the patch file. If the PATCH_ERR alarm is still reported after the loading, download

the correct patch file and then load the patch.

----End


3.109 PATCH_NOT_CONFIRM

Description The PATCH_NOT_CONFIRM is an alarm indicating that a patch is not confirmed after it is activated.



Attribute




Name Meaning

Parameter 1 Indicates the number of the patch that is not confirmed.

Impact on System The active state of the patch is unstable. The board reset may cause the patch to be invalid and to be in the inactive state.

Possible Causes After a patch is activated, confirm whether to run or deactivate the patch after a certain period of time. Otherwise, the PATCH_NOT_CONFIRM alarm is reported. In this case, the functions of the patch disappear or the bug corrected by the patch appears again.

Handling Procedure Step 1 If you confirm that the patch runs normally, issue the command to run the patch in a timely

manner. After you confirm that the operation of the patch is abnormal, issue the command to deactivate the patch in a timely manner.

----End


3.110 PATCHFILE_NOTEXIST

Description The PATCHFILE_NOTEXIST is an alarm indicating that the patch file does not exist when the patch is automatically loaded.




Attribute



Parameters None.

Impact on System When the PATCHFILE_NOTEXIST alarm occurs, the functions of the patch do not exist or the bug corrected by the patch appears again.

Possible Causes If a patch is running before the NE reboots, the NE automatically loads and runs the patch after the reboot. If any patch file is lost at this time, the PATCHFILE_NOTEXIST alarm is reported.

Handling Procedure Step 1 Download the patch file again and then load it to the NE.

----End


3.111 PAUSE_ERROR

Description The PAUSE_ERROR is an alarm indicating that the JCOM board detects an error of its internal chip.

Attribute



Parameters None.



Impact on System The JCOM board is the system communication board. If the JCOM board has a hardware failure, the Ethernet communication of the system fails. The PAUSE_ERROR alarm does not affect existing services, but affects system functions such as the monitoring for the entire NE and the update of service configuration.



----End


3.112 POWER_ALM

Description The POWER_ALM is an alarm indicating that the voltage of the board power module is beyond the normal range.

Attribute




Name Meaning

Parameter 1 Indicates the power channel ID.

Parameter 2 Indicates the type of the voltage alarm. 0x01: Undervoltage 0x02: Overvoltage




Name Meaning

Parameter 3 0x01: The POWER_ALM alarm is detected by the first MBUS module of the board.

0x02: The POWER_ALM alarm is detected by the second MBUS module of the board.

Impact on System When the voltage of the board power module is beyond the normal range, the board might fail to function properly.

Possible Causes The input power supply is abnormal, and the voltage of the power module is beyond the

normal range. The power module of the alarmed board is abnormal. The JPBU board is not installed.

Handling Procedure Step 1 Check whether the JPBU board is installed and configured on the NE. If not, add the JPBU

board.

Step 2 If the alarm persists after the JPBU board is added, replace the alarmed board.

----End


3.113 POWER_FAIL

Description The POWER_FAIL is an alarm indicating that the SCC board reports a battery power failure.

Attribute






Name Meaning

Parameter 1 Indicates the power channel ID.

Impact on System When the SCC board is being powered on, the battery power supply is not required. Therefore, if the POWER_FAIL alarm is generated during the running of the equipment, the services are not affected. If the SCC board is powered off when the POWER_FAIL alarm occurs, however, the information recorded in the SCC board might be lost.

Possible Causes The battery power supply of the SCC board has a lower power or is faulty.


----End


3.114 POWER_SWITCH

Description The POWER_SWITCH is an alarm indicating that, after the board power module fails, the power supply is switched to the JPBU board.

Attribute







Name Meaning

Parameter 1 Indicates the number of the power supply channel where the switching occurs.

Parameter 2 0x01: The POWER_SWITCH alarm is detected by the first MBUS module of the board.

0x02: The POWER_SWITCH alarm is detected by the second MBUS module of the board.

Impact on System The power backup board JPBU is able to provide power supply protection for only one board. If the power of the alarmed board is supplied by the JPBU board, the JPBU board fails to provide power supply protection for other boards, and as a result the system stability is affected. Therefore, the POWER_SWITCH alarm must be handled as soon as possible.

Possible Causes After the power module of the alarmed board fails, the power supply is switched to the JPBU board.


----End


3.115 PUM_BCM_ALM

Description The PUM_BCM_ALM is an alarm indicating that the bias current of the pump laser crosses the threshold.



Attribute




Name Meaning



Indicates the serial number of the laser. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.

Impact on System When the bias current of the pump laser on the optical amplifier board crosses the threshold, the laser becomes instable. As a result, the services have bit errors and can even be interrupted. The PUM_BCM_ALM alarm must be handled immediately.

Possible Causes The optical amplifier board has a hardware failure.

Handling Procedure Step 1 Perform a cold reset for the alarmed optical amplifier board, or remove the alarmed board and

then insert it again. Check whether the alarm is cleared.

Step 2 If the alarm persists, replace the alarmed optical amplifier board.

----End





3.116 PUM_TEM_ALM

Description The PUM_TEM_ALM is an alarm indicating that the board pump laser detects the threshold-crossing of the ambient temperature.

Attribute




Name Meaning


Parameter 2 Indicates the serial number of the laser. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.

Impact on System The PUM_TEM_ALM alarm affects the laser performance.

Possible Causes The ambient temperature is too high or too low. The board has a hardware failure.

Handling Procedure Step 1 Check the air conditioner in the equipment room, to make sure that the ambient temperature is

between 5ºC and 45ºC.

Step 2 If the PUM_TEM_ALM persists even when the ambient temperature is between 5ºC and 45ºC, reset the alarmed board, or remove the alarmed board and insert it again. Check whether the alarm is cleared.


----End




3.117 PUMP_COOL_EXC

Description The PUMP_COOL_EXC is an alarm indicating that the cooling current of the pump laser crosses the threshold.

Attribute




Name Meaning



Indicates the serial number of the laser. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.

Impact on System The services that pass through the alarmed board are impaired or interrupted.

Possible Causes The ambient temperature is too high. The board has a hardware failure.


lower than 45ºC.

Step 2 If the PUMP_COOL_EXC alarm persists even when the ambient temperature is lower than 45ºC, replace the faulty board.

----End





3.118 PWR_LOW

Description The PWR_LOW is an alarm indicating that the SCC board detects a power voltage lower than the normal voltage.

Attribute




Name Meaning

Parameter 1 Indicates the type of undervoltage.

Impact on System When the power voltage of the SCC board is abnormal, the proper functioning of the SCC board is affected. Hence, the PWR_LOW alarm must be handled as soon as possible.

Possible Causes The power module is faulty. The SCC board is faulty.


----End




3.119 PWR_LOW_PROTECTED

Description The PWR_LOW_PROTECTED is an alarm indicating that the system enters into the lower voltage protection mode.

Attribute



Parameters None.

Impact on System The NE cannot function properly, and the services are interrupted.

Possible Causes The voltage of the equipment power supply is too low.

Handling Procedure Step 1 Check the power supply equipment in the equipment room, to make sure that the voltage is

within the normal range.



----End


3.120 PWR_MAJ_ALM

Description The PWR_MAJ_ALM is an alarm indicating that the JPIU input voltage is a severe undervoltage or overvoltage.




Attribute




Name Meaning

Parameter 1 0x01: Severe undervoltage 0x02: Severe overvoltage

Impact on System The JPIU boards adopt the 1+1 hot backup scheme.

When one JPIU board detects a severe undervoltage or overvoltage of the input voltage, it reports the PWR_MAJ_ALM alarm, and then the NE uses the other JPIU board for power supply.

If the two JPIU boards detect the undervoltage or overvoltage of the input voltage at the same time, the system stability is severely affected.

Possible Causes The possible causes of the PWR_MAJ_ALM alarm are as follows: The input voltage is abnormal. The JPIU board has a hardware failure.

Handling Procedure Step 1 Check whether the input voltage of the power supply is normal.



Step 2 Check whether the cable connection between the bolt and the power box is normal.

Step 3 If the input power and the cable connection are both normal, replace the alarmed JPIU board, and then check whether the alarm is cleared.

----End




3.121 PWR_OVER

Description The PWR_OVER is an alarm indicating that the SCC board detects a power voltage higher than the normal voltage.

Attribute




Name Meaning

Parameter 1 Indicates the type of overvoltage.

Impact on System When the power voltage of the SCC board is abnormal, the proper functioning of the SCC board is affected. Hence, the PWR_OVER alarm must be handled as soon as possible.

Possible Causes The power module is faulty. The SCC board is faulty.


----End





3.122 R_LOC

Description The R_LOC is an alarm indicating loss of clock.

Attribute




Name Meaning

Parameter 1 Indicates the actual optical interface number of the board. For example, Parameter 1 = 0x01. In this case, the R_LOC alarm is reported from optical interface 1 of the board.

Impact on System When the R_LOC alarm occurs, the line board fails to extract the clock from the received optical signals. Consequently, the services are interrupted.

Possible Causes The clock extraction module on the line board is faulty. The JSTG board at the opposite station is faulty or is out of position.

Handling Procedure Step 1 Perform a cold reset on the line board that generates the alarm at the local station. Then check

whether the R_LOC alarm is cleared.

Step 2 If the alarm persists, the clock extraction module on the line board may be faulty. In this case, replace the line board, and then check whether the R_LOC alarm is cleared.

Step 3 If the alarm persists, check whether the JSTG board at the opposite station is faulty. If yes, replace the JSTG board, and then check whether the R_LOC alarm is cleared.

----End




3.123 R_LOF

Description The R_LOF is an alarm indicating loss of frame on the receive side of the line. When the correct A1A2 byte is not contained in five frames consecutively received on the receive side of the local optical station, the R_LOF alarm is reported.

Attribute




Name Meaning

Parameter 1 Indicates the actual optical interface number of the alarm board.

Impact on System When the R_LOF alarm occurs, the services are interrupted, and the AIS signal is

inserted in the downstream station. When the R_LOF occurs, the system automatically returns the MS_RDI alarm to the

upstream station. Consequently, the upstream station reports the MS_RDI alarm.

Possible Causes The fiber is incorrectly connected. The received optical power is improper. The signals transmitted at the opposite station do not have the frame structure. The receive unit at the local station is faulty.




Handling Procedure Step 1 Check whether the fiber is incorrectly connected. For example, two boards at different rates

are connected to each other. If yes, modify the incorrect connection, and then check whether the R_LOF alarm is cleared.

Step 2 If the alarm persists, check whether the received optical power at the local station is proper.

Step 3 If the received optical power is extremely low:

1. Clean the fiber connector at the local station and the receive optical interface on the line board, and then check whether the alarm is cleared.

2. Check whether the flange is correctly connected to the optical attenuator at the local station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared.

Step 4 If the received optical power is extremely high, provide more optical attenuators to adjust the received optical power to a proper value, and then check whether the R_LOF alarm is cleared.

Step 5 If the alarm persists, check whether the launched optical power at the opposite station is within the specified value range.

If not, handle the alarm according to the method of handling the OUT_PWR_ABN alarm.

If the launched optical power is proper, perform an optical loopback to the line board at the local station. If the alarm is cleared at the local station, the signals transmitted at the opposite station do not have the frame structure. In this case, replace the relevant line board at the opposite station. If the alarm persists, replace the relevant line board at the local station, and then check whether the R_LOF alarm is cleared.


Step 6 If the alarm persists, check whether the fiber cable is faulty. If yes, remove the fault, and then check whether the R_LOF alarm is cleared.

----End


3.124 R_LOS

Description The R_LOS is an alarm indicating loss of signal on the receive side of the line.



Attribute




Name Meaning


Impact on System When the R_LOS alarm occurs, the services are interrupted, and the AIS signal is

inserted at the downstream station. When the R_LOS occurs, the system automatically returns the MS_RDI alarm to the

upstream station. Consequently, the upstream station generates the MS_RDI alarm.

Possible Causes The fiber is cut or is not connected. The laser is shut down. Signals in the line are heavily attenuated. The receive unit at the local station is faulty. The transmit unit (including the clock board) at the opposite station is faulty.

Handling Procedure Step 1 If the signals in the line are heavily attenuated or some fibers are cut, replace the relevant

fiber, and then check whether the R_LOS alarm is cleared.

Step 2 If the optical interface is not connected with a fiber and is idle, shut down the laser at the optical interface. In this case, the R_LOS alarm is automatically cleared.

Step 3 If the alarm persists, check whether the laser of the relevant line board at the opposite station is in the shutdown state on the T2000. If yes, start up the laser, and then check whether the R_LOS alarm is cleared.

Step 4 If the alarm persists, check the launched optical power at the opposite station on the T2000. If the launched optical power is improper, replace the relevant board at the opposite station.

Step 5 If the alarm persists, check whether the clock board at the opposite station is faulty. If yes, replace the clock board.




Step 6 If the alarm persists, check whether the receive board at the local station is faulty, and replace the line board that reports the alarm at the local station. Then check whether the R_LOS alarm is cleared.

----End


3.125 R_OOF

Description The R_OOF is an alarm that the out-of-frame event occurs on the receive side of the line.

Attribute




Name Meaning


Impact on System When the R_OOF alarm occurs, the services are interrupted, and the AIS signal is

inserted at the downstream station. When the R_OOF occurs, the system automatically returns the MS_RDI alarm to the

upstream station. Consequently, the upstream station generates the MS_RDI alarm.

Possible Causes The received signals are heavily attenuated. Excessive bit errors occur during transmission. The transmit unit at the opposite station is faulty. The receive unit at the local station is faulty.



Handling Procedure Step 1 On the T2000, check whether the received optical power at the local station is proper.

Step 2 If the received optical power is extremely low:

1. Clean the fiber connector at the local station and the receive optical interface on the line board, and then check whether the alarm is cleared.

2. Check whether the flange is correctly connected to the optical attenuator at the local station, and whether the attenuation value specified in the optical attenuator is proper. After making sure that the flange and optical attenuator are used properly, check whether the alarm is cleared.

Step 3 If the received optical power is extremely high, provide more optical attenuators to adjust the received optical power to a proper value, and then check whether the R_OOF alarm is cleared.

Step 4 If the alarm persists, check whether the launched optical power at the opposite station is within the specified value range. If not, handle the alarm according to the method of handling the OUT_PWR_ABN alarm.

Step 5 If the alarm persists, excessive bit errors may occur during transmission. In this case, check whether the fiber is faulty. After removing the faulty fiber, then check whether the R_OOF alarm is cleared.

----End


3.126 RELAY_ALARM

Description The RELAY_ALARM is an alarm of the relay. This alarm occurs when there is an alarm input.

Attribute


Critical Environment alarm





Name Meaning

Parameter 1 Indicates the number of the alarm input/output.

Impact on System The RELAY_ALARM alarm does not affect the NE.

Possible Causes The alarm input mode is enabled. The status of the alarm input/output changes.

Handling Procedure Step 1 View the RELAY_ALARM alarm on the T2000. Confirm the number of the alarm

input/output according to Parameter 1.

Step 2 Cut off the alarm input/output. Then the RELAY_ALARM alarm is automatically cleared.

----End


3.127 RELAY_ALARM_CRITICAL

Description The RELAY_ALARM_CRITICAL is an alarm of critical alarm inputs. This alarm occurs when the user sets the severity of an available alarm input to critical.

Attribute


Critical Environment alarm




Name Meaning


Impact on System The RELAY_ALARM_CRITICAL alarm does not affect the operation of the SCC or the services on the NE.

Possible Causes The possible cause of the RELAY_ALARM_CRITICAL alarm is as follows:

There is a critical alarm input.

Handling Procedure Step 1 View the RELAY_ALARM_CRITICAL alarm on the T2000. Confirm the number of the

alarm input/output according to Parameter 1.

Step 2 Cut off the alarm input/output. Then the RELAY_ALARM_CRITICAL alarm is automatically cleared.

----End


3.128 RELAY_ALARM_IGNORE

Description The RELAY_ALARM_IGNORE is an alarm of warning alarm inputs. This alarm occurs when the user sets the severity of an available alarm input to warning.

Attribute


Warning Environment alarm





Name Meaning


Impact on System The RELAY_ALARM_IGNORE alarm does not affect the operation of the SCC or the services on the NE.

Possible Causes The possible cause of the RELAY_ALARM_IGNORE alarm is as follows:

There is a warning alarm input.

Handling Procedure Step 1 View the RELAY_ALARM_IGNORE alarm on the T2000. Confirm the number of the alarm


Step 2 Cut off the alarm input/output. Then the RELAY_ALARM_IGNORE alarm is automatically cleared.

----End


3.129 RELAY_ALARM_MAJOR

Description The RELAY_ALARM_MAJOR is an alarm of major alarm inputs. This alarm occurs when the user sets the severity of an available alarm input to major.

Attribute






Name Meaning


Impact on System The RELAY_ALARM_MAJOR alarm does not affect the operation of the SCC or the services on the NE.

Possible Causes The possible cause of the RELAY_ALARM_MAJOR alarm is as follows:

There is a major alarm input.

Handling Procedure Step 1 View the RELAY_ALARM_MAJOR alarm on the T2000. Confirm the number of the alarm


Step 2 Cut off the alarm input/output. Then the RELAY_ALARM_MAJOR alarm is automatically cleared.

----End


3.130 RELAY_ALARM_MINOR

Description The RELAY_ALARM_MINOR is an alarm of minor alarm inputs. This alarm occurs when the user sets the severity of an available alarm input to minor.

Attribute


Minor Environment alarm





Name Meaning


Impact on System The RELAY_ALARM_MINOR alarm does not affect the operation of the SCC or the services on the NE.

Possible Causes The possible cause of the RELAY_ALARM_MINOR alarm is as follows:

There is a minor alarm input.

Handling Procedure Step 1 View the RELAY_ALARM_ MINOR alarm on the T2000. Confirm the number of the alarm


Step 2 Cut off the alarm input/output. Then the RELAY_ALARM_ MINOR alarm is automatically cleared.

----End


3.131 RS_CROSSTR

Description The RS_CROSSTR is an alarm indicating that the number of regenerator section bit errors crosses the threshold.

Attribute


Minor Service alarm




Name Meaning

Parameter 1 Indicates the number of the optical interface where the number of regenerator section bit errors crosses the threshold.


Indicates the number of the path where the number of regenerator section bit errors crosses the threshold.




Impact on System The service quality of the board that reports the alarm is degraded. The services of the board that reports the alarm are interrupted.

Possible Causes The laser performance at the opposite station is degraded. The receive optical power at the local station is over high or over low. The clock performance at the local station or the opposite station is degraded. The fiber performance is degraded.

Handling Procedure Step 1 Perform an inloop on the alarmed board at the local station.

If the alarm is cleared, go to Step 2. If the alarm persists, the fault occurs at the local station. Go to Step 4.

Step 2 Perform an outloop at the opposite station.

If the alarm is cleared, the fault occurs at the opposite station. Go to Step 3. If the alarm persists, the fiber performance is degraded or the fiber jumper connector is

dirty. Go to Step 5.

Step 3 Replace the line board at the opposite station.

If the alarm is cleared, the fault is removed. The alarm handling ends.




If the alarm persists, replace the cross-connect and timing board at the opposite station. The alarm handling ends.

Step 4 Replace the alarmed board at the local station.

If the alarm is cleared, the fault is removed. The alarm handling ends. If the alarm persists, replace the cross-connect and timing board at the local station. The

alarm handling ends.

Step 5 Clean the fiber jumper connectors at both the local and opposite stations.

If the alarm is cleared, the fault is removed. The alarm handling ends. If the alarm persists, the optical cable is fault. Remove the fault, and the alarm handling

ends.

----End


3.132 RTC_FAIL

Description The RTC_FAIL is an alarm of SCC real time clock (RTC) failure. This alarm occurs when the clock of the SCC is faulty.

Attribute



Parameters None.

Impact on System When the RTC_FAIL alarm occurs, rerouting may fail and thus the services are interrupted in ASON networks. The RTC_FAIL alarm may affect non-ASON networks, and thus needs to be cleared as soon as possible.

Possible Causes The SCC board is damaged.



Handling Procedure Step 1 Replace the SCC board of the corresponding equipment.

----End


3.133 S1_SYN_CHANGE

Description The S1_SYN_CHANGE is an alarm indicating that, in the S1 byte mode, the clock source is switched. This alarm occurs when, in the SSM mode, the traced clock source is switched.

Attribute



Parameters None.

Impact on System When the S1_SYN_CHANGE alarm occurs, the traced clock source is switched in the SSM mode. If the new clock source has a lower quality, pointer justifications and bit errors are generated, and as a result the quality of services is affected.

Possible Causes There is a fiber cut. The external BITS is interrupted. The S1_SYN_CHANGE alarm occurs at the upstream station.

Handling Procedure Step 1 Check whether there is any fiber cut and whether any service board reports the R_LOS alarm.

If yes, properly connect the fiber to clear the R_LOS alarm, and then check whether the S1_SYN_CHANGE alarm is cleared.

Step 2 If fiber connections are normal, check the external BITS.

1. Check whether the input cable of the external BITS is damaged. If yes, connect a good input cable, and then check whether the S1_SYN_CHANGE alarm is cleared.




2. Make sure that the 2 Mbit/s cable interface for the external BITS input is properly secured on the front panel of the subrack. Check whether the S1_SYN_CHANGE alarm is cleared.

3. Check whether the 2 Mbit/s cable interface for the external BITS input is faulty. If yes, replace the relevant interface board, and then check whether the S1_SYN_CHANGE alarm is cleared.

Step 3 If the alarm persists, check whether the S1_SYN_CHANGE alarm occurs at the upstream station. If yes, repeat steps 1 and 2 to clear the S1_SYN_CHANGE alarm at the upstream station. The S1_SYN_CHANGE alarm at the local station is then automatically cleared.

----End


3.134 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.

Impact on System The SCC_CHANGE alarm reminds the user that the SCC board has been replaced. After the replacement, the data on the current SCC board might be inconsistent with the data on the original SCC board, and the NE will enter into the configuration lockout state. As a result, new service information cannot be downloaded. If the services on the current SCC board are forcibly downloaded, the existing services before the replacement might be lost.

Possible Causes The SCC board is replaced.



Handling Procedure Step 1 When the NE is running in a network, the SCC_CHANGE alarm is not reported. The alarm is

reported only when the SCC board is manually replaced. Contact Huawei technical support engineers to replace SCC board according to the SCC replacement process.

----End


3.135 SECU_ALM

Description The SECU_ALM is an alarm indicating that an illegal user fails to log in to the NE.

Attribute




Name Meaning

Parameter 1 Indicates the login terminal.


Indicates the login errors.


Indicates the first two characters of the user name that is locked after the login verification fails.

Impact on System The SECU_ALM alarm has the following impact on the system: The SECU_ALM alarm is ended soon after it is reported.

Possible Causes The cause for the SECU_ALM alarm is as follows:




An illegal user tries to log in to the EN.

Handling Procedure Step 1 Query the EN log to check the user name that is used for the login.

----End

Related Information After three wrong login passwords are entered, the NM automatically locks the screen. Only the administrator can unlock the screen.

3.136 SLAVE_BAD

Description The SLAVE_BAD is an alarm indicating that the alarmed board detects a fault of the standby cross-connect board, standby clock board, or standby SCC board.

Attribute




Name Meaning

Parameter 1 Indicates the type of the faulty standby board. 0x00: Standby higher order cross-connect board 0x01: Standby clock board 0x02: Standby SCC board 0x03: Alarmed board itself

Parameter 2 When the value of Parameter 1 is 0x00 or 0x03, Parameter 2 indicates the faulty bus number.

When the value of Parameter 1 is 0x01 or 0x02, the value of Parameter 2 is always 0x01.

Parameter 3 Indicates the slot number of the standby board.



Impact on System Every service board of the OptiX OSN 9500 can select its own cross-connect board, clock board, and SCC board. When the SLAVE_BAD alarm occurs, therefore, the active/standby protection of the cross-connect board, clock board, or SCC board is lost.

If the alarmed board also reports the MASTER_ERR alarm, and the slot number parameters of the MASTER_ERR and SLAVE_BAD alarms are the same, the services on the alarmed board are interrupted.

If the alarmed board does not report the MASTER_ERR alarm, or if the alarmed board does report the MASTER_ERR alarm at the same time but the slot number parameters of the MASTER_ERR and SLAVE_BAD alarms are different, the services are not affected. In this case, the alarmed board only loses the active/standby protection options of the cross-connect boards, clock boards, or SCC boards.

Possible Causes Bit errors are generated in the signals that the alarmed board receives from the standby

cross-connect board. The standby clock board, from which the alarmed board receives signals, has a bad clock

quality. The alarmed board detects a fault of the standby SCC board. The alarmed board detects a fault of its own hardware.

Handling Procedure Step 1 Locate the faulty board according to the alarm parameters.

Step 2 Replace the faulty board.

Step 3 If the SLAVE_BAD alarm persists, contact Huawei technical support engineers.

----End

Related Information Even if the SLAVE_BAD alarm is cleared after the board replacement, you need to report this alarm to Huawei technical support engineers.

3.137 SLAVE_WORKING

Description The SLAVE_WORKING is an alarm indicating that the standby board is working.

Attribute







Name Meaning

Parameter 1 Indicates the type of the faulty standby board. 0x00: Standby higher order cross-connect board 0x01: Standby clock board 0x02: Standby SCC board


Parameter 3 Indicates the slot number of the working standby board.

Impact on System In case a line board reports the SLAVE_WORKING alarm and the working standby board is an SCC board according to the alarm parameters, the reconfiguration of services might cause bit errors in existing services and even interrupt the existing services.

In other cases, the SLAVE_WORKING alarm does not affect services.

Possible Causes Bit errors are generated in the signals that the alarmed board receives from the active

cross-connect board. As a result, the alarmed board selects signals from the standby cross-connect board.

The active clock board, from which the alarmed board receives signals, has a bad clock quality. As a result, the alarmed board selects signals from the standby clock board.

The alarmed board detects a fault of the active SCC board.

Handling Procedure Step 1 If the SLAVE_WORKING alarm is generated during a new deployment, it need not be

handled.

Step 2 If the SLAVE_WORKING alarm is generated when the equipment is already in stable operation, contact Huawei technical support engineers to handle the problem.

----End




3.138 SNCP_FAIL

Description The SNCP_FAIL is an alarm indicating the SNCP switching failure.

Attribute




Name Meaning


Indicates the protection group ID. Parameter 1 is the higher byte, and Parameter 2 is the lower byte. For example, Parameter 1 = 0x00, and Parameter 2 = 0x01. In this case, the SNCP switching fails for the protection group whose ID is 1.

Impact on System When the SNCP switching fails, the services with SNCP are not protected, and the services in this SNCP group are interrupted.

Possible Causes During the SNCP switching, the service grooming fails.

Handling Procedure Step 1 Reset the SCC board for a re-computation of all services.

----End





3.139 SPEED_ERROR

Description The SPEED_ERROR is an alarm indicating that the JCOM board detects a rate error of its internal chip.

Attribute



Parameters None.

Impact on System The JCOM board is the system communication board. If the JCOM board has a hardware failure, the Ethernet communication of the system fails. The SPEED_ERROR alarm does not affect existing services, but affects system functions such as the monitoring for the entire NE and the update of service configuration.



----End


3.140 SWITCH_DISABLE

Description The SWITCH_DISABLE is an alarm indicating that the protection switching function is manually disabled for the higher order cross-connect boards and the clock boards. This alarm is used for internal test purposes.



Attribute


Warning Security alarm

Parameters None.

Impact on System The SWITCH_DISABLE alarm affects the active/standby switching function of the higher order cross-connect boards and of the clock boards.

Possible Causes During the test, a command is issued to request the board software to disable the switching function.

Handling Procedure Step 1 Log in to the NE to cancel the switching disabling command. The SWITCH_DISABLE alarm

is cleared.

----End


3.141 SYN_BAD

Description The SYN_BAD is a synchronization source degrade alarm.

Attribute



Parameters None.




Impact on System When the SYN_BAD alarm occurs, tracing the relevant clock source may cause service bit errors.

Possible Causes The quality of the traced clock source is degraded. The clock board that reports the SYN_BAD alarm has a hardware failure.

Handling Procedure Step 1 Switch to another clock source. If the SYN_BAD alarm is cleared, confirm why the original

clock source is degraded and handle the problem.

Step 2 If the alarm persists, the clock board may have a hardware failure. In this case, replace the clock board.

----End


3.142 SYNC_C_LOS

Description The SYNC_C_LOS is an alarm indicating that the signals from the synchronization source are lost.

Attribute




Name Meaning

Parameter 1 Indicates the slot number of the line board where the lost line clock source resides.



Name Meaning

Parameter 2 Indicates the corresponding optical interface number on the line board where the lost clock source resides.

Impact on System The configured line clock source is faulty and unavailable.

Possible Causes The line clock source configured in the NE clock tracing table fails.

Handling Procedure Step 1 According to the alarm parameters, confirm the relevant line board and optical interface

where the faulty clock source resides.

Step 2 On the T2000, check whether the optical interface on the relevant line board has any critical alarms, such as R_LOS and R_LOF.

Step 3 If yes, first clear these critical alarms, and then check whether the SYNC_C_LOS alarm is cleared.

Step 4 If the alarm persists, replace the line board where the faulty clock source resides.

----End


3.143 SYNC_F_M_SWITCH

Description The SYNC_F_M_SWITCH is an alarm indicating that the manual or forced switching is performed for a clock source.

Attribute







Name Meaning


Indicates the number of the clock source that the clock tracing is forcibly or manually switched to. If Parameter 1 is 0xf0 and Parameter 2 is 0x01, the clock tracing is forcibly or manually switched to the first external clock source. If Parameter 1 is 0xf0 and Parameter 2 is 0x02, the clock tracing is forcibly or manually switched to the second external clock source. If Parameter 1 is 0xf1 and Parameter 2 is 0x01, the clock tracing is forcibly or manually switched to the internal clock source of the equipment. In other cases, the clock tracing is forcibly or manually switched to a line clock source. Parameter 1 indicates the slot number of the board, and Parameter 2 indicates the optical interface number on the board. For example, when Parameter 1 is 0x05 and Parameter 2 is 0x01, the clock tracing is forcibly or manually switched to the clock source at optical interface 1 on the board in slot 5.

Impact on System When the manual or forced switching is performed, the automatic switching function of the clock board is affected.

Possible Causes A manual or forced switching is performed for the clock tracing.

Handling Procedure Step 1 View the SYNC_F_M_SWITCH alarm on the T2000, and then confirm the alarmed clock

source according to the alarm parameters.

Step 2 Clear the manual or forced switching for this clock source, and the alarm is automatically cleared. For details, refer to "Performing Clock Source Switching."

----End




3.144 SYNC_FAIL

Description The SYNC_FAIL is an alarm indicating that the batch backup of databases fails between the active and standby SCC boards.

Attribute




Name Meaning

Parameter 1 Indicates the failure type. 0x21: The communication fails between the active and standby SCC boards.

0x31: The database backup fails. 0x32: The software versions of the active and standby SCC boards are inconsistent.

Parameter 2 The value is always 0xff.

Impact on System The synchronization failure between the active and standby SCC boards results in the failure of the active/standby protection function of the SCC boards.

Possible Causes The software versions of the active and standby SCC boards are inconsistent. The communication fails between the active and standby SCC boards. The standby SCC board is faulty.

Handling Procedure Step 1 Check whether the NE has the MSSW_DIFFERENT alarm, which indicates that the software

versions of the active and standby SCC boards are inconsistent. If the software versions are inconsistent, update the software of the standby SCC board.




Step 2 Check whether the standby SCC board is securely inserted in the slot, and whether the standby SCC board is offline. If the standby SCC board is not securely inserted or is offline, remove the board and insert it again. Then check whether the SYNC_FAIL alarm is cleared.

Step 3 If the SYNC_FAIL alarm persists, check whether the standby SCC board has the HARD_BAD alarm. If yes, replace the standby SCC board.

Step 4 If the communication fails between the active and standby SCC boards according to the alarm parameters, perform a warm reset for the standby SCC board, or remove the standby SCC board and insert it again.


----End


3.145 SYNC_LOCKOFF

Description The SYNC_LOCKOFF is an alarm indicating that the clock source is locked out.

Attribute




Name Meaning

Parameter 1 When the value of Parameter 1 is 0xf0, an external clock source is locked out. In this case, you can determine the external clock source number according to Parameter 2. When the value of Parameter 1 is not 0xf0, a line clock source is locked out. In this case, Parameter 1 indicates the slot number of the line board where the line clock source resides.



Name Meaning

Parameter 2 When the value of Parameter 1 is 0xf0, Parameter 2 indicates the number of the locked external clock source. When the value of Parameter 1 is not 0xf0, Parameter 2 indicates the number of the optical interface where the lock line clock source resides.

Impact on System A locked clock source is no longer available for clock source selection.

Possible Causes A command is manually issued to lock out the clock source.

Handling Procedure Step 1 Release the lockout of the clock source, and then the SYNC_LOCKOFF alarm is cleared.

----End


3.146 T_LOSEX

Description The T_LOSEX is an alarm indicating that the backplane bus is faulty.

Attribute




Name Meaning

Parameter 1 Indicates the number of the faulty backplane bus.




Impact on System Some or all of the services on the alarmed board are interrupted.

Possible Causes The board is not securely inserted in the slot. The active and standby cross-connect boards are out of position or are not securely

inserted in the slots. The board slot is faulty.

Handling Procedure Step 1 Make sure that the four higher order cross-connect boards are all securely inserted in the slots.

Check whether the T_LOSEX alarm is cleared.

Step 2 If the alarm persists, replace the alarmed board and then check whether the alarm is cleared.

Step 3 If the alarm persists, install the alarmed board into another slot and then check whether the alarm is cleared.

----End


3.147 TEM_HA

Description The TEM_HA is an alarm indicating that the temperature of the laser is extremely high.

Attribute




Name Meaning




Impact on System When the TEM_HA alarm occurs, the laser is faulty. Consequently, the services are interrupted.

Possible Causes The ambient temperature is extremely high. The optical module is faulty.

Handling Procedure Step 1 Check whether the ambient temperature in the equipment room is extremely high. If yes,

decrease it to a proper value for the equipment to work well, and then check whether the TEM_HA alarm is cleared.

Step 2 If the alarm persists, the optical module may be faulty. Replace the board that generates the alarm, and then check whether the TEM_HA alarm is cleared.

----End


3.148 TEM_LA

Description The TEM_LA is an alarm indicating that the temperature of the laser is extremely low.

Attribute




Name Meaning





Impact on System When the TEM_LA alarm occurs, the laser is faulty. Consequently, the services are interrupted.

Possible Causes The ambient temperature is extremely low. The optical module is faulty.

Handling Procedure Step 1 Check whether the ambient temperature in the equipment room is extremely low. If yes,

increase it to a proper value for the equipment to work well, and then check whether the TEM_LA alarm is cleared.

Step 2 If the alarm persists, the optical module may be faulty. Replace the board that generates the alarm, and then check whether the TEM_LA alarm is cleared.

----End


3.149 TEMP_ALARM

Description The TEMP_ALARM is an alarm indicating that, according to the report from the EMPU board, the ambient temperature crosses the upper or lower threshold.

Attribute




Name Meaning

Parameter 1 0x01: The detected temperature crosses the upper threshold. 0x02: The detected temperature crosses the lower threshold.



Impact on System If the NE works under a threshold-crossing temperature for a long time, the board life and the system stability are affected.

Possible Causes The ambient temperature crosses the upper (50ºC) or lower (–5ºC) threshold.


between 0ºC and 45ºC.

----End


3.150 TEMP_MAJ_ALM

Description The TEMP_MAJ_ALM is an alarm indicating that the temperature of the board is over the major upper threshold.

Attribute




Name Meaning

Parameter 1 Indicates location where the alarm is raised. 0x01: This alarm is detected at the air intake. 0x02: This alarm is detected at the air outtake.

Parameter 2 0x01: This alarm is detected by the first MBUS module on the board. 0x02: This alarm is detected by the second MBUS module on the board.




Impact on System The temperature of the board is over the major upper threshold. The board may be damaged and the services on this board may be interrupted.

Possible Causes The ambient temperature is too high.

The board is faulty.

Handling Procedure Step 1 Lower the temperature in the equipment room, to make sure that the ambient temperature is

between 0ºC and 45ºC. Check whether the TEMP_MAJ_ALM alarm is cleared.

Step 2 If the alarm persists even when the ambient temperature is normal, check if the fans in the fan tray assembly work normally. If not, replace the faulty fan.

Step 3 If the TEMP_MAJ_ALM alarm is not cleared, replace the alarmed board.

----End

Related Information The equipment can fail in several minutes without a fan tray assembly. Insert the fan tray assembly back to the equipment immediately after the fan replacement.

3.151 TEMP_MIN_ALM

Description The TEMP_MIN_ALM is an alarm indicating that the temperature of the board is over the minor higher threshold or below the minor lower threshold.

Attribute






Name Meaning

Parameter 1 Indicates location where the alarm is detected. 0x01: This alarm is detected at the air intake. 0x02: This alarm is detected at the air outtake.

Parameter 2 0x01: The temperature of the board is over the minor higher threshold. 0x02: The temperature of the board is below the minor lower threshold.

Parameter 3 0x01: This alarm is detected by the first MBUS module on the board. 0x02: This alarm is detected by the second MBUS module on the board.

Impact on System Working in such a state for a long time shortens the lifetime of the board, and effects the stability of the system.

Possible Causes The ambient temperature is too high or too low. The board is faulty.

Handling Procedure Step 1 Adjust the temperature in the equipment room, to make sure that the ambient temperature is

between 0ºC and 45ºC. Check whether the TEMP_MIN_ALM alarm is cleared.

Step 2 If the alarm persists even when the ambient temperature is normal, check if the fans in the fan tray assembly work normally. If not, replace the faulty fan.

Step 3 If the TEMP_MIN_ALM alarm is not cleared, replace the alarmed board.

----End

Related Information The equipment can fail in several minutes without a fan tray assembly. Insert the fan tray assembly back to the equipment immediately after the fan replacement.

3.152 TEMP_OVER

Description The TEMP_OVER is an alarm indicating that the temperature of the JBPA/JBA2 board is over the threshold.




Attribute




Name Meaning

Parameter 1 Indicates the optical interface number of the board where the temperature is over the threshold.


Indicates the sequence number of the laser where the temperature is over the threshold. Parameter 2 is the higher byte, and Parameter 3 is the lower byte.

Impact on System When the temperature of the JBPA/JBA2 board is over the threshold, the performance of the optical amplifier module is affected, and the optical amplifier module might even be burnt out. In addition, the received optical power at the opposite end is abnormal, and the services are impaired.

Possible Causes The ambient temperature is too high. The board is faulty.

Handling Procedure Step 1 Lower the temperature in the equipment room, to make sure that the ambient temperature is

between 0ºC and 45ºC. Check whether the TEMP_OVER alarm is cleared.

Step 2 If the alarm persists even when the ambient temperature is normal, replace the alarmed board. Check whether the alarm is cleared.

----End




3.153 TEST_STATUS

Description The TEST_STATUS is an alarm indicating that the board is in the test status.

Attribute


Warning Processing alarm

Parameters None

Impact on System None

Possible Causes A command is issued for the board to change to the test status.

Handling Procedure Step 1 When a command is issued to end the test status, the TEST_STATUS alarm is automatically

cleared. However, this does not eliminate the system impact that arose during the test status of the board.

----End


3.154 TF

Description The TF is an alarm of laser transmission failure.

Attribute







Name Meaning

Parameter 1 Indicates the actual number of the optical interface on a board where the alarm occurs.

Impact on System When the TF alarm occurs, the laser transmission becomes faulty, which causes service interruption.

Possible Causes The laser is aged.

Handling Procedure Step 1 Replace the alarmed board. Check whether the alarm is cleared.

----End


3.155 TMP_DIFF_OVER

Description The TMP_DIFF_OVER is an alarm indicating that the temperature difference between the air exhaust vent and the air intake vent of the board is over the threshold.

Attribute







Name Meaning

Parameter 1 0x01: The TMP_DIFF_OVER alarm is detected by the first MBUS module of the board.

0x02: The TMP_DIFF_OVER alarm is detected by the second MBUS module of the board.

Impact on System When the board has a local high temperature, the board life and the system stability are affected. As a result, bit errors that affect the service quality might be generated.

Possible Causes The ventilation of the NE is bad. The temperature detection module of the board is damaged.

Handling Procedure Step 1 Clean the air filter, and then check whether the TMP_DIFF_OVER alarm is cleared.

Step 2 If the alarm persists, replace the alarmed board.

----End


3.156 TR_LOC

Description The TR_LOC is an alarm indicating the transmit loss of clock.

Attribute








Name Meaning

Parameter 1 If the TR_LOC alarm is reported by the SCC board, Parameter 1 indicates the type of the lost clock.

If the TR_LOC alarm is reported by a board other than the SCC, the value of Parameter 1 is always 0x03, which indicates both clock boards fail to transmit clock signals.

Impact on System If the TR_LOC alarm is reported by the SCC board, the alarmed SCC board cannot

function properly. If the TR_LOC alarm is reported by a board other than the SCC, the services on the

alarmed board are impaired.

Possible Causes The clock boards are faulty or not in position. The alarmed board is faulty.

Handling Procedure Step 1 Check whether the clock boards are in position. If the clock boards are not in position, install

them. If they are in position, go to the next step.

Step 2 View the clock board alarms to determine the working status of the clock boards.

1. If the clock boards report alarms, handle the clock board alarms first. 2. If the clock boards do not report alarms, the board that reports the TR_LOC alarm is

faulty. In this case, perform a cold reset for the alarmed board, or replace the alarmed board.

----End


3.157 TU_AIS_VC3

Description The TU_AIS_VC3 is a TU alarm indication signal in the VC-3 lower order path. TU alarm indication is the AIS at the level of the VC-3 lower order path. If a board has detected that the TU path is all "1"s, the TU_AIS_VC3 alarm is reported.



Attribute




Name Meaning




Parameter 4 Indicates the number of the VC-3 lower order path. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01, Parameter 4 = 0x01. In this case, the TU_AIS_VC3 alarm is reported from VC-3 lower order path 1 of AU-4 path 1 for optical interface 1 on the board.

Impact on System When the TU_AIS_VC3 alarm occurs, the VC-3 path services are interrupted.

Possible Causes Some higher-level alarms, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, occur in

the system. A hardware fault alarm, such as the PLL_FAIL or CHIP_FAIL, occurs at the upstream

station. The cross-connect and timing board is faulty. The relevant path at the opposite station is faulty.

Handling Procedure Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, is

detected on the T2000. If yes, take priority to clear it, and then check whether the TU_AIS_VC3 alarm is cleared. If the alarm persists, go to the next step.

Step 2 Check whether any hardware fault alarm, such as the PLL_FAIL or CHIP_FAIL, occurs at the upstream station. If yes, clear it, and then check whether the TU_AIS_VC3 alarm is cleared. If the alarm persists, go to the next step.

Step 3 Perform a cold reset on the board that reports the alarm. Then check whether the TU_AIS_VC3 alarm is cleared. If the alarm persists, go to the next step.





Step 4 Replace the board that reports the alarm, and then check whether the TU_AIS_VC3 alarm is cleared. If the alarm persists, go to the next step. Step 5 Check whether the cross-connect and timing board is faulty. If yes, replace it, and then check whether the TU_AIS_VC3 alarm is cleared.

Step 5 Check whether the board at the opposite station is faulty. If yes, replace it, and then check whether the TU_AIS_VC3 alarm is cleared.

----End


3.158 TU_LOP_VC3

Description The TU_LOP_VC3 is an alarm indicating the loss of pointer in the VC-3 lower order path. If a board has detected that the TU-PTR value is an invalid pointer or NDF reversion in eight consecutive frames, the TU_LOP_VC3 alarm is reported.

Attribute




Name Meaning






Name Meaning

Parameter 4 Indicates the number of the VC-3 lower order path. For example, Parameter 1 = 0x01, Parameter 2 = 0x00, Parameter 3 = 0x01, Parameter 4 = 0x01. In this case, the TU_LOP_VC3 alarm is reported from VC-3 lower order path 1 of AU-4 path 1 for optical interface 1 on the board.

Impact on System When the TU_LOP_VC3 alarm occurs, the VC-3 path services are interrupted.

Possible Causes Some higher-level alarms, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, occur in

the system. A hardware fault alarm, such as the PLL_FAIL or CHIP_FAIL, occurs at the upstream

station. The cross-connect and timing board is faulty. The relevant path at the opposite station is faulty.

Handling Procedure Step 1 Check whether any higher-level alarm, such as the R_LOS, R_LOF, HP_SLM or AU_AIS, is

detected on the T2000. If yes, take priority to clear it, and then check whether the TU_LOP_VC3 alarm is cleared. If the alarm persists, go to the next step.

Step 2 Check whether any hardware fault alarm, such as the PLL_FAIL or CHIP_FAIL, occurs at the upstream station. If yes, clear it, and then check whether the TU_LOP_VC3 alarm is cleared. If the alarm persists, go to the next step.

Step 3 Perform a cold reset on the board that reports the alarm. Then check whether the TU_LOP_VC3 alarm is cleared. If the alarm persists, go to the next step.


Step 4 Replace the board that reports the alarm, and then check whether the TU_LOP_VC3 alarm is cleared. If the alarm persists, go to the next step.

Step 5 Check whether the cross-connect and timing board is faulty. If yes, replace it, and then check whether the TU_LOP_VC3 alarm is cleared.

Step 6 Check whether the board at the opposite station is faulty. If yes, replace it, and then check whether the TU_LOP_VC3 alarm is cleared.

----End





3.159 W_OFFLINE

Description The W_OFFLINE is an alarm indicating that the tact switches of the clock board, cross-connect board, or SCC board are out of position.

Attribute




Name Meaning

Parameter 1 Indicates which of the two tact switches is out of position. 0x01: The upper tact switch of the board is out of position. 0x02: The lower tact switch of the board is out of position.

Impact on System If the upper and lower tact switches of the board are both out of position, the active/standby switching function of the clock boards, cross-connect boards, or SCC boards is affected.

Possible Causes The ejector levers of the board are pulled open. The tact switches on the ejector levers of the board are faulty.

Handling Procedure Step 1 Properly push the ejector levers of the board in position, and then check whether the

W_OFFLINE alarm is cleared.

Step 2 If the alarm persists, replace the alarmed board.

----End




3.160 W_R_FAIL

Description The W_R_FAIL is an alarm indicating the reading and writing failure of the board register.

Attribute




Name Meaning

Parameter 1 Indicates the chip number.


Indicates the failure cause.

Impact on System When the reading and writing failure occurs on the board register, the services on the board are interrupted.

Possible Causes The board is faulty. The clock board is faulty.

Handling Procedure Step 1 Replace the alarmed faulty board.

Step 2 If the alarm persists, replace the clock board of the local NE.

----End





3.161 WRG_BD_TYPE

Description The WRG_BD_TYPE is an alarm of wrong board type. This alarm occurs when the types of the logical board and the physical board are different.

Attribute




Name Meaning

Parameter 1 Indicates the number of the slot that generates this alarm.

Impact on System The WRG_BD_TYPE alarm does not affect the existing services and the operation of the system. The slot that generates this alarm, however, cannot be configured with services.

Possible Causes The original board is replaced by one that supports multiple board IDs. The types of the logical board and the physical board are different.

Handling Procedure Step 1 View the WRG_BD_TYPE alarm on the T2000, and then confirm the slot number according

to Parameter 1.

Step 2 Check whether the physical board in this slot supports multiple board IDs and whether the physical board can alternate with one of the logical board type. If yes, wait for several minutes. Then the WRG_BD_TYPE alarm is automatically cleared.

Step 3 If the WRG_BD_TYPE alarm persists, check whether the logical board in this slot is correct. If yes, replace the corresponding physical boards. Then check whether this alarm is cleared.



Step 4 If the logical board is wrong, create a correct logical board on the T2000 according to the physical board type. Then check whether the WRG_BD_TYPE alarm is cleared.

----End


3.162 XC_UNSWITCH

Description The XC_UNSWITCH is an alarm indicating that the cross-connect matrix of the board is not switched.

Attribute




Name Meaning

Parameter 1 Indicates the slot number of the board whose cross-connect matrix is not switched.

Impact on System The services related to the alarmed board are interrupted.

Possible Causes 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.

The board is in the BIOS state, and as a result cannot be updated with the cross-connect matrix configured by the NE software.




Handling Procedure Step 1 Check whether the alarmed board has communication alarms. If yes, clear the communication

alarms, and then check whether the XC_UNSWITCH alarm is cleared.

Step 2 Perform a warm reset for the board, and check whether the XC_UNSWITCH alarm is still generated.

Step 3 If the XC_UNSWITCH alarm is still generated after the warm reset, contact Huawei engineers to re-load the board software.

Step 4 If the alarm is still generated after the board software is re-loaded, replace the alarmed board.

----End


Date post:	21-Apr-2015
Category:	Documents
Upload:	geovaneblm1
View:	264 times
Download:	19 times

30121709 Alarm Clearing

Documents