Optix RTN 600 Troubleshooting: Internal

Internal
OptiX RTN 600 Troubleshooting
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

Objectives
 Upon completion of this course, you will be able to:
 List the common analysis methods of fault locating

 Outline the Fault Handling Flow

Analyze the typical faults: traffic interruption, error
bit, etc
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 2

Content
1. Troubleshooting Preparation
2. Troubleshooting Idea and Methods
3. Classified Troubleshooting Examples

Requirements for Maintenance Personnel
 Be familiar with hardware system and Digital Microwave
Communication principle, particularly in the alarm signal

flow
 Alarm/performance generation principle
 Master the basic operations of the transmission
equipment
 NMS, testing devices, loopback, board replacement

Requirements for Maintenance Personnel
 Familiar with the network under maintenance
 Network topology, network protection, traffic

configuration
 Collect and save on-site data
 System alarms, performance events data,

configurations, operation records of NMS

Flow Chart
Start
If the fault does not affect the network

element access, query the alarm and
NO follow the “maintenance manual” ;
On site or not If problems cannot be solved through
the above methods or remote access is
YES not permitted., please deal with the
problems on site.
water flowing or fire? If all indicators

Hardware YES
off, check the PXC board power input;
problems? And then check the SCC board
NO indicators status.

Flow Chart
Please replace the corresponding board
if report the alarm below: A_LOC,
YES DBMS_PROTECT_MODE, HARD_BAD,
Query alarms POWER_ALM, POWER_FAIL,
RADIO_TSL_HIGH, RADIO_TSL_LOW,
NO RP_LOC, T_F_RST , T_FIFO_E,
R_F_RST.
Follow the “maintenance manual” to
handle the alarms below ：
APS_MANU_STOP, ALM_RTC_FAIL,
APS_FAIL, BD_NOT_INSTALLED,
R_LOS,R_LOF,CONFIG_NOSUPPORT,R
ADIO_MUTE,RADIO_RSL_LOW,MW_LO
F,MW_LIM
Transfer to
SDH process

Content

One question
 What is the key for troubleshooting ?
 To locate a failure ACCURATELY in one station

Basic Principles for Locating Faults
 External first, then internal
Exclude external problems first

− IF cable, switch failure
− Power failure, grounding
 Station first, then boards
Try your best to locate the troubles to one node

Basic Principles for Locating Faults
 Microwave side first, then SDH side
 First check the Microwave side problems

 Higher-severity alarms first, then Lower-severity alarms
 First analyze critical/major alarms

 Then come to minor/warning alarms

Common Methods of Fault Locating
 Alarm and performance analysis
 Loopback
 Replacement
 Configuration data analysis
 Configuration modification
 Test with instruments
 Rule of thumb

Alarm and Performance Analysis
How to obtain alarms  O bs e rve ind ic a to rs o n
 Us e NMS and performance? bo a rd s a nd c a bine ts
•Comprehensive
•Not detailed
•All alarms/performance events
•No history alarms
from the whole network
•Accurate
• Current alarms, history
alarms, occurrence time and
performance event data can be
queried.

Obtain alarm and Select the key alarm or

performance events performance events
Limit the troubles to a

Analyze reasons
certain range or a node

1 2 3
MW-RDI
R-LOF
HSB-INDI
 Description
NE1 & NE2 is STM-1 capacity 1+1 configuration;

After switching, that was an alarm “R_LOF" on NE1;
Alarm "MW_RDI", “HSB_INDI” on NE2.

 Possible reasons:
Second ODU is faulty;
IF-board is faulty;
TX/RX Frequencies of the second (protection) ODU are
different from the other three ODUs on this hop;
Hybrid Coupler is faulty;
There is water in hybrid coupler;
IF-Jumper is faulty;
IF-board is faulty.

Loopback
What is loopback?
Loopback is the most common, most efficient

method in troubleshooting.
Inloop Inloop
Line RTN equipment Line
outloop outloop
Inloop
outloop
Tributary

Loopback
Board Loopback Loopback Loopback
Application
involved options tools level
Separate switching faults from transmission

Tributary Inloop/ Loopback Loopback at faults. Determine the tributary board failure
board outloop cable, NMS path level roughly. Be unnecessary to modify service
configuration.
Loopback by Locate single station faults. Roughly

Inloop/ Patch fiber,
Line board optical determines the line board failure. Be no
outloop NMS
interface need to modify service configuration
Inloop/ Loopback by the ODU supports RF port inloops and IF

IF/RF port outloop NMS the IF/RF port port inloops/outloops, separate the faults in
the IFunits or the ODU
May interrupt the traffic and ECC

Notes Software loopback is not a thorough method
Will automatically be removed in 5 minutes (provisionable)

Loopback
 Procedures
 Draw the traffic flow diagram

 Loopback section after section to locate the faulty NE
 Locate the faults to certain boards

Replacement
Objective Application
Fiber External faults
Cable Boards faults
Module
Board
Effective thoughts
MSP switch
SNCP switch
1+1 SD/FD switch
1+1 HSB switch

Configuration Data Analysis
 Query & Analyze the configuration
 Timeslot configuration
 J1 or C2 bytes
 LU 、 TU 、 IF unit or ODU loopback
 SNCP or MSP switching conditions (e.g. MS-SD)
 External commands (e.g. locked switch)
 The consistency of the frequency between two nodes
 The appropriate transmission power of the ODU

Configuration Modification
Objective Application Examples

Port No spare boards
Timeslot Restore the traffic
Slot temporarily

Testing Instrument
Instrument Test item
Bit error testing device Bit error/traffic
Optical power meter Optical power
SDH analyzer Bit error/traffic/overhead bytes ……
Multi-meter Voltage/current/resistance
This method is the most authoritative, but we must have the devices in hand.

Rule of Thumb
Last resort
 Reset board
 Power off and on
 Resend the configuration
 Do not consider them as a panacea
 They are not helpful for us to find the

cause of the failure.

Common Methods of Fault Locating
Methods Application Features
1. Evaluate the whole network situation.
Alarm and 2. Locate the faulty point preliminarily based on the collected data.
performance Universal
analysis 3. Cause no negative effect on normal services
4. Depend on the NMS
Locate the fault to a single 1. Independent of alarm and performance event analysis
Loopback station or board 2. Rapid and effective
1. Convenient
Locate the fault to a board or
Replacement 2. Require spare parts/equipment.
isolate external faults
3. Applied with other methods
1. Can find the fault cause.
Configuration Locate the fault to a single 2. Fault locating time is longer.
data analysis station or board
3. Depend on the NMS
Configuration 1. Have a high risk.
Locate the fault to a board
modification 2. Depend on the NMS
Isolate external faults and 1. A general method with high accuracy

Test with resolve interconnectivity 2. Have certain requirements for the meters.
instruments problem 3. Applied with other methods
1. Fast fault handling
Experience Special cases 2. High probability of mistake
3. Need experience accumulation.

Common Troubleshooting Sequence
Exclude external troubles
Switching Replacement
problem?
Fiber problems? Instrument
testing
Trunk cable?
Loopback
Power supply
system? Alarm/performan
Grounding ce analysis
problem?
Locate troubles to one NE
Loopback Replacement
Loopback
Alarm/performance analysis
Alarm/performance analysis
Configuration analysis
Locate the troubles to one board Configuration modification
Rule of Thumb

Contents

Classified Troubleshooting Examples
 Traffic Interruption
 Wrong configuration
 Bit Errors

Traffic Interruption
1 2
16 16
E1 E1
 Description
 Hardware version is V1R2, can not configure 16E1 services ( just

can configure 11E1 services);
 There are no other services;
 The link between NE1 & NE2 was configured 1+1HSB;

 Handling process
Check the license
License just can support 23 E1( 7 E1

for free) and the 1+1 HSB need the
32 E1 license capacity
Change the license
Delete the 1+1 HSB configuration
Generate the some alarms

1 2
MW-LOF LOG_OUT
16 16
E1 E1
Other configurations YES Check the ODU
be changed ? launch frequency or
the receiving power
NO
Check the
configuration for Use other
1+1HSB configuration
guides

Wrong operation process to
delete the 1+1 HSB
Analysis: configure the

1+1HSB, both ODUs are set
unmute status; After delete
the protection
configuration, both ODUs
will be disturbed each other
because they have same
launch frequency and
polarization ;
Shut down the ODU and configure

the 1+1 HSB again

 Bit Errors

Wrong configuration
1 2
Config_nosupport
16 16
E1 E1
 Description
 NE1 configure 1+0 protection, at the 15 GHz band, and with 16E1 PDH;
 NE1 ODU remains mute though it is set to the unmute status;
 NE1 ODU transmits signals at the power of -55 dBm though its launched
power is set to 21 dBm;
 NE1 generates the Config_nosupport alarm.

Wrong configuration
The launched power of ODU is out of
the range?
The range is -6 to 24dbm, and the

launched power is 21 dbm;
The transmit frequency of ODU is out

of the range?
The range is 15GHZ band, and the

actual frequency is 1.46655 GHZ
The designed frequency is 14.6655

GHZ; so change the transmit
frequency to 14.6655 GHZ

 Bit Errors

Bit Errors
1 2
MW_RDI
MW_LOF
 Description
 Many bit errors generate in the microwave equipment for

the interval is between 15 to 25 minutes;
 The services are interrupted for 5 to 8 seconds each time;
 The equipment generate MW_RDI and MW_LOF alarms;

Bit Errors
Yes
Wrong configuration? Inconsistent working modes or
No working frequencies of the ODUs
at the local and peer ends?
Hardware problems? No
No
Query the alarms
MW_RDI: MW_LOF:
When this alarm is reported, it The performance of the microwave link
means that the link is faulty and deteriorates.
consequently the peer end receives The receive function of the local end fails.
error bits. The working modes of the ODUs in the local and
peer ends are different.
The working efficiency of the ODUs in the local and
peer ends are different.

Bit Errors
The MW_RDI and MW_LOF alarms are

related to the link performance
deterioration
a new link is created and the frequency

interference occurs between the new
and existing links
Guess: other company

After modify the receive and transmit creates a new microwave
powers of the ODUs at the local and hop and the new
peer ends, the problem is solved. microwave hop shares
the site with Huawei.

Questions
 What is the key of troubleshooting?
 To locate a failure ACCURATELY in certain station

 What is the principle of troubleshooting?
 External first, then internal
 Station first, then boards
 Microwave first, then SDH
 Higher-severity alarms first, then lower-severity alarms

Summary
 Which methods for troubleshooting?
 Alarm and performance analysis
 Loopback
 Replacement
 Configuration Data Analysis
 Configuration Modification
 Test with instruments
 Rule of Thumb

Thank You
www.huawei.com

Optix RTN 600 Troubleshooting: Internal

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Optix RTN 600 Troubleshooting: Internal

Hochgeladen von

Copyright:

Internal

OptiX RTN 600 Troubleshooting

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

 List the common analysis methods of fault locating

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 2

2. Troubleshooting Idea and Methods

3. Classified Troubleshooting Examples

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 3

 Be familiar with hardware system and Digital Microwave

Communication principle, particularly in the alarm signal

 Alarm/performance generation principle

 Master the basic operations of the transmission

 NMS, testing devices, loopback, board replacement

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 4

 Familiar with the network under maintenance

 Network topology, network protection, traffic

 Collect and save on-site data

 System alarms, performance events data,

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 5

If the fault does not affect the network

water flowing or fire? If all indicators

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 6

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 7

2. Troubleshooting Idea and Methods

3. Classified Troubleshooting Examples

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 8

 To locate a failure ACCURATELY in one station

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 9

Exclude external problems first

Try your best to locate the troubles to one node

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 10

 First check the Microwave side problems

 First analyze critical/major alarms

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 11

 Configuration data analysis

 Test with instruments

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 12

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 13

Obtain alarm and Select the key alarm or

Limit the troubles to a

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 14

NE1 & NE2 is STM-1 capacity 1+1 configuration;

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 15

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 16

Loopback is the most common, most efficient

Line RTN equipment Line

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 17

Separate switching faults from transmission

Loopback by Locate single station faults. Roughly

Inloop/ Loopback by the ODU supports RF port inloops and IF

May interrupt the traffic and ECC

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 18

 Draw the traffic flow diagram

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 19

Fiber External faults

Cable Boards faults

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 20

 LU 、 TU 、 IF unit or ODU loopback

 SNCP or MSP switching conditions (e.g. MS-SD)

 External commands (e.g. locked switch)

 The consistency of the frequency between two nodes

 The appropriate transmission power of the ODU

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 21

Objective Application Examples

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 22