TD-LTE eNodeB Troubleshooting

Course Objectives

 Know faults types of eNodeB

 Master handling methods of BBU typical faults
 Master handling methods of RRU telecom faults
 Master handling methods of site typical faults
Contents

eNodeB faults types

BBU common faults handling
RRU common faults handling
Site typical faults handling
BBU faults types
1
Transmission bearer subsystem kind fault

2
Operation and maintenance subsystem kind fault

3
Service and process fault

4
Baseband and CMAC fault

5
RRU kind fault
RRU faults types
1
External interface kind fault

2
Fault related with BBU link

3
Fault related with RRU output power

4
Fault related with RRU version download

5
Fault related with RRU hardware
Contents

BBU common faults handling

Transmission bearer subsystem kind fault
Operation and maintenance subsystem kind fault
Service and process fault
Baseband and CMAC fault
RRU kind fault
Association establish failure-1

Fault effect

 Appear major alarm of SCTP association on interface

 Use showtcb, debug command of examine association status,
show association status closed or cookie-wait.

Fault
Fault analysis
analysis and
and location
location

 Physics link fault, due to access method and lower layer link not
stable, can not receive and send packet normally.
 Transmission parameter configuration not correct, IP
parameters, static routing, SCTP parameters not map with peer
end, lead to can not establish association normally
 MAC address on ARP table not correct
Association establish failure-2
Fault
Fault handling
handling method
method

 First make sure physics link correctly connected, then check configuration of
transmission parameters include FE parameter, Gport parameter, IP parameter and
SCTP parameter.
 If not use VLAN, configure FE parameter and Gport parameter by default. IP
parameter means IP address and property configuration of eNB extra network port.
SCTP parameter source port, target port and peer end IP must map with
configuration of peer end. Configuration in different network sections, must configure
static routing parameter correctly.
 Use PrintfArp command to check id get correct MAC address.
IP address collision fault

Fault
Fault effect
effect

 Background network management report ‘IP address collision’ alarm.

Fault
Fault analysis
analysis and
and location
location

 When connect multi-eNB in core network, if not configure IP

addresses according to planned IP addresses, may result two
eNB have the same IP address. After start eNB, send free ARP
request to check if there is the same IP address, if yes, appear
IP collision effect.
Fault
Fault handling
handling method
method

 Modify IP address of base station to make sure base station IP

address unique.
 Examine transmission interface status-1
Fault
Fault effect
effect
 Transmission physical interface-transmission may optic and electricity. At present background can not check if now
working optical interface/electrical interface is normal. If use electrical interface, need to notice which work mode
negotiate successfully(10Mbps half duplex, 100Mbps full duplex and auto-sensing, 10Mbps full duplex, 100Mbps
half duplex, 1000Mbps)

Fault
Fault analysis
analysis and
and location
location

 In CC input command
to examine work mode
of current network port
 As following picture,
abis port abnormal
and debug port
normal.
Examine transmission interface status-2
Fault
Fault handling
handling method
method
 Need to check if physical connection of abis port is normal
 Need to check if work mode of abis port after negotiation is correcy
 If transmission interface is
If transmission interface is electrical
port, in the following picture electrical optical port, in the following
port work normally and work mode is picture optical port work normally
100 Mbps full duplex. and work mode is 1000 Mbps full
duplex.
Foreground and background can not establish link
Fault
Fault effect
effect
 OMC and base station interface display broken link

Fault
Fault analysis
analysis and
and location
location
 Examine configuration: if OMC access IP is consistent with base station IP, if base
station configure OMC-B parameter
 Examine physical link
 Examine triple handshake
Fault
Fault handling
handling method
method
 Use packet catcher to check, if background NM(network management) send active broken
link packet(Syn packet:0x02), if base station answerback(Syn-Ack:0x0a), if background
answerback(Ackpacket:0x08)
 Case one: if after NM send Syn packet all the time, base station not answer, base station side not
work normally.
 Case two: if background senf Syn packet(0x02) request, base station answer Syn-Ack(0x0a),
then background not send Ack(0x08) to respond, but resend Syn(0x02)packet
 Case three: if triple handshake of foreground and background can’t succeed, need to check if ask
base station side to resend Syn-Ack packet, if yes, BS work abnormally, if not, background work
abnormally.
Can’t get user plane next hop MAC address-1
Fault
Fault effect
effect
 After start eNB, once in a while appear user plane channel fail, uplink data of user plane can’t be
forwarded in QE. Examine uplink user link table of QE, find corresponding mac address is 0

 Examine ARP table of BRS, can’t find

arp table entry of corresponding user
plane core network interface board.
Can’t get user plane next hop MAC address-2
Fault
Fault analysis
analysis and
and location
location
 When configure static routing or IP port gateway, will add static routing
next lop or arp table entry of gateway address initiate arp request, arp
table entry is ARPF_WAITING
 Time-out initiate, initaite arp request repeatealy for ARP_MAXRETRY
times
 More than ARP_MAXRETRY times, will delete arp table entry
 By analysis can see after corresponding configuration, BRS initiate
ARP_MAXRETRY times and peer end not answer, result arp table
entry be deleted

Fault
Fault handling
handling method
method
 From core network side user plane network element ping IP
address of CC, at this time, there will be MAC address of user
plane next lop in ARP table, then reestablish service, QE can be
transmitted.
Contents

BBU common faults handling

Transmission bearer subsystem kind fault
Operation and maintenance subsystem kind fault
Service and process fault
Baseband and CMAC fault
RRU kind fault
Can ping base station, but can’t login LMT
Fault
Fault effect
effect
 In condition of PC network adapter speed is auto induct, can ping
base station, but can’t login LMT successfully

Fault
Fault analysis
analysis and
and location
location
 Caused by fire wall
 Not load FPGA cause speed negotiation between Debug port
and PC fail, usually appear after delete files on flash disk

Fault
Fault handling
handling method
method

 Attempt to solve by closing fire wall

 Set network adapter of PC connecting base station Debug port
100M full duplex
Remote LMT login appear FTP upload failure
Fault
Fault effect
effect
 Remote LMT login base station, appear FTP upload failure

Fault
Fault analysis
analysis and
and location
location
 Number 21 port of remote PC be occupied
 BBU appear failure

Fault
Fault handling
handling method
method
 Number 21 port of remote PC be occupied, during LMT login process, BBU need
to use database file in LMT attached ftp server. In this case, mitigation method as
following: open PC task manager to check if there has boot other ftp server
process, name such as ‘ftpserver’, if yes, close this process, then restart EOMS. If
can’t find other ftp server process in task manager, can reboot PC/
 BBU appear failure, can attempt login BBU using ftp command of cmd.
Can’t use signaling tracing
Fault
Fault effect
effect
 In independent installed client end, client can login server end, but can not boot
signaling tracing, after click login, display can’t login

Fault
Fault analysis
analysis and
and location
location
 Now signaling tracing is a independent software, need to communicate directly
with foreground. Once independent client end can’t find routing to foreground,
can’t not use signaling tracing

Fault
Fault handling
handling method
method
 In transmission configuration of ground resource management, click right key to
add OMC-B link, on popup interface, fill in IP address of OMC the same with
machine IP address contain client end.
Can’t use EMS client end remote module
Fault
Fault effect
effect
 Can’t use remote module of EMS client end, can’t use any remote function

Fault
Fault analysis
analysis and
and location
location
 Appear network connection abnormity between OMM and EMS
 OMM and EMS versions not matching

Fault
Fault handling
handling method
method
 If OMM and EMS network connection appear abnormity, first check if physical
connection is normal, then check if routing between EMS and OMM is normal, if
there is fire wall, need to close fire wall then connect
 If OMM and EMS versions not matching, in network element management, in
OMC node click right key to choose forcing upload, EMS may upload remote
client end to EMS service end through FTP in OMM.
Can’t connect Oracle database to NM software
Fault
Fault effect
effect
 NM program can’t connect to database normally

Fault
Fault analysis
analysis and
and location
location
 Database related service not boot normally and monitoring process configured
wrong

Fault
Fault handling
handling method
method
 Check if oracle.exe process is booted in task manager(Windowsxp system)
 Check if have booted oracle related service in system service
(OracleDBConsole***,OracleOraDb10g_home1TNSlistener,oracleService***etc
(***is database instance name)), make sure related service changed to boot
automatically.
 Use Sqlplus command to link database to check, command format as followed:
Sqlplus user name/code@database instance name, if can enter database means
link in normal. If can’t enter need to check monitoring process and service process
configuration is succeed.
Contents

BBU common faults handling

Transmission bearer subsystem kind fault
Operation and maintenance subsystem kind fault
Service and process fault
Baseband and CMAC fault
RRU kind fault
SCTP association disconnect
Fault
Fault effect
effect
 LMT alarm that SCTP association disconnect

Fault
Fault analysis
analysis and
and location
location
 Network cable break, cause network failure
 SCTP related parameter configuration not correct, lead to packet unreachable.

Fault
Fault handling
handling method
method
 Check if physical connection is normal, make sure physical layer communication
normal
 Check if IP parameter is correct, configure principle: 20.2.environment
number.environment number
 Check if static routing is set correctly, notice usually modify not effective, need to
newly add
 Check if SCTP parameter is set correctly, make sure remote end IP address and
port number correct
S1 establish fail
Fault
Fault effect
effect
 LMT adjacent network element MME display Disable.

Fault
Fault analysis
analysis and
and location
location
 Sctp association break
 Cell not exist
 In S1 setup request related parameter wrong

Fault
Fault handling
handling method
method
 Make sure SCTP association OK, make sure communication of
transport layer normal
 Check if RRU boot normally, if cell is ok
 Check if cell TA correctly configured, core network usually support TA
0~5.
X2 establish fail
Fault
Fault effect
effect
 X2 port always printout X2 establish request message

Fault
Fault analysis
analysis and
and location
location
 Physical layer fault, mainly mean fault caused by link failure
 If network cable of core network is connected to Eth0 port of base station
 SCTP parameter configured not correctly
 Not add adjacent network element
 Not close fire wall
Fault
Fault handling
handling method
method
 Check if physical connection is normal, if all indicators of network card are
normal, make sure physical layer connection normal
 Network cable of core network need connected to Eth0 port of base station
 If add adjacent network element
 Close fire wall
UE side and core network ping packet failure

Fault
Fault effect
effect
 UE side and core network ping packet failure

Fault
Fault analysis
analysis and
and location
location
 Physical fault, mainly mean association link of eNB and S1 port of core network
failure
 Parameter configure abnormal, mainly mean IP parameter, association
parameter, etc, related with S1 port association not configured correctly
 Subsystem abnormal, if each subsystem of eNB side can respond normally
UE side and core network ping packet failure

Fault
Fault handling
handling method
method
 By examining background board status detection diagram to check if board is in normal
status.
 Examine if physical connection is normal, if network cable of core network connected
toEth0 port of base station, if S1 port association indicator are normal in background.
 Examine parameter configuration of S1 association link
 Catch packet on PDN side, to see if can receive packet to locate base station or core
network problem. If PDN side not receive data packet, first check base station side user
interface. By DSP monitoring tool to examine user plane statistics variables, check if
user plane dmac data statistics is increased, then if data on rlc layer is increased, in
UBPM board shell by user plane operation command if pdcp data statistics and gtpu
data statistics is increased, by DSP monitoring tool check user plane statistics variables,
check statistics of SDU combination if increased, explain if there is data fragment and if
data fragment can make of full packet, then check Rnlu printout, check if rearranged
time-out machine is overtime, check if bottom layer lose packet.
Cell establish fault

Fault
Fault effect
effect
 Cell establish fail

Fault
Fault analysis
analysis and
and location
location
 Physical layer fault, board status abnormal, fault caused by RRU status abnormal
or optical port link failure
 Parameter configuration abnormal, mainly cell parameter configuration abnormal.
Cell establishment involve many parameters need to check according to alarm
information and feedback of subsystems.
Cell establish fault

Fault
Fault handling
handling method
method

 Examine if physical connection and board status are normal.

 Examine optical port link, by background alarm information, check if there is
optical port link alarm information
 Examine subsystem feedback and parameter configuration. By signaling tracing
check if cell establish query response feedback by each subsystem are
successfully answered. If yes, result in feedback message is 0, if not, result is
1and ErrorCode or Cause in message isn’t 0, through this result can find cause of
fault. Also can examine printout information in RNLC TraceMe by eNB side or
background alarm information, to make clear if module initialization abnormal
inside RNLC caused by wrong parameter configuration.
UE can’t downlink synchronize or select proper cell

Fault
Fault effect
effect
 After cell establishment, UE can’t synchronize or select proper cell

Fault
Fault analysis
analysis and
and location
location
 If frequency in UE side is correctly configured
 If UE can correctly demodulate synchronized PBCH
 If UE can correctly demodulate SIB, can’t select cell without SIB1 or SIB2
 If RSRP value measured by UE meet cell selection.

Fault
Fault handling
handling method
method
 Check if UE frequency is correct
 If can see SIB1 and S1, but cell status is without RSRP, show that RSRP value
can’t satisfy cell standard, can check if fading of wireless link too deep, if station
RRU work in normal, if can’t find any abnormal, can try to reset or change RF
subcard until problem solved.
UE accessed to target, X2 port switch still fail
Fault
Fault effect
effect
 X2 port switch, after target eNB receive PathSwitchRequestAcknowledge, release UE instance.

Fault
Fault analysis
analysis and
and location
location
 MME actively initiate UEContextReleaseComman lead to UE be released during
switch
 UE actively initiate Detach lead to be released
 PathSwitchRequestAcknowledge not delivered for this UE instance, means when
the UE instance wait for its own PathSwitchRequestAcknowledge and time out,
lead to UE be released.

Fault
Fault handling
handling method
method
 By signaling tracing, check if MME delivery UEContextReleaseCommand actively
 By signaling tracing, check if UE delivery Detach actively
 Examine if MMEUES1APID and eNBUES1APID in
PathSwitchRequestAcknowledge belong to the UE ID, if not, that means core
network not response PathSwitchRequest message of this UE.
X2 port switch trigger fail

Fault
Fault effect
effect
 When UE switch from one eNodeB cell to another eNodeB cell, not witch by X2
port but by S1 port

Fault
Fault analysis
analysis and
and location
location
 Connection not established between the X2 ports of eNodeB
 Mmes connect two eNodeB not belong to the same MME group

Fault
Fault handling
handling method
method
 Examine if X2 port connection between two eNodeB is in connected status
 Examine if two eNodeB connect MME belong to the same MME group
Measurement report trigger fail
Fault
Fault effect
effect
 RSRP D-value between two cells satisfy switch threshold, UE not report
measurement report

Fault
Fault analysis
analysis and
and location
location
 UE capacity can’t support related frequency
 UE capacity can’t support GAP(inter-frequency need, intra-frequency not need)
 Nset adjacent cell
 Not satisfy switch threshold after calculate filtering

Fault
Fault handling
handling method
method
 Examine if UE capacity support ralated measurement frequency
 Inter-frequency switch need to examine if UE capacity support GAP
measurement
 If configure other eNB cell parameter table, if E-UTRAN adjacent cell table. If
eNBld and cellId in the two tables are consistent
 By filtering formula to calculate if RSRP D-value of the two cells satisfy switch
threshold.
Contents

BBU common faults handling

Transmission bearer subsystem kind fault
Operation and maintenance subsystem kind fault
Service and process fault
Baseband and CMAC fault
RRU kind fault
UE initial access fail
Fault
Fault effect
effect
 From UE side LMT find Msg1,Msg2,Msg3 repeat nonstop, can’t access, or in
some step after Msg4 for example can’t capacity message can’t succeed lead to
access fail

Fault
Fault analysis
analysis and
and location
location
 UE not synchronize to directly connect cell, but synchronize to interferential cell
 Channel quality not good, deep fading
 UE side send power too small, lead to station CRC check wrong

Fault
Fault handling
handling method
method
 Examine if UE synchronized cell ID consistent with station cell ID, if not, reset UE
and synchronize to direct cell
 Examine if station side CRC or PUSCHCRC of Msg3 is OK, if many errors, check
if link attenuation is normal, if attenuation too large, decrease the attenuation and
then try to access
 Change station side path loss compensation factor to 1.0, then retry to access
 Reset UERF subcard and then try to access
UE configure CQI/PMI/RI, but UE not report

Fault
Fault effect
effect
 UE configure period CQI/PMI/RI report, but see from station side UE not send
CQI/PMI/RI, lead to when transfer mode TM3, because UE not report RI, station
not dispatch double current.

Fault
Fault analysis
analysis and
and location
location
 May cause by downlink service, ACK/NACK and CQI/PMI/RI transferred in the
same subframe. Caused by default support indicator of LMT PUCH parameter -
>the same subframe send ACK/NACK and CQI at the same time is false.

Fault
Fault handling
handling method
method
 Change the support indicator of LMT PUCH parameter ->the same subframe send
ACK/NACK and CQI and the same time true, if the cell establish access succeed,
problem solved.
UE side detect CRC of service all wrong

Fault
Fault effect
effect
 After Ue attach succeed, do downlink service CRC all wrong

Fault
Fault analysis
analysis and
and location
location
 PCFICH demodulate fail
 PDCCH demodulate fail
 eNB dispatch RB beyond UE handling capacity

Fault
Fault handling
handling method
method
 Make sure if CFI can resolve correctly. If can’t, may caused by downlink channel
condition, need to adjust downlink channel quality, if can, but PDCCH resolve all
wrong, first check downlink channel quality, then confirm if UE and CCE
aggregation degree of eNB consistent (UE not support blind check)or CCE
distribution fail (UE support blind check), last confirm if eNB dispatch RB beyond
UE handling capacity, if yes need to modify downlink RB until inside UE handling
capacity.
UE side detect CRC of service partial wrong

Fault
Fault effect
effect
 After Ue attach succeed, do downlink service CRC partial wrong

Fault
Fault analysis
analysis and
and location
location
 Not estimate BF weight value using uplink reference signal or SRS
 Antenna rectification not enabled

Fault
Fault handling
handling method
method
 Examine if initiate uplink service or SRS enable to do uplink channel estimation
or enable uplink/downlink antenna rectification
UE set RI=2, channel quality good, but station not
dispatch double current
Fault
Fault effect
effect
 UE set RI=2, and channel quality good, but station still dispatch single current mode.

Fault
Fault analysis
analysis and
and location
location
 UE may set R1=2, but maybe UE not report CQI/PMI/RI, station can’t sure about
downlink channel quality, so dispatch single current in conservative mode,
another reason maybe(same with 3.5.2)set period CQI/PMI/RI, but downlink has
service, ACK/NACK and CQI/PMI/RIQ transferred in the same subframe. Default
support indicator of LMT PUCH parameter ->the same subframe send
ACK/NACK and CQI at the same time is false

Fault
Fault handling
handling method
method
 In station LMT set period report CQI/PMI/RI
 Change the support indicator of LMT PUCH parameter ->the same subframe
send ACK/NACK and CQI and the same time true, if the cell establish access
succeed, problem solved.
Contents

BBU common faults handling

Transmission bearer subsystem kind fault
Operation and maintenance subsystem kind fault
Service and process fault
Baseband and CMAC fault
RRU kind fault
Can’t remote login RRU through BBU
Fault
Fault effect
effect
 Can’t remote login RRU through BBU

Fault
Fault analysis
analysis and
and location
location
 BBU not configure fiber RF resource relation
 Fiber module not inserted in configured optical port
 Send and receive fiber inserted reversely

Fault
Fault handling
handling method
method
 Check background if fiber RF resource configured, make sure have configured.
 Check if fiber module inserted in RF resource configured optical port, make
sure fiber module inserted optical port is configured optical port.
 Check if physical connection is normal, if corresponding optical port light on
baseband board flick in a rate of 1MHz, if corresponding light not flash insert
two fiber reversely, if constant flash mean RRU is booting.
Antenna port not output power
Fault
Fault effect
effect
 Cell normal, but antenna port not output power

Fault
Fault analysis
analysis and
and location
location
 Standing wave ratio too large lead to power amplifier close
 PA may not open
 DAC not open

Fault
Fault handling
handling method
method
 Check background if there is standing wave ratio alarm, if yes, check if feeder
cable connected normally, if not connected normally correct the connection
and open PA on background by reblock and unblock channel
 If there is no standing wave ratio alarm, remote login RRU by BBU, to check if
PA open, if not, open PA by command
 Remote login RRU by BBU, check if DAC is open, if not open DAC by
command.
Contents

RRU common faults handling

External interface kind fault
Fault related with BBU link
Fault related with RRU output power
Fault related with RRU version download
Fault related with RRU hardware
RRU can’t connect external debug port
Fault
Fault effect
effect
 Can’t ping network cable connected RRU external LMT port

Fault
Fault analysis
analysis and
and location
location

 Not connect with crossover cable

 Computer and RRU not in the same network section
 If connect multi- RRU by hub, because IP/MAC of RRU are the same, lead to
collision
 Check if the fire wall of computer is open, need to close fire wall

Fault
Fault handling
handling method
method
 Change to use crossover cable
 External port of RRU fixed to 199.33.33.33, set IP of computer as
199.33.XX.XX section, mask as 255.255.0.0
 Not to connect multi-RRU to s hub
 By changing Windows fire wall set to close it
RRU external RUN indicator flash abnormally
Fault
Fault effect
effect
 RRU external RUN indicator flash rate higher than 1Hz for a long time(if RRU start
normally, run indicator should flash in 1Hz rate)

Fault
Fault analysis
analysis and
and location
location
 RRU loading version under boot, flash rate under boot is 5 Hz
 Version boot process fail, and RRU softwrae can’t reboot
 RRU version stored in local flash may be broken, under boot load version not
succeed, reboot repeatedly
Fault
Fault handling
handling method
method
 If flash rate higher than 1Hz in a short time(shorter than 5 minutes), it’s normal,
it need time to boot RRU version
 Software version not correct RRU using, lead to boot fail. Need to check RRU
software specification packet. If some wrong with single RRU, connect with
R&D, save RRU boot log information
 If flash rate is 5Hz for a long time, maybe RRU local flash version broken, at
this time RRU version activated by BBU can’t respond and download, need to
change RRU.
RRU external alarm indicator constant light
Fault
Fault effect
effect

 RRU external alarm indicator constant light

Fault
Fault analysis
analysis and
and location
location
 RRU report alarm

Fault
Fault handling
handling method
method
 Check RRU now and history alarm information on network management OMC
or EOMS software
Contents

RRU common faults handling

External interface kind fault
Fault related with BBU link
Fault related with RRU output power
Fault related with RRU version download
Fault related with RRU hardware
RRU boot setup fail
Fault
Fault effect
effect
 After RRU start and run, LMT RF resource show RRU status as ‘fault+link break’

Fault
Fault analysis
analysis and
and location
location
 Fiber connected reversely
 Fiber module rate and fiber not match
 Fiber broken

Fault
Fault handling
handling method
method
 Exchange fiber
 Examine if fiber match with fiber module (single mode, multi-mode)
 Change fiber
RRU show board communication link broken
alarm

Fault
Fault effect
effect
 After RRU run normally, suddenly link break, background show ‘board software
status abnormal’, ‘board communication link broken’ alarm

Fault
Fault analysis
analysis and
and location
location
 Software reboot abnormally
 Fiber link with BBU abnormal, heartbeat loss more than 3 times reboot

Fault
Fault handling
handling method
method
 Examine if fiber link is broken.
Contents

RRU common faults handling

External interface kind fault
Fault related with BBU link
Fault related with RRU output power
Fault related with RRU version download
Fault related with RRU hardware
RRU display whole system calibration fail
alarm
Fault
Fault effect
effect

 After RRU boot and run, display ‘whole system calibration fail alarm’

Fault
Fault analysis
analysis and
and location
location
 Some wrong with RRU reflection link and feedback link gain
 RRU off-line parameter broken

Fault
Fault handling
handling method
method

 Use showofflinevalid to check broken off-line parameters

RRU display standing wave ratio alarm
Fault
Fault effect
effect
 RRU boot and run, display ‘standing wave ratio alarm’

Fault
Fault analysis
analysis and
and location
location
 RRU RF port load not connected correctly
 RRU internal RF component broken, if inside RRU PA, RF switch feedback
reflection can’t work normally, wrongly detect standing wave ratio or PA control
wire connect board and PA loss or bad.

Fault
Fault handling
handling method
method
 Examine if interface of RF port and antenna screwed tightly
 RRU send for repair
RRU display downlink output less/over power
alarm
Fault
Fault effect
effect
 After RRU boot and run, display ‘downlink output less/over power alarm’

Fault
Fault analysis
analysis and
and location
location

 Calibration fail, lead to output power over or less

 RRU internal RF component broken, something wrong with forward emission
gain or feedback detection link gain.

Fault
Fault handling
handling method
method
 Use showpwr command to check TCPW power, if too small, mean output less
power
 Use showpa command to check PA switch, if ‘downlink output lsee/over power
alarm’always exist and PA is closed, mean produce more power output, close
PA to protect. Can try to delete and establish cell, if abnormal always exist,
may RRU gain wrong, need sent to repair
RRUdisplay downlink power abnormal alarm

Fault
Fault effect
effect
 After RRU boot and run, display ‘downlink power abnormal alarm’ (1. downlink digital power over 2. downlink
digital power less)

Fault
Fault analysis
analysis and
and location
location

 Baseband version run abnormally

 Baseband transceiving data abnormally

Fault
Fault handling
handling method
method
 Check if baseband board exist abnormal alarm
Contents

RRU common faults handling

External interface kind fault
Fault related with BBU link
Fault related with RRU output power
Fault related with RRU version download
Fault related with RRU hardware
RRU display software download fail alarm

Fault
Fault effect
effect
 After RRU upgrade software, display ‘software download fail alarm’

Fault
Fault analysis
analysis and
and location
location
 RRU version packet background download and activate not correct
 RRU local enable new version abnormal

Fault
Fault handling
handling method
method

 Examine if RRU specification packet background activated is correct

RRUdisplay software download fail alarm
caused by too large file
Fault
Fault effect
effect
 After RRU upgrade software, display ‘file too large cause software download fail alarm’

Fault
Fault analysis
analysis and
and location
location
 RRU version packet background download and activate wrong, file too large
 RRU local flash remaining room not enough to restore newly download version

Fault
Fault handling
handling method
method
 Examine if RRU specification packet background activated is correct
 Examine remaining room of flash
Contents

RRU common faults handling

External interface kind fault
Fault related with BBU link
Fault related with RRU output power
Fault related with RRU version download
Fault related with RRU hardware
Display RRU input power monitoring alarm
Fault
Fault effect
effect
 Display ‘input power monitoring alarm’

Fault
Fault analysis
analysis and
and location
location
 RRU power supply voltage too high or too low
 RRU local enable new version not in normal

Fault
Fault handling
handling method
method

 Examine if power supply satisfy requirement:

 Direct current ：  Alternating current ：
 Input voltage alarm signal over power
 Input voltage alarm signal over
point: -57~-60V power point: 266~286V
 Recovery point ： -54~-60V
 Recovery point ： 256~286V
 Hystersis ：≥ 1.5V
 Hystersis ：≥ 5V
 Input less voltage alarm point ： -38~-41V
 Input less voltage alarm point
： 154~164V
 Recovery point ： -38~-43.2V
 Recovery point ： 154~176V
 Hystersis ：≥ 1.5V
 Hystersis ： ≥ 5V
RRU display power temperature abnormal
alarm
Fault
Fault effect
effect

 RRU diaplay ‘power temperature abnormal alarm’

Fault
Fault analysis
analysis and
and location
location
 RRU output power too large, RF efficiency not enough
 RRU heat dissipation condition not good

Fault
Fault handling
handling method
method

 Examine if external environment of RRU is over heat

 Examine heat dissipation and ventilation condition of RRU case, best to hang the
RRU vertically.
RRU display PA over heat alarm

Fault
Fault effect
effect
 RRU display ‘PA over heat alarm’

Fault
Fault analysis
analysis and
and location
location
 RRU output power too large, RF efficiency not enough
 RRU heat dissipation condition not good

Fault
Fault handling
handling method
method

 Examine if external environment of RRU is over heat

 Examine heat dissipation and ventilation condition of RRU case, best to hang the
RRU vertically.
RRU display board over heat alarm

Fault
Fault effect
effect
 RRU display ‘board over heat alarm’

Fault
Fault analysis
analysis and
and location
location
 RRU output power too large, RF efficiency not enough
 RRU heat dissipation condition not good

Fault
Fault handling
handling method
method

 Examine if external environment of RRU is over heat

 Examine heat dissipation and ventilation condition of RRU case, best to hang the
RRU vertically.
RRU display local oscillator lose lock alarm

Fault
Fault effect
effect
 RRU display ‘local oscillator lose lock alarm’

Fault
Fault analysis
analysis and
and location
location
 RRU RF local oscillator clock chip broken, lose lock
 There is external strong interference signal affect the performance of RRU local
oscillator chip

Fault
Fault handling
handling method
method

 Check if there is external interference signal

RRU display not detect PA alarm

Fault
Fault effect
effect
 RRU display ‘not detect PA alarm’

Fault
Fault analysis
analysis and
and location
location
 Bad connection with RRU PA and board connecting line
 Power supply of RRU PA not in normal, PA not be powered.

Fault
Fault handling
handling method
method

 Send RRU to repair

Contents

eNodeB faults types

BBU common faults handling
RRU common faults handling
Site typical faults handling
Not respond core network S1 switch request
Fault
Fault effect
effect
 Now the least value of core network delete back-propagation channel timer is 1s, so
between target side send HandOverNotify to respond next switch request can’t switch for
1s, if restart switch display switch prepare timer out-time

Fault
Fault analysis
analysis and
and location
location
 Wireless side and core network side have different understanding of time, actually it’s
very possible to switch again in 1s
 Network overlay distribution unreasonable
 This station not optimize wireless for frequent switch situation

Fault
Fault handling
handling method
method
 Try to modify delete back-propagation channel timer of core network(least value is 1s)
 Try to modify A3 event threshold, default value is 3dB, suggest change to 4dB
 Add switch prepare timer time, suggest change to 1100ms
 Modify report times and alternation of event trigger report
 Try to add time of TA timer, increase RLC most transfer times, modify N310 and N311
value according to field test condition
Cell establish fail
Fault
Fault effect
effect
 Check from OMC, cell quit service
 Board indicator abnormal
 UE can’t access

Fault
Fault analysis
analysis and
and location
location
 RRU or BPLnot run normally
 Wrong with fiber/fiber module
 Not configure association parameter

Fault
Fault handling
handling method
method
 Check if RRU or BPL has abnormal alarm
 Check if configure SCTP, IP, adjacent NE
 Check if connecting ling between RRU and BPL is usable, if interface lose
 Check if running version is correct
UE access not succeed
Fault
Fault effect
effect
 UE can’t access

Fault
Fault analysis
analysis and
and location
location
 Cell not established
 Cell resource not sufficient
 Power overload
 UE not allocated number
 User not have enough balance

Fault
Fault handling
handling method
method
 Check if cell is established successfully
 Check UE information on core network to see if the user can access
 Check if cell has power overload etc alarm message
 Make service observation of the UE on OMC to find which specific fail
 If admission fail, check if cell resource sufficient
 If timer over time, confirm if antenna coverage bad
S1/X2 switch fail
Fault
Fault effect
effect
 When user move or on some crossing, UE stream not stable

Fault
Fault analysis
analysis and
and location
location
 Antenna environment not good, exist interference, adjacent cell miss configured,
switch threshold set unreasonable

Fault
Fault handling
handling method
method

 Check service observation of switch on OMC to find if the UE exist switch fail
 If admission fail, check if cell resource or power sufficient
 If timer over time, confirm if switch threshold set reasonably
Terminal can’t find network

Fault
Fault effect
effect
 Terminal can’t find network

Fault
Fault analysis
analysis and
and location
location
 There are two concepts of UE downlink synchronization, one is downlink main
/assistant synchronization, the other need to consider if broadcast information is
resolved correctly on the basis.
 Downlink main /assistant synchronization depend on cell frequency, if succeed,
can get cell bandwidth and physical cell ID from UE side, if fail, maybe frequency
not set correctly
 In the situation can’t receive cell broadcast, can check MIB and SIB, MIB
information contains cell bandwidth and power parameter. If can’t resolve MIB,
maybe parameter in high lay information packet not correct
Terminal can’t find network

Fault
Fault handling
handling method
method

 Check if fiber insert correctly. Cell index must consistent with fiber port
number(fiber port number is 2,1,0 from left to right), notice fiber indicator on BPL
board, flash in each second mean fiber link normal
 Make sure if RRU RF work normally, work bandwidth and frequency set in
allowed dynamic range
 Check if control plane cell, FPGA cell is established successfully
 Change terminal
Serdes broken link more than 30s will trigger RRU
whole board reset, analyze and handle
Fault
Fault effect
effect
 RRU fpga would detect optical port frame frequency in a 10ms period, if in 30s detected frame frequency
continuously wrong, will set cpu tag, cpu will invoke call back function of high layer to reset whole board, after
low lay invoke interface, high lay will judge now board software enter working status and control to enable
whole board reset

Fault
Fault analysis
analysis and
and location
location
 First judge if exist reset in BBU side, in BBU reset condition may cause broken
link more than 30s
 If BBU side normal, detect if BPL FPGA run normally
 Check downlink fiber and fiber module, judge if fiber match with fiber module, if
all fibers normal
 Login BBU shell, check if exist ‘FN FR error! AD9549 will be open!’printout
information

Fault
Fault handling
handling method
method
 Change fiber