Download - MODULE Alarm Analyze

www.huawei.com

Huawei Technologies Co., Ltd.

23/4/17

OptiX RTN 600 - 900 Troubleshooting – Alarm analyze RTN---Radio Transmission Node

Huawei Technologies Co., Ltd. Page 2Page 2

Summary

For the MW RTN radio troubleshooting, need check the

alarm first, afterward analyze and handle these

alarms .

This document introduce the alarm which possibly

meet when do the troubleshooting and how to

handle these.


1.Compare Alarm Priority and Severity

Alarm PRIORITY is different with alarm SEVERITY.

Alarm SEVERITY is the grade of how service being affected.

Alarm PRIORITY determines the sequence of dealing with the alarm.

Alarm SEVERITY is defined by product description with 4 level

Critical, Major, Minor, Warning.

Alarm PRIORITY is defined by experience of troubleshooting with 4 level

Hardware problem and wrong configuration, Mw Link error,

Cross-connection error, Services interrupt


2. Priority For Alarm

2.1 Hardware problem and wrong configuration(1st):

BD_NOT_INSTALLED, BD_STATUS, CONFIG_NOSUPPORT,

HARD_BAD, IF_CABLE_OPEN, IF_INPWR_ABN, IF_MODE_UNSUPPORT

NO_BD_SOFT, POWER_FAIL, RADIO_MUTE

2.2 Mw Link error(2nd)

MW_LOF, MW_RDI, RADIO_RSL_HIGH, RADIO_RSL_LOW

2.3 Cross-connection error(3rd)

R_LOF/R_LOS,MS_AIS

2.4 Services interrupt(4th)

T_ALOS, TU_AIS, UP_E1_AIS/DN_E1_AIS, ETH_LOS, TU_AIS_VC12/TU_LOP_VC12


BD_STATUSBD_STATUS is an alarm indicating that a board is not in position.

Possible Causes :

The board is faulty

The board is installed in an incorrect slot or connect poorly

The IF cable are poorly connected or switched off the ODU power supply if the alarm for ODU

Handing Procedure:

Step 1: Check whether the physical board is installed into a correct slot ,properly installed and tightly fixed

Step 2: Check whether the ODU is powered on and the IF cables are correctly connected.

Step 3: Remove and insert the board again

Step 4: Replace the board, ODU and IF cable

2.1 Hardware problem and wrong configuration(1st):


CONFIG_NOSUPPORT

CONFIG_NOSUPPORT is an alarm indicating that the configuration is

not supported. This alarm is reported if the ODU detects that

the configured parameters do not match those of the ODU.

Possible Causes :

The type of the ODU mismatches the configured

parameters.

Wrong ODU frequency band ,Wrong frequency point , Wrong

TX power, Wrong protection type etc.

Handing Procedure:

Step 1: Check whether the configured parameters meet the

network planning requirements including frequency band ,

frequency point , TX power, protection type etc with WebLCT.


IF_MODE_UNSUPPORTED

IF_MODE_UNSUPPORTED is an alarm indicating that

the configured IF working mode is not

supported.

Possible Causes :

The IF board is not loaded with correct

software.

Handing Procedure:

Step 1: Loading down the correct software.


BD_NOT_INSTALLED

BD_NOT_INSTALLED is an alarm indicating that a board is installed

but the associated logical board is not installed.

Possible Causes :

the slot is not configured with the logical board

The physical board is installed into a wrong slot or connect poorly.

Handing Procedure:

Step 1: Check whether the physical board is installed into a correct

slot.

Step 2: Check whether the physical board properly installed and

tightly fixed .

Step 3: Configure the logical board through the WebLCT


HARD_BAD

HARD_BAD is an alarm indicating hardware errors.

Possible Causes :

The board is faulty.

The board and the backplane aare not properly connected

Handing Procedure:

Step 1: Check whether the physical board is installed into a

correct slot ,properly installed and tightly fixed.

Step 2: Remove and insert the board again

Step 3: Replace the board that reports the alarm.


IF_CABLE_OPEN

IF_CABLE_OPEN is an alarm indicating that the IF cable is disconnected.

Possible Causes :

The IF cable is loose or faulty.

The IF port on the IF board is faulty

The power module of the ODU is faulty

Handing Procedure:

Step 1: Check whether the connector of the IF cable is loose or whether

the connector is not properly made.

Step 2: Check whether the jacket of the IF cable is damaged.

Step 3: Replace IF cable

Step 4: Replace IF board and ODU.


IF_INPWR_ABN

IF_CABLE_OPEN is an alarm indicating that the input IF power of the

ODU is abnormal.

Possible Causes :

There is an inloop operation on the IF port.

The IF board or ODU or IF cable is faulty

Handing Procedure:

Step 1: Check whether there is an onloop operation n the IF port

Step 2: Check whether the IF cable are soggy, broken or pressed.

Step 3: Check whether the cable connector workmanship meets the

requirement

Step 4: Replace IF board and ODU.


NO_BD_SOFT

NO_BD_SOFT is an alarm indicating that the board software is

missing

Possible Causes :

Software loading is abnormal.

Handing Procedure:

Step 1: Re-load the software.


POWER_FAIL

POWER_FAIL is an alarm indicating that the power supply fails.

This alarm is reported if the ODU detects that ist power

module fails.

Possible Causes :

The power module of the ODU is faulty.

Handing Procedure:

Step 1: Replace the ODU that reports the alarm.


RADIO_MUTE

RADIO_MUTE is an alarm indicating that radio transmitter is muted

Possible Causes :

The transmitter of the local station is muted.

The data configuration of the ODU is incorrect.

The IF board is faulty , causing abnormal IF output.

Handing Procedure:

Step 1: Check whether the transmitter of the ODU is muted with WebLCT.

Step 2: Check whether there is an CONFIG_NOSUPPORT alarm, and

handle the alarm, Check whether the configured parameters meet

the network planning requirements .

Step 3: Replace the IF board


MW_LOF

MW_LOF is an alarm indicating that the Microwave frame is lost.

Possible Causes :

The microwave link performance degrades.

The transmit unit of the remote station is faulty.

The receive unit of the local station is faulty.

Handing Procedure:

Step 1: Check whether the transmit and receive frequency meet the network planning.

Step 2: Check whether the transmit power of the remote station is normal .

Step 3: Check whether the antennas at both ends are properly adjusted

Step 4: Check whether the outdoor units such as antennas , combiner , ODU , and flexible waveguide are wet, damp , or damaged.

Step 5:Check whether there is block in the transmit direction.

Step 6: Replace the ODU


RADIO_RSL_HIGH

RADIO_RSL_HIGH is an alarm indicating that radio receive

power is too high .

Possible Causes :

The ODU is faulty

There is a strong interference source nearby.

Handing Procedure:

Step 1: Change the frequency point .



RADIO_RSL_LOWRADIO_RSL_LOW is an alarm indicating that radio receive power is too

low .

Possible Causes :

The microwave link signal is too much attenuated.

The transmit power of the remote station is too low

The ODU of the local station is faulty

Handing Procedure:

Step 1: Check whether the transmit power of the remote station is normal .

Step 2: Check whether the antennas at both ends are properly adjusted

Step 3: Check whether the polarization direction of the antenna, ODU and hybrid coupler is correctly set.

Step 4: Check whether the outdoor units such as antennas , combiner , ODU , and flexible waveguide are wet, damp , or damaged.

Step 5:Check whether there is block in the transmit direction.



MW_RDI

MW_RDI is an alarm indicating that there are defects at the

remote end of the microwave link.

Possible Causes :

The transmit unit of the local station is faulty

Handing Procedure:

Step 1: Check whether the transmit power of the local station is

normal .

Step 2: Handle the microwave alarm occurred to the remote

station .


R_LOS/R_LOF

R_LOS/R_LOF is an alarm indicating that signal is lost at

the receive side.

Possible Causes :

PXC board is faulty

Handing Procedure:

Step 1: Check whether the other microwave link alarm

such as MW_LOF, RADIO_RSL_LOW . Handle the MW link

alarm first.

Step 2: Replace the PXC board .


MS_AIS

MS_AIS is an alarm indicating multiplex section alarm.

Possible Causes :

PXC board is faulty

Handing Procedure:

Step 1: Check whether the other microwave link alarm

such as MW_LOF, RADIO_RSL_LOW . Handle the MW link

alarm first.

Step 2: Replace the PXC board .

.


T_ALOS

T_ALOS is an alarm indicating that 2M signal is lost at the specific

port.

Possible Causes :

The port does not access the 2M service signal or not loopback

The trunk cable incorrectly connect DDF

Handing Procedure:

Step 1: Check whether the port access the 2M service signal . If no

signal access , loopback the port at DDF.

Step 2: Check whether the patching meet the planning and tightly

fixed.

.


UP_E1_AIS/ DN_E1_AIS

UP_E1_AIS/ DN_E1_AIS is an alarm indicating that 2M

up/down signal is abnormal.

Possible Causes :

The remote station does not access the 2M service

signal

Handing Procedure:

Step 1: Check whether The remote station does not

access the 2M service signal . If no need access 2M

service according to the planning, ignore the alarm.


TU_AIS

TU_AIS is an alarm indicating that 2M service has errors.

Possible Causes :

The data configuration is wrong

The PXC board is faulty

Handing Procedure:

Step 1: Check whether the cross-connection data is

correct.

Step 2: Perform a loopback operation to confirm which

side has the faulty.

Step 3: Replace the PXC at the faulty side.


ETH_LOS

ETH_LOS is an alarm indicating that the Ethernet port is disconnected.

Possible Causes :

The Ethernet port is disconnected

The Ethernet cable is faulty

The working mode of the port does not match that of the port at the remote end.

Handing Procedure:

Step 1: Check the planning with the Ethernet port , if no need connected , ignore the alarm.

Step 2: Check whether the Ethernet cable and connector are properly made and tightly fixed .

Step 3: Check whether the equipment connected to the port is faulty and whether the working mode of the port at both ends match .each other.

Step 4: Replace the Ethernet board that report the alarm.


TU_AIS_VC12/ TU_LOP_VC12

TU_AIS_VC12/ TU_LOP_VC12 is an alarm indicating that there are errors in VC-12 Level transmission.

Possible Causes :

The data configuration is incorrect.

The PXC board is faulty

The Ethernet board is faulty

Handing Procedure:

Step 1: Check whether the cross-connection data and Ethernet data are correct.

Step 2: Perform a loopback operation to confirm which side has the faulty

Step 3: Replace the PXC at the faulty side.

Step 4: Replace the Ethernet at the faulty side.

Thank youwww.huawei.com

Download - MODULE Alarm Analyze

Top Related