8.WR_SM07_E1_1 ZXSDR Node B Troubleshooting-44

8/10/2019 8.WR_SM07_E1_1 ZXSDR Node B Troubleshooting-44

1/44

ZXSDR Node B Troubleshooting

Guide

ZTE University


2/44


3/44

Fault Classification and Troubleshooting

Method

Fault classification Common troubleshooting method


4/44

Fault Classification

Service fault Transmission fault

Management and maintenance fault

Hardware fault


5/44

Common Troubleshooting Method

In the order of hardware, configurations, andprotocol.

Hardware running normally

Configurations and software version correct

Service flow. According to the protocol stack structureof the interface, from bottom layer to high layer.

From easy to difficult


6/44

Service Fault

Faults related to R99 service DPA and UPA service faults


7/44

Faults Related to R99 Service- Cell Setup

Fails

[Fault Phenomena] NBAP message displays that the cell setup fails.

[Troubleshooting]

Check the current alarms and history alarms. If there

are alarms about RRU/FS/BPC board fault, reset,

reboot, or change the faulty board, and then the fault

may disappear.

Check whether the cell configurations are consistent onthe RNC and Node B, especially CELLID, LOCALCELL-

ID, CELL-POWER, and BAND.


8/44

Faults Related to R99 Service- RNC Initiates

Cell Deletion

[Fault Phenomena] The RNC initiates the cell deletion.

[Troubleshooting]

Check the current alarms and history alarms. If there are alarmsabout RRU/FS/BPC board fault, reset, reboot, or change the faulty

board, and then the fault may disappear.

If there is transmission alarm, check whether the transmission

connections are reliable, the resistance is matching, and the

transmission bearer network quality meets the requirements. If the check results show that the Node B configurations are normal,

check RNC configurations.


9/44

Faults Related to R99 Service- CCH is Set up

and Deleted Repeatedly

[Fault Phenomena] After the Common Transport Channel (CCH) is set up, it

is deleted soon. And then, the CCH is setup again.

Such case repeats continuously.


10/44

Faults Related to R99 Service- CCH is Set up

and Deleted Repeatedly

[Troubleshooting] Check whether the transmission parameter

configurations are consistent on the RNC and Node B. ATM transmission parameters:

ATM addresses are consistent on the RNC and Node B.

AAL2 state is normal.

PVC path bandwidth and path group bandwidth are limited.

IP transmission parameters:

Service IP address is configured correctly.

IP path bandwidth and path group bandwidth are limited.


11/44

Faults Related to R99 Service- UE Can Not

Register Normally

[Fault Phenomena] The UE can not receive signals and can not register

normally.

[Troubleshooting]

Check whether the network mode of the UE is WCDMA.

Check whether the USIM is distributed

Check whether LAC and RAC configurations are correct.

Check whether the power configurations of all CCH are

normal.

Check whether RF connection in the cell of Node B is

normal and is consistent with actual connection.


12/44


Perform Service Normally

[Fault Phenomena] The UE can receive nice signals but can not perform

services normally.


13/44


Perform Service Normally

[Troubleshooting] Enable PMS and check whether the cell digital/analog

transmission power and the UL RSSI is normal, and

whether there are strong interferences from the outside.

Check whether RACH package is increased normally Check whether the pilot detection threshold is normal.

Check whether the ratio of RACH data package and

FACH data package is normal

Check whether the parameter settings related to FACHare correct

Check whether the cell radius settings are reasonable


14/44

DPA Service Faults- HSDPA Download Rate

is too Low or Drops Suddenly

[Fault Phenomena] When HSDPA service is being downloaded, the rate is

too low.

[Troubleshooting] Check whether the prescription of the (U) SIM card is

correct

Check the HSDPA cell configurations


15/44

DPA Service Faults- HSDPA Download Rate

is too Low or Drops Suddenly

Check whether there are too many HSDPA users in the

cell

Check whether the CQI reported is too low

Check whether the re-transmission proportion is normal Check the times of cells scheduling

Try sending some data packages from RNC to check

whether the rate can reach the ideal rate


16/44

UPA Service Faults- HSUPA Upload Rate is

too Low or Drops Suddenly

[Fault Phenomena] When HSUPA service is being uploaded, the rate is too

low.

[Troubleshooting] Make sure that HSDPA serving is working normally

Check in the cell measurement, the difference between

first receiving bandwidth and second receiving

bandwidth should be about 3 db

Check the value of SIR in UE measurement


17/44

UPA Service Faults- HSUPA Upload Rate is

too Low or Drops Suddenly

Check whether the cell is overloaded Check whether the value of UPH, HLBS, and TEBS in

UPA UE measurement is correct

Check whether the values of HarqFail, First

transmission error bit rate, Second transmission errorbit rate, and Third transmission error bit rate in UPA UE

measurement are too large

In QXDM, check whether the authorization is fluctuated,

whether UEs BLER is too large, whether there are too

many DTX, and whether the power of DPCCH is high


18/44

Transmission Fault

Ethernet transmission faults E1/T1 transmission related faults

OMCB failed to access NodeB


19/44

Ethernet Transmission Fault- SCTP Link

Abnormality

[Fault Phenomena] The alarm that SCTP is abnormal occurs

[Troubleshooting]

Check whether the hardware connections are normal

Check whether parameter configurations are correct

Check whether SCTP link is set up successfully


20/44

E1/T1 Transmission Faults- E1/T1 LOS Alarm

[Fault Phenomena] The electric signal is lost. The receiving end can not

detect the line pulse or logic 1 during a period, so the

RNC reports LOS (Loss Of Signal) alarm. Usually, the

signals on the peer line can not be detected becauseRx end of the E1/T1 physical line is faulty.

[Troubleshooting]

Check the physical state of E1 line: Check whether SA board is inserted stably.

Check whether E1 connector is loose.


21/44

E1/T1 Transmission Faults- E1/T1 LOS Alarm

Check whether the connector pins are intact, withoutslant pins and broken pins.

Check whether the external connector of the E1 line is

damaged and whether it is good contact with the peer

end.

Check whether the layout of E1 transmission cable

complies with the engineering specifications and

whether there is force from the outside.

Use the E1 self-loop line to loop the faulty line. If the

alarm resumes, check the E1 line on the peer end.


22/44

E1/T1 Transmission Faults- E1/T1 Remote

Alarm Indication

[Fault Phenomena] RAI (Remote Alarm Indication) is detected by the local

end.

[Troubleshooting]:

If Tx end sends the line fault alarm or the link isdisconnected, check whether Tx line connection is

normal (refer to E1/T1 LOS alarm).

Check whether E1 frame structure matches. Check

whether both ends of the line are working in the samemode, dual-frame mode or multi-frame mode.

Check whether there are a great number of error codes

on the Tx line.


23/44

E1/T1 Transmission Faults- E1/T1 LIF Alarm

of Near-End Receiving Link

[Fault Phenomena] On the NM, the IMA link state is available on the near

end and unavailable on the far end.

Sscop signaling link connection disconnected (514)

E1/t1 Ima group is in non-working state (508)

[Troubleshooting]

Loop IMA link from the BTS optical terminal to the RNC

check whether the E1 TS is normal

Loop from the optical terminal to the BTS

Perform the loop test on the SDTA board


24/44

OMCB Failed to Access Node B

[Fault Phenomena] When the OMCB accesses the Node B, it prompts the

failure or timeout.

[Troubleshooting]

Check whether the route from the PC to the RNC isadded correctly.

Check whether FTP server configuration is correct.

Check whether the route is added on the PC and OMM.

Check whether the Node B is enabled normally.

Check the firewall settings and see whether OMCB

connection is blocked.


25/44

Management and Maintenance Fault

Version load abnormality


26/44

Version Load Abnormality- Specification

Package Download Failure

[Fault Phenomena] The specification package download fails

[Troubleshooting]

Log onto the CC board through the telnet and carry out

the dosFsShow /ROOT/ command to view the

remaining space of the FLASH disk, delete some files of

the previous specification package.

Carry out the cd /ROOT/sw1 or cd /ROOT/sw2command to switch to the destination directory. Carry

out the ll command to display the version file in the

directorydelete *.swv files under both directories


27/44

Version Load Abnormality- Specification

Package Activation Fails

[Fault Phenomena] The specification package fails in activation and the

system prompts that there is data/software being

synchronized.

[Troubleshooting]

Wait until the standby CC board completes the software

synchronization. Check the current state of the standby

CC through the OMCB. If the state does not contain thesynchronous state, it indicates that the standby board

has completed the synchronization and the specification

package can be activated now.


28/44

Hardware Fault

Temperature related faults Clock reference related faults

Lightening protection box alarms

RRU abnormality


29/44

Lightning Arrester Fault

[Fault Phenomena] Alarm on the LMT interface: Lightning Arrester Alarm At

Indoor Lightning Protection Box (1536)

[Troubleshooting]

Check the configuration of the alarm input dry contactin OMCB

Check whether there is an alarm on the indoor

lightening protection box

Check the connection cable that connects the externalalarm device on the equipment

Check the connection cable on the SA

Check whether the SA board is loose in the plug


30/44

Environmental Temperature is High

[Fault Phenomena] Alarm on the EOMS interface: Environmental

Temperature is High (1500)

[Troubleshooting] check whether the dustproof net is blocked

Check whether the equipment is BS8900

Check whether the air conditioner is normal in the

equipment room


31/44

Environmental Temperature is High

Choose EOMS maintenance navigator Ground

resourcesEnvironment monitor, set the value of

Upper limit as 50

Choose DMS Maintenance navigator

Diagnosis andTestEnvironment monitor information query, if the

value of Control layer inlet temperature is larger than

50, replace the FA (Fan Amplifier).


32/44

LOS Alarm on Ir Optical Port

[Fault Phenomena] On the OMCB interface, there is the alarm:

On the LMT interface, there is the alarm: Ir optical port

has LOS alarm (Ir optical port ID: 2).


33/44


34/44

LOS Alarm on Ir Optical Port

Make sure that the optical fiber on the RRU isconnected to the Optical port 1, not Optical port 2,

Make sure that the optical fiber is in good contact with

optical module on the RRU

Replace the standby fiber on the faulty RRU Replace the optical module of the RRU


35/44

Clock Critical Alarm

[Fault Phenomena] On the LMT interface, there is the alarm: Clock critical alarm

(AD9516 unlocked) and FS is performing soft reset repeatedly.

[Troubleshooting]

On the OMCB, check if , there is serdes clock alarm on the CC

board

Unplug and plug the CC board

Replace the CC board.

Unplug and plug the FS board

Replace the FS board Insert the previous FS board into a normal shelf


36/44

Clock Reference Source Faults- BITS 2MBps

clock is degraded

[Fault Phenomena]

Cl k R f S F l BITS 2MB


37/44

Clock Reference Source Faults- BITS 2MBps

clock is degraded

[Troubleshooting] Check whether the interface connecting the E1 cable is

in good contact. If not, tighten the cable.

Check and replace the E1 cable.

Replace the SA and check whether the pins on thebackplane slot of the SA is bending or broken.

Check whether the external reference clock is normal.

Replace the CC board with alarm.

Cl k R f S F lt I t l GPS


38/44

Clock Reference Source Faults- Internal GPS

clock reference is lost

[Fault Phenomena]

Cl k R f S F lt I t l GPS


39/44

Clock Reference Source Faults- Internal GPS

clock reference is lost

[Troubleshooting] Check whether the CC board supports the GPS.

Check whether the GPS lightening arrester or GPS

antenna is damaged.

Check whether the GPS feeder is connected nicely. Check whether the clock reference source is configured

correctly.

Check and replace the GPS lightening arrester or GPS

antenna, especially check whether the GPS groundingcomplies with the engineering specifications.

Check and replace the GPS feeder.


40/44

Indoor Lightning Protection Box Alarm

[Fault Phenomena]

On the LMT interface, there is the alarm: Circuit Breaker Alarm At

Indoor Lightning Protection Box(1537).

[Troubleshooting]

Check the configuration of the alarm input dry contact through the

OMCB, Check whether there is alarm on the circuit breaker of the indoor

lightening protection box

Check the cable connecting the lightening protection box

Check the SA output cable

Check whether the SA board is loose in the slot


41/44

Outdoor Lightning Protection Box Alarm

[Fault Phenomena] On the LMT interface, there is the alarm: Outdoor

Lightning Protection Box Alarm(1538)

[Troubleshooting]

Check the configuration of the alarm input dry contactcorresponding to the indoor lightening protection boxthrough the OMCB

Check the dry contact connector

Check whether there is an alarm on the indoor

lightening protection box Check the cable with alarm

Check the RRU dry contact interface


42/44

RRU Abnormal

[Fault Phenomena] The RRU can not be started or any of the following

alarm occurs:

Optical signal loss on the Ir optical port

RRU LOS/LOF alarm Bottom-layer check error code on the Ir optical port


43/44

RRU Abnormal

[Troubleshooting] Check whether the optical fiber and optical module are

intact and whether the connection of them is correct.

Check whether the optical module is 1.25 G as

prescribed

Check whether the FS board is normal

Check whether the topo structure is configured correctly


44/44

Documents

8.WR_SM07_E1_1 ZXSDR Node B Troubleshooting-44