12 WiMAX_T09_E3_WiMAX Routine Maintenance and Troubleshooting-26

8/3/2019 12 WiMAX_T09_E3_WiMAX Routine Maintenance and Troubleshooting-26

1/26

WiMAX Routine Maintenance and

Troubleshooting


2/26

Contents

Routine Maintenance

Troubleshooting


3/26

Routine Maintenance


4/26

Daily and Weekly Maintenance Items

Data Backup and Restoration

Equipment Running Environment Inspection

Board Maintenance Alarm System Maintenance

Log Inspection


5/26

Monthly/Quarterly Maintenance Items

Cabinet Maintenance

Data Correctness Inspection

Spare Part Inspection


6/26

Half-yearly /Annual Maintenance Items

Equipment Cable Maintenance

Grounding and Lightning Inspection


7/26

Contents

Routine Maintenance

Troubleshooting


8/26

Fault Acquiring

Alarms

Service observation

Performance statistics User complaints


9/26

Fault Location Analysis

Intra network, Inter network

External equipment (power supply, transmission

and switch) System, single BS, some BSs fault, global faults,

system parameter

Software and hardware


10/26

Common Troubleshooting Methodologies

Exclusion Method

Trial Method

Analogy Method Reasoning Method


11/26

Common Maintenance Methods

Fault Symptom Analysis Observing Indicators

Alarm and Log Analysis

Service Analysis Test with Instruments and Meters

Replacement Method

Service test and Drive Test

Unplugging/Plugging Method


12/26

Typical Fault Analysis

Cause Analysis of Low FTP Download Rate Check AAA and confirm whether the maximum rate of user

profile configuration is adequate.

Check whether the segment subcarrier is configured according to5M\10M full subcarrier.

After the traffic flow has been established, check whether the

service type and the maximum rate accord with those of AAA. Check the UL/DL CINR and RSSI by using the NPT and confirm

whether interference exists there.

Check whether the switch connected in the middle link is limitedon the port rate.

Check whether the transmission link is limited. Check whether the Ethernet cables connected the server, switch

and BS are proper.

Check whether the Receiver Buffer and Sent Buffer of the FTPserver are limited.


13/26

Typical Faults in RRU (1)

Checking Approach to RRU Malfunction

RRU version information: CPU, FPGA, BOOT and

EPLD of the WPTP board as well as MCU and BOOT

of the WDPA board Alarm information: Alarm Description, Reason Code

Description and Append Information

Board diagnosis information: WPTR and WDPA

diagnosis information RF runtime data observation information


14/26


No RRU Detected

OMC Alarm: No WTRX detected and No WDPA detected; Cause Analysis :

The fiber between RRU and BBU is broken, damaged or of poor quality. The fiber and optical modules between RRU and BBU are in poor contact or

mismatched. The versions of RRU, BBU and OMC are mismatched. The fixed Tx and Rx connectors of fiber are installed respectively in an opposite

position. The RRU is not powered on. Internal malfunctions occur in the RRU.

Troubleshooting : Check the connection condition of fiber. Check and replace the fiber and optical modules between RRU and BBU. Update the RRU version on the NE to make the versions of RRU,BBU and OMC

matching. Observe whether the SD on the PHY board is constantly on. For the Rx and Tx connectors oppositely placed, exchange their locations at the

BBU. Check whether the -48 V power of RRU is normal and the -48 V power connector

is properly connected; Replace RRU.


15/26


No WDPA Detected

OMC Alarm: No WDPA detected;

Cause Analysis :

The WDPA version is mismatched.

The power connector of the WDPA module is in poor contact, causing thatthe WDPA is not powered on.

The control cable between the WDPA and WPTR modules is improperlyconnected, causing that the communication between them is abnormal.

Troubleshooting :

Check whether the WDPA version matches the WPTR version.

Reset the WDPA module on the OMC.

Open the RRU to check whether the power connector of the WDPA module

and the control-cable connector between the WDPA and WPTR modules areconnected well.

Not recommended. Its better

to be opened by ZTE


16/26

Typical Faults in RRU (4) No WDPA Detected

OMC Alarm: The PA is abnormal, and The PA Channel 0/1 VSWR isabnormal and The PA Channel 0/1 is closed.

Cause Analysis :

The antenna and feeder corresponding to the channels is not connected well.

The frequency range of DL signals exceeds that of the duplexers RFE.

Troubleshooting :

Use sitemaster to test the real VSWR of the antenna and feeder system andmake sure the VSWR less than 1.5.

Check whether the connectors of the antenna and feeder are screwed downand the shield layer near to the feeders connector is grounded well.

To adjust the frequency range of the DL signals to that of the duplexers RFE,

modify the center frequency of the DL signals on the OMC.


17/26

Typical Faults in RRU (5) WDPA-Disabled Alarm

OMC Alarm: The PA is abnormal, and The PA Channel 0/1 is closed

Cause Analysis : The VSWR alarm results in the WDPA-disabled alarm.

The broken link of the R6 interface on the BBU results in the WDPA-disabledalarm. The alarms of two channels simultaneously closed.

The abnormal GPS clock on the BBU also results in the WDPA disabledalarm. The alarms of two channels simultaneously closed are created.

The WDPA module is manually disabled

Troubleshooting : First view the append information to locate the detailed alarm cause.

For the WDPA-disabled alarm caused by the VSWR alarm, refer to thesolution of WDPA VSWR Alarm and Closed.

For the WDPA-disabled alarm caused by the broken link of the R6 interface,

perform the Ping command to check the link state from MPXM to AGW. TheWDPA is automatically enabled after the R6 interface recovers.

For the WDPA-disabled alarm caused by the abnormal GPS clock, checkwhether the TFM board and GPS receiver work normally.

For the WDPA disabled manually, enable the WDPA according to yourrequirement (In Alarm Management, set the WDPA to the Enable state).


18/26


WDPA Hardware Failure Alarm

OMC Alarm: The PA is abnormal, and The PA Channel 0/1 is with ahardware failure Cause Analysis :

The alarm may be caused by the poor contact of the control cable betweenWDPA and WPTR.

Troubleshooting : False alarms may persist in the old version; update the old version to

V.3.32.00P02 and then check whether the alarm genuinely occurs. Open the RRU to check the connection of the control cables connectors

between WDPA and WPTR. Or extract and insert the connectors. (NotRecommended)

Replace the RRU.


19/26

Typical Faults in RRU (7) RRU Auto-calibration Failure Alarm

OMC Alarm: RRU auto calibration failed, and Tx0/Tx1 auto calibration

failed Cause Analysis :

WDPA Disabled Forward Link Abnormal

Troubleshooting : For the auto calibration failure caused by the disabled WDPA, refer to the

solution of the WDPA-disabled alarm. Set the WDPA to the Enable state andthen manually originate the calibration flow.

For the auto calibration failure caused by the abnormal forward link, open theRRU to check the RF cable connection between the WPTRs RF output andthe WDPAs RF input.


20/26

Typical Faults in RRU (8) Low Reverse-link RSSI Alarm

OMC Alarm: Reverse link RSSI is low, and RX0/ RX1/ RX2/ RX3RSSI low

Cause Analysis :

For the alarm, it is recommended to observe the correspondingRSSI values in the RF Runtime Data Observation window.


21/26


Low RRU Forward-Power Alarm

OMC Alarm: RRU forward power is low, and Tx0/Tx1 power is

low

Cause Analysis :

The WDPA module is disabled.

The WDPA module is faulty in hardware.

The RRU auto-calibration fails.

The baseband power is low.

Troubleshooting :

Refer to the solution of WDPA-closed alarm, WDPA hardware

failure alarm and RRU auto-calibration failure alarm.

For the alarm caused by the low baseband power, first force to reset

the WBPM board. If the reset is invalid, replace the WBPM board.


22/26

Typical Faults in RRU (10) Inconsistent Configuration of RRU Board Type

OMC Alarm: The board type is inconsistent with that configured on OMC. Cause Analysis :

The PTR type configured on the OMC is inconsistent with that configured on the RRU.

Troubleshooting :


23/26

Typical Faults in RRU (11) Antenna Ability Checking Error

OMC Alarm: RRU antenna ability parameter checking error.

Cause Analysis : The antenna mode configured on the OMC is beyond the antenna ability actually

supported by the RRU.

Troubleshooting : In the Configuration Management window, modify the number of Rx/Tx antennas of the

segment to the antenna ability supported by the RRU.


24/26

Typical Faults in RRU (12) RRU Parameter Configuration Failed

OMC Alarm: RRU parameter configuration failed, and the configurationdata error

Cause Analysis : The configuration failure alarm results in the RRU power-on failure. Generally,

the RRU is reset after 6 to 7 minutes.

Modify the frequency rangeconfigured on the OMC intothe supported range.

The error is caused by themismatching RRU logicversion

The radio parameter errorresults in the read failure


25/26

Capture Guide of On-site Fault LocationInformation

Configuration Data NE Running Version Information

Alarm Information

OMC Log Board Diagnosis Information

Running Information Observation

Network Performance Test


26/26

12 WiMAX_T09_E3_WiMAX Routine Maintenance and Troubleshooting-26

Documents

Transcript of 12 WiMAX_T09_E3_WiMAX Routine Maintenance and Troubleshooting-26