Internal Only▲
ZXSDR NodeB Troubleshooting Applicable to Staff with with Skill Certificate Certificate Level II or Lower Released by GU Product Support Dept.
Internal Only▲
Version Introduction Version
Date
Author
Checked Checked by
R1.0
2011-03-24 2011-03-24
Zhao chenmu
***
References: 1. 2.
Amendment Record None
Internal Only▲
Course Objectives Objectives:: To understand the usage of trouble shooting tools To master the trouble shooting flow
Internal Only▲
Content Troubleshooting Tools Troubleshooting & solution flow Common Trouble examples
Internal Only▲
Troubleshooting Tools
EOMS (Embedded Operations and Maintenance Subsystem) Display Board Status Double-click the board on the NodeB rack layout; A dialog box will be displayed, displayed, listing detailed information including Board info, Board status, and alarm info. detail in online manual.
EFMS (Embedded Faults Maintenance Subsystem) Alarm Browse Browse window: displaying fault alarm information detail in online manual.
Internal Only▲
Content Troubleshooting Tools Troubleshooting & solution flow Common Trouble examples
Internal Only▲
Trouble Shooting and Solution Flow
Step 1 Find a fault alarm
Step 2 Information collection
Step 3 Information analysis
Step 4 Solution
Internal Only▲
Find a Alarm on EOMS
Internal Only▲
Find a Alarm on EFMS
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 simple and straightforward way .
Alarm Source Show where the alarm was invoked Alarm severity Four alarm levels indicated in descending order of severity is Critical , , Major , , M i n o r , and W a r n i n g .
Critical = must be handled at once Major = should be handled during working-hours. Minor = to be be handled at proper time so as to avoid serious fault. Warning = = necessary to be handled so as to avoid more serious fault.
Internal Only▲
Information Informatio n 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
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 t he AlarmSolutions document by indexing the alarm code.
Internal Only▲
Content Troubleshooting Tools Troubleshooting & solution flow Common Trouble examples
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
Internal Only▲
e.g 1: 23-Ethernet light and electricity lose Detail Description
System Actions
This alarm is given when FE port is configured, but network cable is not well connected with its peer end.
When this alarm occurs, the system will set the link via the network port to be fault.
Possible Causes Net cable failure
Handling Suggestions Check the net cable for any failure
The opposite net port is faulty.
Check the counterpart net port for any failure.
The local net port is faulty.
Check the local net port for any failure.
Impact on system Board operation is normal.The net port data transmission is interrupted, and the service is not available.
Internal Only▲
e.g 2: 14-Loss of Signal at Ir interface Detail Description
System Actions
Optical signal between BBU and RRU is lost, which will affect system normal running.
None.
Possible Causes
Handling Suggestions
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.
Impact on system 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.
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 failure in the fiber optics, the optical module. Check for the possible hardware failure with the lower level RRU.
Internal Only▲
e.g 3: 13-Board hardware fault Detail Description
System Actions
When the board hardware initialization is failed or it cannot c annot work normally due to hardware fault, this alarm is reported.
The board status is changed to be fault by the system.
Possible Causes Board hardware fault
Impact on system The board is faulty. The board fails to provide bearer service..
Handling Suggestions Reset the board. Replace the board.
Internal Only▲
e.g 4: 1009-Antenna over VSWR alarm Detail Description
System Actions
VSWR at antenna port is > 3.0
None
Possible Causes
Handling Suggestions
Antenna feeder is faulty.
Check antenna feeder.
Board is faulty.
Check the VSWR of antenna feeder by level.
Impact on system Board operation is normal. There is no transmission t ransmission power output for the RF channel. Service interruption occurs.
Check RRU.
Internal Only▲
e.g 5: 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 f ree 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.
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.
System Actions None
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.
Internal Only▲
Chapter/Course Chapter/Cours e Review
What tools can you use for trouble shooting？
What is the trouble shooting flow ？
Internal Only▲
