ZXSDR NodeB Troubleshooting

ZTE University

Content

Troubleshooting Tools Troubleshooting & solution flow Common Trouble examples

Troubleshooting Tools

EOMS (Embedded Operations and Maintenance Subsystem)

Display Board Status

Double-click the board on the NodeBrack 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

Content

Troubleshooting Tools Troubleshooting & solution flow Common Trouble examples

Trouble Shooting and Solution Flow

Step 1 Find a fault alarm Step 2 Information collection Step 3 Information analysis Step 4 Solution

Find a alarm on EOMS

Find a alarm on EFMS

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 simple and straightforward way .

Alarm SourceShow where the alarm was invoked

Alarm severityFour alarm levels indicated in descending order of severity is Critical, Major, Minor and Warning .

Critical = must be handled at onceMajor = 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.

Information analysis

Double click on the alarm, on the solution page , analysis will be shown as following: Detail Description Possible Causes Impact on system System Actions

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 Alarm Solutions document by indexing the alarm code

Content

Troubleshooting Tools Troubleshooting & solution flow Common Trouble examples

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

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

Detail Description This alarm is given when FE

port is configured, but network cable is not well connected with its peer end.

Possible Causes Net cable failure The opposite net port is

faulty. The local net port is faulty.

Impact on system Board operation is

normal.The net port data transmission is interrupted, and the service is not available.

System Actions When this alarm occurs, the

system will set the link via the network port to be fault.

Handling Suggestions Check the net cable for any

failure Check the counterpart net

port for any failure. Check the local net port for

any failure

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

Detail Description Optical signal between BBU and RRU is

lost, which will affect system normal running.

Possible Causes Failure in the fiber optics, the optical

module, or the connection on this level board.

The board on the lower level is not properly powered on.

Failure in the fiber optics, the optical module on the lower level board.

Hardware failure on the lower level board.

System Actions None.

Impact on system Service Impact:

The board connected with the optical port is faulty.

Service Impact: The board with the failure works normally,

but the board with optical port has failure. The "Loss of Signal at Ir interface" alarm

occurred to the FS functionality board during the RRU reset process is an accompanying alarm. The services beard by the system will be interrupted during the reset process.

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

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

Handling Suggestions Check for the failure in the fiber optics, the

optical module, or the connection on this board.

Check the power supply to the lower level board.

Check for the possible hardware failure with the lower level RRU.

e.g 3: 13-Board hardware fault

Detail Description When the board hardware

initialization is failed or it cannot work normally due to hardware fault, this alarm is reported.

Possible Causes Board hardware fault

Impact on system The board is faulty. The board fails to provide

bearer service..

System Actions The board status is changed

to be fault by the system.

Handling Suggestions Reset the board. Replace the board

e.g 4: 1009-Antenna over VSWR alarm

Detail Description VSWR at antenna port is >

3.0

Possible Causes Antenna feeder is faulty. Board is faulty.

Impact on system Board operation is normal. There is no transmission

power output for the RF channel. Service interruption occurs.

System Actions None

Handling Suggestions Check antenna feeder. Check the VSWR of antenna

feeder by level. Check RRU.

e.g 5: RRU RTWP abnormal

Detail Description RRU's RTWP exceed threshold

Possible Causes1.Poor antenna connection, or

Feeder/Jumper defect.2.LNA defect.3.RRU internal poor connection.4.RRU internal receiver circuit

defect. Impact on system

I. Board Status: Board Operation is normal.

II. Service Impact: Service coverage extent is

affected.

System Actions None

Handling Suggestions1. The antenna feeder system is

faulty and Antenna VSWR alarm or Remote antenna over VSWR alarm occurs. Resolve the two alarms first.

2. Diversity antenna that is configured in the system does not exist (such as indoor coverage and outdoor full direction site) and there is no load connected to the RRU diversity. Connect the diversity with proper load.

3.If Rx_In port is used, check the connection and the other end RRU running status.

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

Detail Description When main control board cannot

detect signal input from external reference clock source, it works in free oscillation state. When this happens, the system will report this clock reference source lost alarm.

Possible Causes The configured clock reference

source does not exist. Failure with the external reference

clock or its cable. The board failure.

System Actions None

Impact on system Board operation is normal. When E1 connection is used by Iub

interface, then periodical slide code might occur to the Iub interface. When FE connection is used by Iub, then there is no System Impact.

The impact to the soft handover between Node B base station: over a long period of the alarm, the accuracy of the Node B clock might degenerate, and fail to meet the 3GPP requirement and reduces the success rate of soft handover.

Handling Suggestions Check 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

e.g 7:SCTP association broken

Detail Description SCTP association broken

Possible Causes Physical connection down Configuration illegal

System Actions None

Impact on system Fail to enable Iub

interfacetransfers

Handling Suggestions Check the physical

connection between SDR and RNC

e.g 8: SCTP stream number mismatch

Detail Description SCTP stream number mismatch

Possible Causes The number of in/out SCTP streams configured at

Node B and that configured at RNC are inconsistent.

System Actions None

Impact on systemI. Board Status:

Board operation is normal.II. Service Impact:

The cell can be established, but subsequent NBAP process might fail. UE access fails.

Handling Suggestions On the NetNumen M31

configuration management interface (Transmission Layer

Management in IUB Transmission (Full IP)), check the number of in/out SCTP streams configured at Node B. Check the corresponding configuration at RNC. Ensure that the configuration at both ends is consistent.

e.g 9: incorrect board in slot

Detail Description When the main control

board detects that the board inserted at foreground differs from the actually configured board, this alarm is reported.

Possible Causes The board type configuration

at NetWork Management is incorrect, or the board is incorrectly inserted at BaseStation.

System Actions None

Impact on systemI. Board Status:

Board operation is normal.

II. Service Impact: Board functions improperly,

and board services are down.

Handling Suggestions In Configuration

Managerment, reconfigure the correct board type, or insert a correct board at foreground.

e.g 10:Over-temperature shutdown

Detail Description Caused the fan stops and

over-temperature shutdown

Possible Causes Fan stop； FA is not in place

System Actions None

Impact on systemI. Board Status:

The board is faulty.

II. Service Impact: Board operation might be

abnormal.

Handling Suggestions Check FA

e.g 11: GPS clock reference source lost critical alarm Detail Description

When CC board is failed to detect the signal of external reference clock source, CC boards enters the state of free oscillation. When such state remains longer than critical alarm threshold, configured by an operator, this clock reference source critical alarm is reported.

Possible Causes The configured GPS clock

reference source doesn't exist. Single board error. Cable error.

System Actions None

Impact on systemI. Board Status:

Board operation is normal.

II. Service Impact: Situation 1: If reference clock is

lost, select an available reference clock source with the highest priority according to priority configuration, the system can still work normally.

Situation 2: If all reference clock sources are lost, the system will stay at remaining or free oscillation state.

Handling Suggestions1. Check if a GPS clock reference

source is configured.2. Check if the GPS clock reference is

correct.3. Single board fault.

(1) Reset the board.(2) Replace the board.

e.g 12: OMCB configuration does not work

Detail Description OMCB configuration does

not work

Possible Causes OMCB configuration illegal

System Actions None

Impact on system Fail to connect with OMCB

Handling Suggestions Check the OMCB

configuration Data in RNC and SDR parts.