How to Locate fault during Huawei OptiX OSN2500?

Handling of Abnormalities of Fiber, Cable, and Connector

This section describes how to handle a fiber failure, cable failure, and a connector failure based
on the common causes of the fiber failure, cable failure, and connector failure.

Common Causes

1. Cables are broken or wrongly spliced.
2. Attenuation of cable and flange is very high.
3. The cable connector is loose.
4. Power cables are wrongly connected.
5. The interface board is wrongly connected.

Procedure

Step 1 On the U2000, check whether alarms, such as R_LOS, R_LOF, T_ALOS, P_LOS or

IN_PWR_ABN, are triggered when the fiber, cable, or connector is abnormal. When these

alarms exist, refer to Huawei OptiX OSN 2500 Intelligent Optical Transmission System Alarms

Reference to handle these alarms.

Step 2 Check whether optical fibers and power cables are broken.

Step 3 Check whether optical fibers are wrongly spliced.

Step 4 Check whether connectors are loose.

Step 5 Check whether the bending radius of the optical fiber is not less than 60 mm.

Checking Configuration Data

During the fault location and rectification, the configuration data should be checked.

Check whether the data is correctly configured. Especially, check the configuration data when

the services are interrupted during the equipment installation, commissioning and upgrade.

The query items include data configuration of the network, NE and U2000.

Checking Misoperation

Human misoperation may result in service interruption.

Misoperation

Human misoperation refers to the following operations on the available services.

Configure hardware or software loopback.

Configure services as unloaded.

Procedure

Step 1 Check whether the loopback is configured on the tributary or line. If the loopback is configured,

the LOOP_ALM alarm, indicating the loopback, can be queried on the U2000. In this case,

release the software or hardware loopback on the U2000 or equipment.

Step 2 Check whether "service unloaded" is configured on the U2000. If "service unloaded" is

configured, the alarm indicating that the path is unloaded, such as LP_UNEQ, can be queried

on the U2000. In this case, modify "service unloaded" to "service loaded".

Checking Consistency of Board Models

After the replacement, models of the new board and original board should be consistent.

Procedure

Step 1 Check whether the model of the replaced or added board during the upgrade or expansion is

consistent with that of the original board. Especially, in the case of the cross-connect and timing

boards with the active and standby relation, the active and standby boards should of the same

model. If the board models are inconsistent, the WRG_BD_TYPE alarm, indicating that the

board type of the inserted board is incorrect, can be queried on the U2000.

Step 2 According to the actual situation, check whether the setting of the DIP switch and jumper is correct.

Handling Hardware Faults of Equipment

If the fault is a hardware fault, replace the faulty board with a new one.

Common alarms indicating hardware faults are listed as follows:

HARD_BAD

COMMUN_FAIL

HSC_UNAVAIL

BD_STATUS

BUS_ERR

CHIP_FAIL

PLL_FAIL

TR_LOC

T_LOSEX

For handling of the preceding alarms, refer to the Alarms and Performance Events Reference.

Locate the faulty station by analyzing the alarms, indicators or using the loopback. Then, replace

the faulty board to rectify the fault.