7 OptiX RTN 900 Troubleshooting ISSUE 1.00 PDF

OptiX RTN 900 Troubleshooting
47pt
OptiX RTN 900

Troubleshooting
www.huawei.com
Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.
35pt
Objectives
 Upon completion of this course, you will be able to:
32pt
 Describe general troubleshooting flow of OptiX RTN
910/950/980
 Outline the methods of faults analyzing and locating

) :18pt
 Perform the common troubleshooting for OptiX RTN
910/950/980
Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved. Page2
1
35pt
Contents
1. Methods of Analyzing and Locating Faults
32pt
2. Classified Troubleshooting Analysis
) :18pt
35pt General Troubleshooting

Procedure
Start
Contact Huawei
The fault No
32pt rectified? for technical
support
Observe and
record fault
phenomenon
Find solution
Yes together
) :18pt External Other handling Write fault and rectify fault
cause flow handling report
No
No
Analyze fault causes
and locate the fault The fault
rectified?
End Yes
Rectify fault
2
35pt
Basic Principles of Fault Locating
32pt
1 2 3
High-Severity
External First, Station First, Alarms First,
) :18pt
then Internal then Board then Low-
Severity Alarms
35pt
Common Methods of Fault Locating

 Continueda
32pt
Common Methods of Fault Locating
) :18pt
Alarm Replace- Test with
analysis Loopback RMON
ment instrument Resetting monitoring
Analyze first, then Loopback, and finally replace the board
3
35pt
Alarm Analysis
 Using NMS
32pt
 Comprehensive
 All alarms/performance events from the whole network
 Accurate
 Current alarms, history alarms, occurrence time and performance
) :18pt event data can be queried
 Observing indicators on the boards

 No alarm detailed and history alarms
35pt
Common Alarm Description

Alarm
32pt
Alarm Name Indication
Severity
HARD_BAD The board hardware is faulty
NESTATE_INSTALL Critical The NE is in the installation status.

) :18pt
NO_BD_SOFT the board software is lost
POWER_FAIL The power supply is in an abnormal state
Major
FAN_FAIL The fan is faulty
BD_STATUS The board is not in position
4
35pt
Common Alarm Description (Cont.)

Alarm
32pt
Alarm Name Indication
Severity
MW_LOF Loss of microwave frames
RADIO_RSL_LOW/ Critical ODU receiving power low / high

) :18pt
HIGH
CONFIG_NOSUPPORT Major Wrong configuration parameter in

ODU
MW_FEC_UNCOR Minor FEC can not be corrected in MW

frames
RADIO_MUTE Warning ODU is mute
35pt
32pt
Alarm Name Alarm Severity Indication
IF_CABLE_OPEN IF cable is uninstalled
MW_LIM Link ID mismatch in microwave frame.

) :18pt Major
RPS_INDI Radio protection (1+1 backup)
switched
MW_RDI Microwave remote defection.
LOOP_ALM Minor ODU/IF port was looped.
TEMP_ALARM ODU/IF temperature is abnormal.
5
35pt
32pt
Alarm Name Alarm Severity Indication
R_LOS Loss of SDH signal

Critical
Eth_LOS Loss of Ethernet signal
) :18pt
T_ALOS Los of 2 Mbit/s analog signal
Major
TU_AIS TU path has be interrupted
35pt
Case Analysis
MW_RDI
MW_LOF RPS_INDI
32pt
NE2 NE3
NE1
) :18pt
 Description
 NE1 & NE2 is 1+1 HSB configuration
 There was an alarm “MW_LOF" on NE1
 Alarm "MW_RDI", “RPS_INDI” on NE2
6
35pt
Loopback
 It is useful in the physical layer availability check, such as
32pt
the “signal loss”, “loss of frame” alarms
 It interrupts the traffic and inband DCN, must be carefully
) :18pt
Inloop Inloop
Ethernet RTN 910/950/980 ODU/IF

outloop outloop
Inloop
outloop
E1, STM-1
35pt
Replacement
 If any component is suspected to be faulty, replace the
32pt
component and locate the fault
 In the case of replacement, use one component that
works normally to replace one probably faulty
) :18pt
component to locate and rectify the fault
 The replaceable components include the equipment,

boards and cables
7
35pt
Test with Instrument

 This method is the most authoritative, but we must have
32pt
the devices in hand
Instrument Test item
Bit error testing device Bit error/traffic

) :18pt
Optical power meter Optical power
SDH analyzer Bit error/traffic/overhead

bytes ……
Multimeter Voltage/Resistance ……
Ethernet tester (E.g Ethernet service

SmartBits)
35pt
Resetting
 Resetting is a restoration scheme for application programs and
32pt
data configurations. When the component is not running
properly, after resetting, it will return to the normal state
 Resetting boards
) :18pt
 Resetting equipments by power off and on
 Resend the configuration
 Reset Modes:
 Warm reset loads the correct programs and data on the equipment
 Cold reset restores the correct programs and data before the CPU
power failure
8
35pt
RMON
 By using the remote monitoring (RMON), the Ethernet
32pt
port can be monitored
 History data is saved for the fault diagnosis
 Errors are detected and reported
) :18pt
 Detailed data is provided
35pt
Contents
1. Methods of Analyzing and Locating Faults
32pt
) :18pt
9
35pt
Contents
32pt
2.1 Radio Link Troubleshooting
2.2 Bit Errors in TDM Services Troubleshooting
2.3 Interconnection Troubleshooting with SDH Equipment

) :18pt
2.4 Interconnection Troubleshooting with PDH Equipment
2.5 Ethernet Service Faults Troubleshooting
2.6 Orderwire Faults Troubleshooting
35pt
Radio Link Troubleshooting

 When an NE reports MW_LOF or MW_FEC_UNCOR due to
32pt
failure or performance deterioration of a radio link, there
is a radio link fault
 The key to locating a microwave link fault is to check

) :18pt
whether the transmit power or the receive power are
abnormal, checking whether there is an external
interference as well
10
35pt
Radio Link Troubleshooting (Cont.)

Fault Common Fault Causes
32pt
The transmit power is The ODU is faulty or the frequency / power
abnormal wrong setting.
The antenna direction is not properly
adjusted or be moved.
The antennas have different polarization
) :18pt
directions since installed or after changing
the ODU.
The receive power is always
There is an obstacle in the transmit
lower than the normal value
direction.
The connection between the antenna and
the ODU are abnormally (loose).
The ODU is faulty or the transmit power is
abnormal on the opposite ODU.
35pt

32pt
The receive power is abnormal
There is external interference
due to slow up fading
The receive power is abnormal
The fading margin is insufficient
due to slow down fading
) :18pt The receive power is abnormal

The multipath fading is fast
due to fast fading
The receive power is normal,

but faults occur on the radio There is external interference
link intermittently
11
35pt

 Fault Locating Methods
32pt  Check whether the ODU is muted, powered off, or looped back. Check
whether the data configuration is correct
 Check whether the ODU and the IF board are faulty
 If the transmit power is abnormal, replace the ODU
) :18pt  If the receive power is abnormal, analyze and locate the causes according
to the fading type
 If the receive power is normal but faults occur on the radio link
intermittently, check whether there is interference before you proceed
 If the transmit power and receive power are normal, perform loopback
operations
35pt Bit Errors in TDM Services

Troubleshooting
 When an NE reports an alarm or a performance event on the IF board,
32pt regenerator section (RS), multiplex section (MS), higher order path (HP), or
lower order path (LP), there are bit errors in services
 Locating Methods
 Analyze the equipment alarms and performance events
) :18pt
 First analyze RS bit errors, then MS bit errors, HP bit errors, and finally LP bit
errors or check whether the overlapping part of the service paths is faulty
 When multiple paths have bit errors, first check whether the overlapping part of
the service paths is faulty
 If you fail to locate the fault by analyzing the alarms and performance events,
perform loopback operations section by section
 Replace the parts whose performance may deteriorate with new ones
12

Troubleshooting (Cont.)
32pt
The radio link is faulty. Check whether the
MW_FEC_UNCOR or RPS_INDI alarm is reported. If yes,
There are IF bit errors the radio link is faulty.
The IF board at the local end or opposite end is faulty
The line is faulty.
‟ The common causes for bit errors on the optical line
) :18pt are as follows: the optical fiber line, the optical power
is abnormal, the fiber performance deteriorates, or the
fiber connector is not clean.
‟ In the case of bit errors on the radio link, check
There are RS bit errors whether the MW_FEC_UNCOR or RPS_INDI alarm is
reported. If yes, the radio link is faulty.
The line processing unit or IF board is faulty.
The clock unit is faulty.
The quality of the clock over the network declines.
When the quality of the clock over the network
declines, a pointer justification event occurs.

32pt
The line processing unit or IF board is faulty
The quality of the clock over the network declines
There are not any RS bit errors but
there are MS bit errors or HP bit When the quality of the clock over the network
errors declines, a pointer justification event occurs
The working temperature of the line processing unit or
IF board is excessively high
) :18pt
The tributary board is faulty
The cross-connect unit is faulty
The working temperature of the board is excessively
high
There are only LP bit errors The working temperature of the cross-connect unit is
excessively high.
There is a power surge or an external interference
source, or the equipment is not properly grounded.
(This cause does not need to be considered during the
troubleshooting of a Hybrid IF board.)
13
35pt Interconnection Troubleshooting with

SDH Equipment
 In the case of interconnection with SDH/PDH equipment,
32pt
there is an interconnection fault if the SDHPDH service
cannot be transmitted between the equipment sets
 Fault Causes
) :18pt
 The VC-12 numbering method of the OptiX equipment is
different from the numbering method of the equipment of
certain vendors
 The overhead bytes at both ends are inconsistent
 The indexes of the SDH interfaces do not meet the

requirements
35pt Interconnection Troubleshooting with

PDH Equipment
 In the case of interconnection with PDH equipment, there
32pt
is an interconnection fault if the PDH service cannot be
transmitted between the equipment sets.
 Fault Causes
) :18pt
 There is an impedance mismatch between interfaces
 The equipment is not grounded properly
 The cable performance deteriorates

 The indexes of the PDH interfaces do not meet the
requirements
14
35pt Ethernet Service Faults

Troubleshooting
 An Ethernet service fault
32pt
 Ethernet service interruption
 Ethernet service deterioration
 Fault Causes
) :18pt
 The possible human factors are as follows:
 An Ethernet board loopback or a transmission line loopback occurs
 The parameter settings of the Ethernet ports, such as the port enabled
state, working mode, and flow control, are different from the
parameter settings of the Ethernet ports on the interconnected
equipment
 The service configuration is incorrect.

 Fault Causes
32pt
 The equipment at the local end is faulty
 The line board is faulty or has bit errors
 When the AM function is enabled, the Ethernet service

) :18pt
bandwidth decreases due to the downward AM switch
 The interconnected equipment is faulty
 The network cable is faulty
 The external electromagnetic interference is severe
15

32pt
 Rectify the human-caused faults such as a loopback and a
data configuration error
 Locate the fault cause according to the equipment alarms

) :18pt
 Locate the fault cause according to the RMON performance
events and alarms
35pt
MPLS Tunnels Troubleshooting

 MPLS tunnels problem can use the MPLS OAM function or
32pt
MPLS Ping/Traceroute function
 Common faults of MPLS tunnels are as follow:
 MPLS tunnels fail to be created, and services are unavailable
) :18pt  MPLS tunnels are faulty, and services are interrupted
 MPLS APS switching fails, services are interrupted, and packet loss
or bit errors occur
16
35pt MPLS Tunnels Troubleshooting

(Cont.)
32pt
 Check whether the data is modified, whether the line is
looped back, and whether any boards are replaced
 Handle the link alarms on the MPLS server trail

) :18pt
 Locate the faulty section by using the LSP Traceroute
function
 Locate the fault by replacing boards
35pt
CES Service Troubleshooting
32pt
 Bit errors taken place or service Correspondin
Impact
interrupted g boards:
„CXPAR
 Hardware failure or client signal loss
Caus „CSHN
) :18pt
 The failure in PW, tunnel or radio „ML1 / MD1
e
link „CD1
 Alarms like T_ALOS, AIS, etc. „ISU2 / ISX2

Symptom „IFU2 / IFX2
reported on corresponding CES ports
17
35pt CES Service Troubleshooting

(Cont.)
Symptom Alarm Reported Board
32pt
HARD_BAD, TEMP_ALARM,
CXPAR, CSHN, ML1 /
WRG_BD_TYPE, BUS_ERR,
The CES service MD1
BD_STATUS, CES_LOSPKT_EXC
is interrupted
AM_DOWNSHIFT
ISU2, ISX2, IFU2, or IFX2
MW_CFG_MISMATCH
) :18pt
CES_JTROVR_EXC,
CXPAR, CSHN, ML1,
CES_JTRUDR_EXC,
MD1
The CES service CES_MALPKT_EXC,
is degraded CES_MISORDERPKT_EXC,
CES_STRAYPKT_EXC
AM_DOWNSHIFT
MW_CFG_MISMATCH
35pt CES Service Troubleshooting

(Cont.)
 Replacing boards
32pt
 Meter testing
- Optical power meter - HARD_BAD
- SDH analyzer - COMMUN_FAIL
- BER tester - BUS_ERR
Fault Locating
) :18pt
Methods
 Other layer
 Client side
- PWE3
- Laser
- MPLS Tunnel
- Cable
- Radio link
- Loop
- Clock
18
35pt
ATM Services Troubleshooting

 ATM services are interrupted if they are completely unavailable.
32pt
ATM services are degraded if they have packet loss or incorrect
packets
 Fault Causes
) :18pt  Incorrect operations are performed
 The local NE is faulty
 The transmission link is faulty or has bit errors
 Service bandwidth decreases due to an AM downshift
 The opposite NE is faulty
 External electromagnetic interference is severe
35pt ATM Services Troubleshooting

(Cont.)
32pt
BD_STATUS, ALM_IMA_LIF,
ALM_IMA_LODS, CXPAR, CSHN, ML1 /
The ATM service ALM_IMA_RE_RX_UNUSABLE, MD1
is interrupted ALM_IMA_RE_TX_UNUSABLE,
) :18pt IMA_GROUP_LE_DOWN,
IMA_GROUP_RE_DOWN, LCD
AM_DOWNSHIFT
MW_CFG_MISMATCH
CXPAR, CSHN, ML1,
ALM_IMA_LIF, ALM_IMA_LODS,
MD1
The ATM service ALM_IMA_RE_RX_UNUSABLE,
is degraded ALM_IMA_RE_TX_UNUSABLE, OCD
AM_DOWNSHIFT
MW_CFG_MISMATCH
19
35pt Ethernet Services Carried by PWs

Troubleshooting
 Ethernet services are interrupted if they are completely
32pt
unavailable. Ethernet services are degraded if they have great
delays, packet loss, or incorrect packets
 Fault Causes
) :18pt  Incorrect operations are performed
 The local NE is faulty
 The transmission link is faulty or has bit errors
 Service bandwidth decreases due to an AM downshift
 The opposite NE is faulty
 External electromagnetic interference is severe
35pt Ethernet Services Carried by PWs

32pt
BD_STATUS
The Ethernet EG2D, EM6F, or EM6T
service is COMMUN_FAIL, LAG_DOWN
interrupted ETH_LOS, ETH_EFM_LOOPBACK, or
) :18pt LOOP_ALM
LASER_MOD_ERR EM6F, or EG2D
HARD_BAD or TEMP_ALARM
The Ethernet EG2D, EM6F, or EM6T
FLOW_OVER or
service is LAG_MEMBER_DOWN
degraded
AM_DOWNSHIFT ISU2, ISX2, IFU2, or IFX2
20
35pt
Orderwire Faults Troubleshooting

 If orderwire calls cannot get through when services are
32pt
normal, there is an orderwire fault
 Fault Causes
 The phone set is set incorrectly
) :18pt
 The phone line is connected incorrectly
 The orderwire is configured incorrectly
 The orderwire unit is faulty
 The system control unit is faulty
 The line unit or radio link is faulty
35pt Orderwire Faults Troubleshooting

(Cont.)
32pt
 Check whether the phone set is set correctly, whether the
phone line is connected correctly, and whether the
orderwire is configured correctly
) :18pt  Replace the possibly faulty board to locate the fault
21
35pt
Summary
 General troubleshooting flow of OptiX RTN 910/950/980
32pt
 Basic principles of fault locating
 Common methods of fault locating
 Classified troubleshooting analysis

) :18pt
Thank you
www.huawei.com
22

7 OptiX RTN 900 Troubleshooting ISSUE 1.00 PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

7 OptiX RTN 900 Troubleshooting ISSUE 1.00 PDF

Enviado por

Direitos autorais:

Formatos disponíveis

OptiX RTN 900 Troubleshooting

OptiX RTN 900

Copyright © 2011 Huawei Technologies Co., Ltd. All rights reserved.

 Outline the methods of faults analyzing and locating

2. Classified Troubleshooting Analysis

35pt General Troubleshooting

Basic Principles of Fault Locating

Common Methods of Fault Locating

Analyze first, then Loopback, and finally replace the board

 Observing indicators on the boards

Common Alarm Description

NESTATE_INSTALL Critical The NE is in the installation status.

BD_STATUS The board is not in position

Common Alarm Description (Cont.)

RADIO_RSL_LOW/ Critical ODU receiving power low / high

CONFIG_NOSUPPORT Major Wrong configuration parameter in

MW_FEC_UNCOR Minor FEC can not be corrected in MW

RADIO_MUTE Warning ODU is mute

Common Alarm Description (Cont.)

IF_CABLE_OPEN IF cable is uninstalled

MW_LIM Link ID mismatch in microwave frame.

MW_RDI Microwave remote defection.

LOOP_ALM Minor ODU/IF port was looped.

TEMP_ALARM ODU/IF temperature is abnormal.

Common Alarm Description (Cont.)

R_LOS Loss of SDH signal

 It interrupts the traffic and inband DCN, must be carefully

Ethernet RTN 910/950/980 ODU/IF

 The replaceable components include the equipment,

Test with Instrument

Instrument Test item

Bit error testing device Bit error/traffic

Optical power meter Optical power

SDH analyzer Bit error/traffic/overhead

Ethernet tester (E.g Ethernet service

 Resend the configuration

2. Classified Troubleshooting Analysis

2.2 Bit Errors in TDM Services Troubleshooting

2.3 Interconnection Troubleshooting with SDH Equipment

2.5 Ethernet Service Faults Troubleshooting

2.6 Orderwire Faults Troubleshooting

Radio Link Troubleshooting

 The key to locating a microwave link fault is to check

Radio Link Troubleshooting (Cont.)

Radio Link Troubleshooting (Cont.)

) :18pt The receive power is abnormal

The receive power is normal,

Radio Link Troubleshooting (Cont.)

35pt Bit Errors in TDM Services

35pt Bit Errors in TDM Services

35pt Bit Errors in TDM Services

35pt Interconnection Troubleshooting with

 The indexes of the SDH interfaces do not meet the

35pt Interconnection Troubleshooting with

 The equipment is not grounded properly

 The cable performance deteriorates

35pt Ethernet Service Faults

 Ethernet service deterioration

 The service configuration is incorrect.

35pt Ethernet Service Faults

 The line board is faulty or has bit errors

 When the AM function is enabled, the Ethernet service

 The interconnected equipment is faulty