ZTE ZXSDR NodeB Troubleshooting

8/11/2019 ZTE ZXSDR NodeB Troubleshooting

1/21

Internal Only

ZXSDR NodeB Troubleshooting

Applicable to Staff with Skill Certificate Level II or Lower

Released by GU Product Support Dept.


2/21

Internal Only

Version Introduction

References:

1.

2.

Version Date Author Checked

by

Amendment Record

R1.0 2011-03-24 Zhao chenmu *** None


3/21

Internal Only

Course Objectives:

To understand the usage of trouble shooting tools

To master the trouble shooting flow


4/21

Internal Only

Content

Troubleshooting Tools

Troubleshooting & solution flow

Common Trouble examples


5/21

Internal Only


EOMS (Embedded Operations and Maintenance Subsystem)Display Board StatusDouble-click the board on the NodeB rack layout;

A dialog box will be displayed, listing detailed information including

Board info, Board status, and alarm info.

detail in online manual.

EFMS (Embedded Faults Maintenance Subsystem)

Alarm Browse window:displaying fault alarm information

detail in online manual.


6/21

Internal Only

Content





7/21

Internal Only

Trouble Shooting and Solution Flow

Step 1 Find a fault alarm

Step 2 Information collection

Step 3 Information analysis

Step 4 Solution


8/21

Internal Only

Find a Alarm on EOMS


9/21

Internal Only

Find a Alarm on EFMS


10/21

Internal Only

Information Collection

These information need to be collected Alarm Code

Help to index the detail about the alarm

Alarm Name and sub-code

Reflects such content as fault cause and fault phenomenon in a simpleand straightforward way .

Alarm Source

Show where the alarm was invoked

Alarm severity

Four alarm levels indicated in descending order of severity isCrit ical, Major, Minor, and Warning .

Critical = must be handled at once

Major = should be handled during working-hours.

Minor = to be handled at proper time so as to avoid serious fault.

Warning= necessary to be handled so as to avoid more serious fault.


11/21

Internal Only

Information Analysis

Double click on the alarm, on the solution page ,analysis will be shown as following:

1. Detail Description

2. Possible Causes

3. Impact on system

4. System Actions


12/21

Internal Only

Trouble Solution

Double click on the alarm, on the solution page ,solution will be shown as below:

Handling Suggestions

This can also be shown in the AlarmSolutions

document by indexing the alarm code.


13/21

Internal Only

Content





14/21

Internal Only

Common Trouble Examples

23-Ethernet light and electricity lose(demo & practice)

14-Loss of Signal at Ir interface(demo & practice)

13-Board hardware fault(demo & practice)

1009-Antenna over VSWR alarm(demo & practice)

5-Clock reference source is lost(demo & practice)

7- Clock reference source is degraded

34 Hardware alarm

516 - SCTP association is interrupted.

1028 abnormal power

2009 - SNTP time adjustment failure alarm


15/21

Internal Only

e.g 1: 23-Ethernet light and electricity lose

Detail DescriptionThis alarm is given when FE port is

configured, but network cable is not well

connected with its peer end.

Possible Causes

Net cable failureThe opposite net port is faulty.

The local net port is faulty.

Impact on systemBoard operation is normal.The net port data

transmission is interrupted, and theservice is not available.

System ActionsWhen this alarm occurs, the system will set

the link via the network port to be fault.

Handling SuggestionsCheck the net cable for any failure

Check the counterpart net port for anyfailure.

Check the local net port for any failure.


16/21

Internal Only

e.g 2: 14-Loss of Signal at Ir interface

Detail DescriptionOptical signal between BBU and RRU is lost,

which will affect system normal running.

Possible CausesFailure in the fiber optics, the optical module,

or the connection on this level board.

The board on the lower level is not properlypowered on.

Failure in the fiber optics, the optical moduleon the lower level board.

Hardware failure on the lower level board.

Impact on systemThe board connected with the optical port is faulty.

Service Impact:

The board with the failure works normally, but theboard with optical port has failure.

The "Loss of Signal at Ir interface" alarm occurred tothe FS functionality board during the RRU resetprocess is an accompanying alarm. Theservices beard by the system will be interruptedduring the reset process.

If the alarm occurs to the FS functionality board, allthe services of the system will be interrupted.

If the alarm occurs to the RTR, the services beardon the lower level RRU will be interrupted.

System ActionsNone.

Handling SuggestionsCheck for the failure in the fiber optics, the

optical module, or the connection on this

board.

Check the power supply to the lower levelboard.

Check for the failure in the fiber optics, the

optical module.

Check for the possible hardware failure with

the lower level RRU.


17/21

Internal Only

e.g 3: 13-Board hardware fault

Detail DescriptionWhen the board hardware

initialization is failed or it cannot

work normally due to hardware

fault, this alarm is reported.

Possible CausesBoard hardware fault

Impact on systemThe board is faulty.

The board fails to provide bearerservice..

System ActionsThe board status is changed to be

fault by the system.

Handling SuggestionsReset the board.

Replace the board.


18/21

Internal Only

e.g 4: 1009-Antenna over VSWR alarm

Detail DescriptionVSWR at antenna port is > 3.0

Possible CausesAntenna feeder is faulty.

Board is faulty.

Impact on systemBoard operation is normal.

There is no transmission power

output for the RF channel.

Service interruption occurs.

System ActionsNone

Handling SuggestionsCheck antenna feeder.

Check the VSWR of antenna

feeder by level.

Check RRU.


19/21

Internal Only

e.g 5: 5-Clock reference source is lost

Detail DescriptionWhen main control board cannot detect

signal input from external referenceclock source, it works in free oscillationstate. When this happens, the systemwill report this clock reference sourcelost alarm.

Possible CausesThe configured clock reference source does

not exist.Failure with the external reference clock or

its cable.

The board failure.

Impact on systemBoard operation is normal.

When E1 connection is used by Iub interface,then periodical slide code might occur to

the Iub interface. When FE connection isused by Iub, then there is no SystemImpact.

The impact to the soft handover betweenNode B base station: over a long periodof the alarm, the accuracy of the Node Bclock might degenerate and fail to meetthe 3GPP requirement and reduces thesuccess rate of soft handover.

System ActionsNone

Handling SuggestionsCheck if an incorrect reference

source is configured.

Check if the external clock

reference is correct.

if the board failure then Reset the

board or replace the board.


20/21

Internal Only

Chapter/Course Review

What tools can you use for trouble shooting

What is the trouble shooting flow


21/21

Internal Only

ZTE ZXSDR NodeB Troubleshooting

Documents

Transcript of ZTE ZXSDR NodeB Troubleshooting