14.eNodeB LTE V100R011C10 Troubleshooting PDF

eNodeB LTE
V100R011C10
Troubleshooting
www.huawei.com
Copyright © 2016 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Describe the fault types and influences
 Grasp eNodeB troubleshooting methods
 Perform the eNodeB troubleshooting
Copyright © 2016 Huawei Technologies Co., Ltd. All rights reserved. Page1
Contents
1. Troubleshooting Overview
2. Troubleshooting Cell Unavailable Faults
3. Troubleshooting IP Transmission Faults
4. Troubleshooting Application Layer Faults
5. Troubleshooting Synchronization Faults
6. Troubleshooting Transmission Security Faults
7. Troubleshooting RF Unit Faults
8. Troubleshooting License Faults
General Troubleshooting Process
Start
Back up data.
Collecting fault information
Can the fault scope No

and type be determined?
Yes
Determining the fault scope and type
Identify fault causes
Contacting Huawei for

Rectify the fault Technical Support
No
Is the fault rectified?
Yes
End
Fault Information Collection
Information Item Collection Method
Fault symptom, as well as the time, location Consult the person reporting the fault, e.g,
and frequency of the occurrence customer service center
Equipment running status, fault symptom,
operations performed before the fault occurs,
Consult maintenance personnel
and measures taken after the fault occurs and
the effect of these measures.
Software/hardware running state of the Observe the board indicators, the O&M
equipment system, and the alarm management system
Perform service demonstration, performance
Scope and impact of the fault
measurement, and interface/signaling tracing
Copyright © 2016 Huawei Technologies Co., Ltd. All rights reserved. Page 4
LTE Fault Scope and Type
 In this course, troubleshooting of equipment faults is discussed.
Access faults
Handover faults
Service faults Service drop faults
Inter-RAT interoperability faults
Rate faults
eNodeB faults
Cell faults
OMCH faults
Clock faults
Equipment faults
Security faults
Radio frequency faults
License faults
Copyright © 2016 Huawei Technologies Co., Ltd. All rights reserved. Page 5
Common Maintenance Function
 Common maintenance functions that are used to analyze
and handle faults are as follows:
 User tracing
 Interface tracing
 Comparison/Interchange
 Switchover/Reset
Contact Huawei for Technical Support
 For the problems difficult to be located or solved
 Huawei Contact Information

 If you are in mainland China, dial 4008302118.
 If you are outside mainland China, contact the technical support

personnel in the local Huawei office.
 E-mail: support@huawei.com
 Website: http://support.huawei.com
Contents
Cell Unavailable Faults
 Affected Factors
Transmission Hardware Configuration RF
ALM-29240 Cell Unavailable alarm is reported.
 Possible Causes
 Incorrect data configuration
 Abnormal transport resources
 Abnormal RF resources
 Limited capacity or capability
 Faulty hardware
Incorrect Data Configuration
 Background information
 A cell cannot be set up successfully if the cell parameter settings do
not match the actual RF/baseband processing capability or other
parameters.
 Incorrect data configuration usually leads to a failure in the setup of a

cell, not in the running of a cell.
 Common incorrect data configuration causes

 Incorrect cell power configuration
 Incorrect cell bandwidth configuration
 Incorrect cell network-related configuration
 Incorrect cell power configuration
RRU3628 specification:
Cell1 & cell 2

Configuration:
Each antenna port
Cell band: 20M
output power is 60W
RS power: 17 dbm
Pb: 1
 Incorrect cell bandwidth configuration
Cell configuration: Band 2

EARFCN: 1199
RRU3628 specification:
BAND 1
Downlink:2110MHZ---2170MHZ
 Incorrect cell network-related configuration
RRU hardware installation:

Chain Topology
RRU data configuration:

Star Topology
Abnormal Transport Resources
 Fault Description
 If the cell unavailability is caused by abnormal transport resources, a message
will be displayed after execution of the ACT CELL or DSP CELL command.
The message is displayed as Abnormal S1 link state for a cell.
 Possible causes
S1 interface or
SCTP link is broken
Case for Abnormal Transport Resources
 A cell failed to be activated. In the command output, the value of
Reason For Latest State Change was:
CCEM_CELLBASIC_ERR_CELL_SETUP_FAIL_S1LINK_DOWN~19
73485632.
 Fault Diagnosis
What we observed: Possible Cause:
 Cell failed to be activated  SCTP link is abnormal. DSP SCTPLNK
because of S1 link down.  S1 Interface is abnormal. DSP S1INTERFACE
 There is no related alarms.  There is no configuration
of S1 interface.
Abnormal RF Resources
RRU status is abnormal
2 RRU networking is un-consistent
1
CPRI links is abnormal
CPRI port line rate not negotiated
Case for Abnormal RF Resources
 After a cell activation command was executed, the following output is
displayed.
 Fault Diagnose
 Check RF-channel-related alarms (including VSWR alarms and RF
unit maintenance link alarms) and found there were RF unit
maintenance link alarms. OM personnel then determined that fiber
connections were incorrect according to alarm help information.
Limited Capacity or Capability
 A cell fails to be set up if the required capacity or capability is limited
on software or hardware.
 Possible Causes
 the licensed capacity or capability is limited
Case for Limited Capacity or
Capability
 The output after executing the command of DSP CELL,
Case for Limited Capacity or
Capability (Cont.)
 Fault diagnose
What we observed: Possible Cause:

 Cell failed to be  License file is abnormal.
activated because of  There is no license DSP LICINFO

abnormal license. installed in eNodeB. Compare
 Cell configuration exceed
the license capacity. LST CELL
Faulty Hardware
 Board fault alarms are reported. Alternatively, cell unavailability faults
cannot be rectified after resetting, powering off, or reinstalling faulty
boards.
 Possible Causes
 a fault occurs in the main control board, LBBP, RF unit, or other
hardware (for example, a subrack).
Hardware Fault Handling Procedure
START
Collect the fault info

through alarm browser
and MML command
Observe the panel

indicators
Useful commands:
DSP BRD Determine the fault
DSP RRU type and area
DSP BRDVER
DSP VSWR
DSP CPRIPORT Handle the fault by alarm
handling suggestion
Fault cleared? No Contact Huawei
Yes
END
Observe Panel Indicators
Contents
IP Transmission Faults
SCTP faults:
S1AP ALM-25888 SCTP Link Fault
SCTP IP Layer faults:
IP ALM-25885 IP Address Conflict
Link Layer Physical Layer faults:
ETH ALM-25880 Ethernet Link Fault
Control Plane
FE/GE
NB MME
core layer PTN
Convergence
User Plane layer PTN
FE/GE
UDP IPPath faults: SGW
ALM-25886 IP Path Fault
GTP-U
eNB
IP
Link Layer The same with control plane
ETH
Transmission Fault Location Ideas
 Fault Location Ideas
 Segmentation fault location idea
 Hierarchical fault location idea
 In the actual network failure troubleshooting, firstly try

segment method to determine the point of failure, and then
troubleshoot by layering or other methods
 Idea 1: Segmentation: Ping/Traceroute
 Segmentation method is the most important fault isolation means in
transmission problem troubleshooting.
Router
Access network IP/MPLS

aggregation Router
EPC/U2000
LanSwitch Router/S
ec-GW
Ping successful Ping successful
Ping failure
 PING: Packet Internet Groper
 It is used to check the TCP/IP network connection and device
reachability.
 The source device sends ICMP request packet to the destination

device, then waits for the ICMP echo packets.
B reachability? A B I am here.
MAC
MAC Header IP Header ICMP Packets
End of Frame
IP:10.0.0.1/24 IP:10.0.0.2/24
ICMP Echo Request
ICMP Echo Reply
 Traceroute:
 For test packets from the host to the destination passing
gateway
ICMP Echo Request(TTL=1)
A RTA
ICMP Echo Reply(Timeout)
IP:10.0.0.1/24
ICMP Echo Request(TTL=2)
IP:10.0.0.2/24
ICMP Echo Reply(Timeout)
Ethernet
RTB
B IP:10.1.1.1/24
 Idea 2: Hierarchical
IP address, Mask, Routing table

Lower layer faults
will lead to higher Port status, ARP configuration, VLAN
layer faults
Cables, connectors, signal levels,

coding, clock and framing.
Background Information
 ARP--Address Resolution Protocol
②
MAC address of 10.0.0.2
: 00-E0-FD-00-00-12
HostA HostB
IP:10.0.0.1/24 ARP Reply IP:10.0.0.2/24
MAC:00-E0-FD-00-00-11 MAC:00-E0-FD-00-00-12
①
Need MAC ARP Request?
address of broadcast
10.0.0.2?
unicast
 VLAN
VLAN1 VLAN2
VLAN3 VLAN4
 VLAN has the following advantages:

 Suppresses broadcast storm
 Improves transmission security
 Provides differentiated services
 Routing Table
IP header Data
GE0/0/1
GE0/0/0
192.168.10.0/24 172.16.1.0/24
IP Routing Table :
Network Pro Out Intf. Next hop
192.168.10.0/24 Direct GE0/0/0 192.168.10.254
192.168.12.0/24 Direct GE0/0/1 192.168.12.1
192.168.13.0/24 Direct GE0/0/2 192.168.13.1
172.16.1.0/24 Static GE0/0/1 192.168.12.2
Troubleshooting IP Physical Layer
Faults
 Step 1. Monitor the Ethernet port indicator status.
LED Color Status Description

The negotiation succeeds between the
ON
Ethernet port and the peer port
Green (LINK)
Etherne The negotiation fails between the Ethernet
OFF
t port port and the peer port
Orange/ Blinks fast The port is receiving or transmitting data.
Yellow (ACT) OFF The port does not receive or transmit data.
 If the green indicator on either the local eNodeB or the peer switch is off,
go to the next step.
Faults (Cont.)
 Step 2. Check configurations.
 Run the LST ETHPORT and
DSP ETHPORT commands to
check the Ethernet port
configuration, especially the
Port Attribute, Speed, and
Duplex.
Negotiate with peer

device, SET
ETHPORT to modify.
Faults (Cont.)
 Step 3. Isolate the fault.
 Take the right figure as an example of the
ports used in eNodeB are switch.
Step 3.1 test switch port Step 3.2 test eNodeB port functionality
functionality
Faults (Cont.)
 Step 3.3. Identify and isolate the fault.
 If the ETH port is faulty, try to reset the ETH port and the corresponding board
by MML commands of RST ETHPORT and RST BRD
 Use RST ETHPORT to
reset an Ethernet port
and restart automatic
port negotiation
 The reset of a board causes interruption of services

carried by the board.
 The reset of the
active main control
board causes reset
of the eNodeB
Rest by GUI in U2000 Rest by MML
Troubleshooting IP Link Layer Faults
 Step 1. Check packet transmitting and receiving on the eNodeB.
 Run the DSP ETHPORT command
multiple times.
Repeat the query,

observe the RX and
TX statistics on the
eNodeB port.
 If only the number of packets

transmitted by the eNodeB
increases, the peer device does not
respond. Check whether the
eNodeB has transmitted incorrect
packets or the packets are correct
but the peer device is faulty.
(Cont.)
 Step 2. Query the ARP table. Check whether the eNodeB has learned the
ARP.
 Run the DSP ARP command on the eNodeB. Check whether the ARP entry is
available.
 If the peer ARP entry is available on the eNodeB, you can infer that the fault is not
caused by the ARP entry.
(Cont.)
 Step 2 (Cont.)
 If the eNodeB has not learned the ARP, perform a ping test and check again
 If the eNodeB still has not learned the ARP, run the STR PORTREDIRECT
command to start port redirection to trace the packet header.
(Cont.)
 Step 3. Check the VLAN configuration.
 Run the LST VLANMAP and LST VLANCLASS commands to check whether
the VLAN configuration is correct.
 Run the STR

PORTREDIREC
T on the
 to start port mirroring to trace the packet header. Compare the VLAN configuration
eNodeB
with the VLAN information in the packet. If the VLAN information in the packet is
incorrect, modify the VLAN configuration and check again.
Troubleshooting IP Layer Faults
 Step 1. Query the configured routes.
 Run the LST IPRT and DSP IPRT commands to check whether routes are
correctly configured on the eNodeB.
Troubleshooting IP Layer Faults
(Cont.)
 Step 2. Use the traceroute function to locate the fault.
 Run the TRACERT command on the eNodeB to query the nodes that the
transmitted packets pass and determine the gateway where the route becomes
unavailable.
Contents
Troubleshooting Application Layer
Faults
 Definition
 Application layer faults include unavailability and intermittent
disconnection of SCTP links, IP paths, and OM channels.
SCTP link
MME
IP path
S-GW
Switch Router Router
OM channel
eNB IP- U2000

CLKServer
Troubleshooting SCTP Link Faults
 Either of the following alarms is reported:
 ALM-25888 SCTP Link Fault

 ALM-25889 SCTP Link Congestion
 The SCTP link is abnormal or available only in one direction.
 Possible Causes
SCTP configuration is faulty.
2 2 NE status is
3 abnormal.
1
The transmission is faulty.

Troubleshooting SCTP Link Faults in
Typical Scenario
 Step 1. Check
configurations(Link mode ).
 Check whether SCTP
parameters are correctly
configured on the MME and the
eNodeB.
 On eNodeB side, SCTP link

configuration information can
queried by LST SCTPLNK.
the parameters in red rectangles
are eNodeB parameters and the
parameters in the blue
rectangles are EPC parameters.
Typical Scenario
 Step 1. Check configurations(EP mode ).
Typical Scenario (Cont.)
 Step 2. Check the transmission.
 Ping the MME IP address. If the MME IP address cannot be pinged, check the
route and transmission network, following what described in chapter 3.
How to get the

SCTP destination
IP?
Typical Scenario (Cont.)
 Step 3. Start SCTP message tracing.
 Start SCTP message tracing and compare the tracing result with normal SCTP
message exchange.
Troubleshooting of Intermittent SCTP Link
Disconnection
 Step 1. Check transmission alarms.
 Step 2. Check the QoS of signaling data.

 If VLANs are configured for the eNodeB, check whether the VLAN for signaling data
is correctly configured on the eNodeB.
 If no VLAN is configured for the eNodeB, check whether the DSCP value for
signaling data is the same as that for the transmission network.
 Run the LST DIFPRI command to query the DSCP value for signaling data.
Check whether the DSCP value

is larger than 46 in the QoS
configuration for the
transmission network.
Troubleshooting of Intermittent SCTP Link
Disconnection (Cont.)
 Step 3. Start SCTP message tracing.
 Start SCTP message tracing and analyze the messages to find the cause for
the link failure.
 Step 4. Check the network packet loss rate.

 If the SCTP message tracing shows that packets are lost, check whether the
port attribute of the GE or FE port is consistent with that on the peer device. If
it is consistent, ping the peer device to check the packet loss rate on the
transmission network.
Troubleshooting IP Path Faults
 The S1 interface is normal and cells are successfully activated, but
UEs cannot attach to the network.
 UEs can attach to the network but cannot set up bearers of some
QCIs.
 Possible Causes
 The IP route is incorrectly configured.
 The IP path parameters are incorrectly configured.
Troubleshooting IP Path Faults (Cont)
 Step 1. Check whether ALM-25886 IP Path Fault is reported.
 Clear the alarm if there was
 Step 2. Check whether IP path parameters are correctly configured.

 Run the LST IPPATH command. In the command output, if Path Type is QOS
and DSCP is 0, only default bearers can be set up. In this case, change Path
Type to ANY.
Troubleshooting OM Channel Faults
 The ALM-25901 Remote Maintenance Link Failure alarm is reported.
 OM channel faults are classified into two categories:

 OM channel unavailability: The OM channel is faulty.
 OM channel interruption: The OM channel is intermittently interrupted.
 Possible Causes
 The transmission network is faulty.
 The OM channel parameters are incorrectly configured on the

eNodeB or U2000.
 Some ports are disabled in the transport network.
Check the eNodeB Connectivity with
U2000
The eNodeB
disconnection can be
found though Main
Topology and Alarm
Browser.
Check the U2000 Routing Table
 Run the following command on the U2000 server, check
whether the U2000 has the route to the eNB: netstat –rn
 To add the route, run command: route add host/net

destination gateway
 Example: add net 10.77.204.0: gateway 10.77.198.1
Ping the eNodeB on the U2000
Server
 Check the physical connection between the U2000 server
and eNodeB whose IP address on the Solaris operating
system.
 Format
 Ping IP address of a host
“alive” indicate the connection

between the eNB and the
U2000 is secure
Trace the Route on the U2000
 traceroute IP address of a host
The target IP is
traceable!
The target IP is not
traceable!
in Typical Scenario
 Step 1. Check configurations.
 Check whether OM channel parameters are correctly configured on the U2000
client and the eNodeB.
 Step 2. Check the transmission.

 Ping the IP address of the U2000. If the IP address of the U2000 cannot be
pinged, check the route and transport network, following what described in
chapter 3.
of Intermittent OM Channel
Interruption
 Step 1. Check transmission alarms.
 Clear the physical layer alarms first, then application layer alarms
 Step 2. Check the VLAN configuration.

 If VLANs are differentiated by next-hop IP address, the check is not required.
 Step 3. Check whether network loopbacks exist.

 oversights in network design.
 temporary loopback links that were built during link tests but were not removed
promptly.
Contents
 Clock synchronization
 Two and more signals keep specific relation on frequency or phase. In other
words, the phase or frequency difference of two and more signals keeps in
conventional permissive range at corresponding effective instant.
 Base stations in FDD mode must achieve frequency synchronization. Base

stations in TDD mode must achieve time synchronization.
 Some FDD features also require time synchronization, like eICIC.
Frequency Synchronization Time/Phase Synchronization
A A
B B
Free
Free Running Running Mode
Mode
 Clock Lock Status 
 No available reference clocks.
Startup  Fast Tracking Mode

Start up
 Reference clocks become available
but the phase offset overtop the
threshold.
 Locked Mode
 eNodeB obtains reference clocks
and the frequency offset is less than
locked threshold.
 Handover Mode
 When reference clocks become
unavailable.
 Or phase offset or frequency offset
overtop the locked threshold.
Synchronization Faults
NTP Server
④
GPS/RGPS
①
F PWR
A
N
LBBP
USCU
PWR
② IEEE 1588v2
LBBP UMPT
eNodeB ③ Packet
(Clock Client) FE/GE
Transmission
Sync ETH Network EPC
 Classification of synchronization faults:

Clock Server
① Clock reference problem
② IP clock link fault
③ System clock unlocked fault
④ Time synchronization failure
Synchronization Faults
 Possible Causes
 The clock mode is incorrectly set.
 The clock source is incorrectly added.
 The clock working mode is incorrectly set for the eNodeB.
 The external reference clock is abnormal, for example, there is excessive frequency
deviation.
 The clock source is incorrectly selected, which leads to a clock lock failure.
Synchronization Faults Description
 External reference clocks for eNodeBs include GPS, synchronous Ethernet, clock over
IP, BITS, E1/T1, and TOD clocks.
 Any abnormality in a reference clock will cause the eNodeB incapable of locking the
reference clock.
 The clock status can be checked by running the DSP CLKSTAT command.
Troubleshooting Synchronization
Faults
 Step 1. Check the clock configuration for the eNodeB by DSP CLKSTAT .
 Check whether the clock synchronization mode is set to a specified mode. If not,
set by SET CLKSYNCMODE.
 Check whether the clock sources are correctly added.
 Check whether the work mode of the clock is correctly set. If not, set by SET
CLKMODE.
 If the eNodeB needs to lock an external clock source, set the clock working
mode to AUTO or MANUAL.
Faults (Cont.)
 Step 2. Check whether the external clock resources of the eNodeB work
properly by DSP CLKSRC. Pay attention to the following 2 parameters.
 License Authorized: Allow

• Run the DSP LICENSE command. If the Allocated, Config, and Actual Used
fields of the Enhanced Synchronization control item are all 1, the eNodeB
synchronization function is enabled. If not, apply license with this function.
 Clock Source State: Available
Faults (Cont.)
 Step 2. continue
 If the IPCLK is used, and the Clock Source State is Unavailable.
Check the connectivity with the IP clock server.
 Ping the IPCLK at the eNodeB
– LST IPCLKLINK to get

the IP clock server IP
address
 Login the IPCLK server to check the connectivity with eNodeB
Faults (Cont.)
 Step 3. Check whether the eNodeB correctly selects a clock source.
 When multiple external clock sources are added and work properly, the output
of the DSP CLKSRC command indicates that the status of these clock sources
is Available.
 The output of the corresponding link query command (DSP IPCLKLINK, DSP
SYNCETH, DSP GPS, or DSP TOD) indicates that the status of the clock link
is also Available.
Faults (Cont.)
 Step 4. Check whether the eNodeB correctly locks an external clock
source.
 To check the lock status, run the DSP CLKSTAT command.
 Current Clock Source: It indicates the clock source to be traced by the eNodeB.
 Current Clock Source State: The value should be Normal.
 PLL Status: The initial status should be Fast Tracking, and then Locked.
 Clock Synchronization Mode: It indicates the configured clock synchronization mode.

Contents
Definitions of Transmission Security
Faults
 A transmission security fault occurs when an IPSec tunnel
between an eNodeB and an SeGW malfunctions. This fault leads
to abnormal communication between the eNodeB and the EPC.
 Transmission security faults include:

 IKE negotiation failure
 IPSec tunnel setup failure
 Certificate application failure
Troubleshooting Specific
Transmission Security Faults
 When a transmission security fault occurs:
 The eNodeB is out of control, and all operation commands cannot be
delivered from the U2000 to the eNodeB.
 The eNodeB is under control, but transmission-related alarms are displayed.
 Transmission detection commands such as ping cannot be successfully

executed.
 Possible causes:
 Transmission security parameters are mismatched between the local and
peer ends, which leads to IPSec tunnel negotiation failures.
 Security tunnel update fails due to certificate update failures or certificate

expiry.
Troubleshooting Flowchart for
Transmission Security Faults
Start
Are IKE proposal Yes Yes

Modify IKE proposal Is the fault
configurations inconsistent? configurations. rectified?
No No
Are IKE peer Yes Yes

Modify IKE peer Is the fault
configurations
configurations. rectified?
inconsistent?
No No
Are IPSec proposal Yes Yes

Modify IPSec proposal Is the fault
configurations configurations. rectified?
inconsistent?
No
No
Are IPSec policy Yes Yes
Modify IPSec policy Is the fault
configurations
configurations. rectified?
inconsistent?
No No
Yes Yes
Are ACL rules Modify ACL rules. Is the fault
incorrected? rectified?
No No
Contact Huawei technical support.
End
Troubleshooting Procedure
 Step 1. Check whether an IPSec policy group is bound to the port
involved by LST IPSECBIND command.
Example of listing binding relationships
 If no binding relationship is found, bind an IPSec policy group to the

port by ADD IPSECBIND.
Troubleshooting Procedure (Cont.)
 Step 2. Check whether the IKE proposal is correctly configured by
DSP IKEPROPOSAL command.
Example of listing IKE negotiation results
 If the values in the red frame are inconsistent with the network plan,
run the MOD IKEPROPOSAL command to change them.
 Step 3. Check whether the IKE peer is correctly configured by
DSP IKEPEER command
Example of listing IKE peer information
 If the values in the red frame

are inconsistent with the
network plan, run the MOD
IKEPEER command to
change them.
 Step 4. Check whether the IKE proposal configuration on the
eNodeB is the same as that on the SeGW by the LST
IKEPROPOSAL command
 check whether the IKE proposal with the ID indicated in step 3 is
consistent with what used by the SeGW. Pay more attention to the
encryption algorithm, authentication algorithm, IKE version, and
key.
 If the authentication is based on digital certificates, go to 5.
 If the authentication is based on shared keys, go to 6.
 Step 5. Check whether the eNodeB's certificate chain is correct.
 Run the DSP TRUSTCERT command to check the operator's root
certificate.Example of listing operator's root certificate information
 Run the DSP CERTMK command to check the operator's device

certificate.Example of listing operator's device certificate information
 Step 5. Continue
 Run the DSP APPCERT command to check whether the certificates
used for IKE and SSL are correct.
Example of listing certificates used for IKE and SSL
 Step 6. Check whether the IPSec proposal is correctly configured
by the DSP IPSECPROPOSAL command.
Example of listing IPSec proposal information
 If the values in the red

frame are inconsistent
with the network plan,
run the MOD
IPSECPROPOSAL
command to change
them.
 Step 7. Check whether the IPSec policy is correctly configured by
the DSP IPSECPOLICY command.
Example of listing IPSec policy information

frame are inconsistent with
the network plan, run the
MOD IPSECPOLICY
command to change them.
 Step 8. Check whether the ACL rule is correctly configured
by the LST ACLRULE command.

frame are inconsistent with
the network plan, run the
MOD ACLRULE command
to change them.
Example of listing ACL rule information
Typical Case
 An IPSec policy group was bound to a port, but an IPSec tunnel failed
to be set up between the eNodeB and the SeGW.
 Fault Diagnosis
 Step 1. OM personnel checked whether the IPSec-related parameters
were correctly configured.
 The output of the DSP IKESA command indicated that the IKE SA status in
phase 1 was Ready or Ready|StayAlive, but the status in phase 2 was
None. IPSec-related parameter settings were checked and were found to
be the same as those on the SeGW.
Typical Case (Cont.)
 Fault Diagnosis
 Step 2. OM personnel checked header information.
 There were four IKE_AUTH exchanges between the eNodeB and the
SeGW. After that, the SeGW did not respond to the IKE_AUTH message
from the eNodeB. When an eNodeB has not received any responses from
an SeGW for a long time, the eNodeB will continue to send six IKE_AUTH
messages before staring the next round of authentication negotiation.
 Step 3. OM personnel checked the IKE_AUTH messages sent from

the SeGW to the eNodeB.
 The notification payload in the messages was NO_PROPOSAL_CHOSEN.
This indicated that the SeGW failed to obtain the required IPSec proposal
and therefore this round of IKE authentication negotiation failed. The
SeGW sent these messages to notify the eNodeB of this failure.
Contents
Antenna feeder System
② Pole  Main components:

 Antenna
① Antenna
 eNodeB
③
Connector  Jumper
③  Feeder
Connector  Connector
③
Connector
④ Jumper
④ Jumper
⑤ Cable Tray ⑥ Cable Clip

⑦ Feeder
⑧ eNodeB
RF Unit Faults
Antenna feeder system faults:

ALM-26529 RF Unit VSWR Threshold Crossed
ALM-26522 RF Unit RX Channel RTWP/RSSI
Unbalanced
PIM interference:
External Interference:
Abnormal KPIs
Abnormal KPIs
ALM-26522 RF Unit RX Channel RTWP/RSSI
Unbalanced
Uplink channel faults:

ALM-26521 RF Unit RX Channel ALD Antenna faults:
RTWP/RSSI Too Low ALM-26541 ALD Maintenance
Link Failure
ALM-26530 RF Unit ALD Current
Out of Range
ALM-26531 RF Unit ALD Switch
Configuration Mismatch
RF Unit Faults
 Background Information
 voltage standing wave ratio (VSWR)
 passive inter-modulation (PIM) interference
 External interference
 remote electrical tilt (RET) antennas
VSWR (voltage standing wave ratio )
 What is VSWR?
 VSWR is to measure impedance match within the

antenna & feeder system, also to measure health status
of the system.
Out power
 The format of VSWR
VSWR=(1+|Γ|)/(1-|Γ|)
|Γ|=10^( R.L./20)
50Ω
R.L. (dB)＝Backward power(dBm)－Forward power(dBm)
R.L.(Return Loss)
Feedback power
Γ, coefficient of feedback
VSWR Test in eNodeB
 The VSWR test result indicates the connection condition between the RF
unit and the antenna system. If a large VSWR value is obtained, the
antenna system is improperly connected with the RF unit. The output
power of the RF unit is not transmitted through the antenna but reflected
back. A high reflected power damages the RF unit, and the total reflection
may break down the unit.
Principle of a VSWR test
PIM (Passive Inter-Modulation)
Interference
 What is PIM interference?
an example of a PIM result
Characteristics of PIM Interference
 The stronger the input signal power is, the
stronger the power of PIM product is.
Power Frequency
PIM
 Only when the frequency
of PIM product falls in the
 The stronger the non- UL band, does PIM
linearity of the antenna Non- interference occur.
system is, the stronger the
Linearity
power of PIM product is.
External Interference
 Two types of external interference:
Spurious emission interference
Blocking
Interference
External Interference Characteristics
 Stable external interference has the following typical
characteristics:
 Two interference signals received by a receiver are correlated but with
different power. They have the same impact on the RTWP.
 External interference occupies a certain bandwidth. Monophony

interference does not carry any useful information, however, it seldom
exists.
 External interference is received only by antennas, which simplifies

the troubleshooting procedure.
Procedure to Determine External
Interference
 To determine whether external Interference exists,
 Step 1. Check whether PIM interference exists.
 Shut down downlink channels and then check whether the RTWP is
excessively high. If RTWP is normal, it means there is PIM interference.
 Step 2. If RTWP is excessively high after step 1, check whether

external interference exists. Perform the following steps:
 Disconnect an RRU or RFU from the jumper, and then connect the RRU or
RFU to a matched load or direct open-circuit to check whether the RTWP
falls within the normal range.
 If the RTWP is normal, external interference exists.
Remote Electrical Tilt Antenna
 An RET antenna can be
remotely controlled because it
is equipped with a drive called
the RCU. The RCU is installed
closely to the RET antenna.
 The right figure shows the

structure and working principles
of an RET antenna equipped
with an RCU.
Troubleshooting VSWR Faults
 Fault Description Antenna
 An alarm ALM-26529 RF Unit VSWR

Jumper
Threshold Crossed is reported if there are
VSWR faults in the RF channels of an RF TMA ②
unit. Jumper
 Possible cause
Main feeder
① VSWR alarm threshold setting problem.③
② Hardware installation is improper.
③ The supported frequency band ②
Jumper
mismatch between RRU and other
Combiner ②
components.
④ A VSWR-related circuit fault in RRU. ① RRU
④
Troubleshooting VSWR Faults
 Step 1. Check the detected VSWR value when the alarm is reported.
 Step 2. Check the VSWR alarm threshold of the RF unit.

 Run the LST RRU command
to query the VSWR alarm
threshold of the RF unit.
 If the threshold is
improper, change
it by running the
MOD RRU
command.
Troubleshooting VSWR Faults (Cont.)
 Step 3. Check the current VSWR value.
 a. Run the DSP VSWR command to query the current VSWR value.
 b. Run the STR VSWRTEST command to query the offline VSWR

value.
 Step 4. Compare the VSWR values queried by running the STR
VSWRTEST and DSP VSWR commands.
 If the two values are the same and are greater than the threshold for
reporting VSWR alarms, onsite investigation is required. Go to step 5.
 If the two values are significantly different, run the STR VSWRTEST
command to perform VSWR tests on a frequency point at an interval
of 1 MHz or smaller within the bandwidth range to compare tested
VSWR values.
 If the values are the same, go to step 5.
 If some of the values are large, collect necessary information and contact
Huawei technical support for further analysis.
 Step 5. Check the feeder connection at the local end.
 Check whether the frequency band supported by the RF unit is
consistent with that supported by the components of the antenna
system according to the network plan.
 It is recommended that a Sitemaster be used to measure the distance

between the point with a large VSWR value and the test point during a
VSWR test.
 If no Sitemaster is available, locate the fault by using isolation

methods. Add load to different parts of the feeder at the local end.
Then, run the STR VSWRTEST to start a VSWR test on each
isolation part of the feeder to locate the fault.
Troubleshooting RTWP Faults
 An RTWP-related alarm is reported.
 ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced
 ALM-26521 RF Unit RX Channel RTWP/RSSI Too Low
 Possible Causes
 The setting of attenuation on the RX channel of the RF unit is
incorrect.
 The feeder connected to the RF unit is faulty.
 Passive intermodulation (PIM) exists.
 External interference exists.
 The feeder is improperly connected with the antenna.
 The hardware in an RF module is faulty.

Troubleshooting RTWP Faults
 Step 1. Rectify the faults and modify the improper settings.
 1.1. Check whether alarms related to ALD or TDM are reported. If yes,
clear the alarm by referring to Troubleshooting ALD Link Faults.
 1.2. Run the LST RXBRANCH command to check whether attenuation of

the RX channel of the RRU is configured as planned.
 If it is not configured as
planned, run the MOD
RXBRANCH command to
modify the configuration.
 If yes, go to step 1.3.
 1.3. Check whether the ALM-26522 or ALM-26521 alarm is reported.

 If either of the alarms is reported, clear the alarm by referring to the alarm help.
 If the ALM-26522 alarm cannot be cleared perform 2 to 6.
Troubleshooting RTWP Faults (Cont.)
 Step 2. Check whether PIM interference exists
 Step 2.1. Run the ADD CELLSIMULOAD command to add a
simulated load. For example, ADD CELLSIMULOAD: LocalCellId=x,
SimLoadCfgIndex=9;
 Step 2.2. Start RTWP tracing.
If the values on one RTWP

curve are significantly greater
than the values on other
RTWP curves, PIM
interference exists.
If values on all RTWP
curves are basically the
same, there is no PIM
interference and go to step 3.
Example of RTWP tracing result
 Step 2.3. If PIM interference exists, use either of the following
methods to determine the location or device where PIM is introduced:
 Breakpoint-based PIM detection
For example, set 4 breakpoints from the RF unit top to the antenna port,
as shown in right figure. At first, disconnect the cable at breakpoint 1,
connect breakpoint 1 to a low-intermodulation attenuator, and add a
downlink simulation load.
–If RTWP values do not change, PIM interference is not caused by

the RF unit.
–If RTWP values increase, PIM interference is caused by the RF

unit.
Perform the similar steps to the other breakpoints.
 Step 3. Perform Broadband on-line frequency scan to check
whether external interference exists.
 Observe the scan result until the ALM-26239 is reported. Then, send
the local tracing results, running logs of RF units, and investigation
results to Huawei technical support for fault diagnosis.
 Step 4. Check whether a crossed pair connection exists.
 The alarm caused by a crossed pair connection has the following
characteristics:
 The alarm is reported in at least two sectors under the same eNodeB.
 RTWP variations of different RF channels are uncorrelated.
 RTWP variations are similar in different sectors.
 Two methods for troubleshooting cells with a crossed pair connection

 Perform drive tests and trace signaling without interrupting the services.
 Run the STR CROSFEEDTST command to start the a crossed pair connection
test.
Troubleshooting ALD Link Faults
Potential Failure Points of ALD system
Antenna failure
RCU installation
RCU configuration
AISG cable
AISG connector
RCU connector
Troubleshooting ALD Link Faults
 An ALD-related alarm is reported if there are ALD link faults in the RF

channels of an RF unit.
 Possible Causes
 The setting of the ALD power supply switch is improper.
 The settings of the ALD current alarm thresholds are incorrect.
 The ALD connections are abnormal.
 The ALDs are faulty.
 Fault Handling Procedure

 Step 1. Rectify the faults and modify the improper settings.
 Step 2. If the fault persists, contact Huawei technical support.
Contents
License Background Information
 License structure:
 A license consists of a common segment, a service segment, a
feature segment.
common segment
service segment
feature segment
License Background Information
 License states:
 An eNodeB can operate
in a default, protected,
demo, normal, or
emergency license state.
The following figure
shows the relationships
between these five states.
License Faults
 License faults are license-related alarms and faults that
occur during eNodeB license installation or during network
running.
 Possible Causes
 Incorrect operations
 Misunderstanding over the license mechanism
 Errors in license files
 Product defects
Troubleshooting License Faults That
Occur During License Installation
 The following error messages displayed in the MML command output means
license installation fails:
 License check failed; license serial number became invalid; the license file does
not match the product; the license versions do not match.
 The license file has expired; the file type is DEMO.
 The license control items do not match; the configured value exceeds the value in
the license file or the validity date of the control item is earlier than that in the
license file.
 Possible Causes
 The ESNs, VR versions, or product types do not match.
 The license file has expired or the license file type is incorrect.
 The system configuration items do not match the license control items.
Typical Cases
 After eNodeBs at a site were upgraded from eRAN2.0 to eRAN2.1,
the eNodeBs experienced failures to install commercial licenses. The
following error message was displayed:
 The configured value of the control item is greater than the value in the
license file
 Fault Diagnosis
 This message shows that the configured values on the current
eNodeB exceeded the limits of the license file. Compare the license
control items in the license file with the configuration that has taken
effect on the eNodeB to find the configuration items that have been
activated on the eNodeB but were not authorized by the license file.
Typical Cases (Cont.)
 Fault Handling
 Step 1. Query the configured values on the eNodeB with the
authorized values in the license file by DSP LICINFO command.
 When the configured value on the eNodeB exceeds the allocated value in
the license file, Data Configuration Exceeding Licensed Limit is displayed.
Typical Cases (Cont.)
 Step 2. Check the functions not authorized by the license file.
 Find the configuration items that are activated (the Config value is set
to 1 on the eNodeB but not included in the license file.
 Step 3. Reinstall the license.

 Modify the eNodeB configuration, disable the functions not authorized
by the license file.
 Apply for a new license file that includes these function items and in
which the allocated values are equal to or greater than the configured
values on the eNodeB. Then, reinstall the license.
Troubleshooting License Faults that
Occur during Network Running
 Related alarms
 ALM-26815 Licensed Feature Entering Keep-Alive Period
 ALM-26816 Licensed Feature Unusable
 ALM-26817 License on Trial
 ALM-26818 No License Running in System
 ALM-26819 Data Configuration Exceeding Licensed Limit
 Related events
 EVT-26820 License Emergency Status Activated
 EVT-26821 License Emergency Status Ceased
Occur during Network Running (Cont.)
 Possible Causes
 Licensed Feature Entering Keep-Alive Period
 Licensed Feature Unusable
 License on Trial
 No License Running in System
 Data Configuration Exceeding Licensed Limit
 License Emergency Status Activated
 License Emergency Status Ceased
Occur during Network Adjustment
 After a command was run to enable a function, a configuration
activation failure occurred due to license restriction.
Example of a configuration activation failure due to license restriction
Occur during Network Adjustment
 Possible Causes
 No license is running on the eNodeB.
 The license for the eNodeB has expired, and the keep-alive
period has expired.
 The license for the eNodeB does not have the permission to
apply for license control items.
Summary
Thank you
www.huawei.com

14.eNodeB LTE V100R011C10 Troubleshooting PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

14.eNodeB LTE V100R011C10 Troubleshooting PDF

Uploaded by

Copyright:

Available Formats

eNodeB LTE

Copyright © 2016 Huawei Technologies Co., Ltd. All rights reserved.

 Grasp eNodeB troubleshooting methods

 Perform the eNodeB troubleshooting

2. Troubleshooting Cell Unavailable Faults

3. Troubleshooting IP Transmission Faults

4. Troubleshooting Application Layer Faults

5. Troubleshooting Synchronization Faults

6. Troubleshooting Transmission Security Faults

7. Troubleshooting RF Unit Faults

8. Troubleshooting License Faults

Collecting fault information

Can the fault scope No

Identify fault causes

Contacting Huawei for

Inter-RAT interoperability faults

Radio frequency faults

 Huawei Contact Information

 If you are outside mainland China, contact the technical support

2. Troubleshooting Cell Unavailable Faults

3. Troubleshooting IP Transmission Faults

4. Troubleshooting Application Layer Faults

5. Troubleshooting Synchronization Faults

6. Troubleshooting Transmission Security Faults

7. Troubleshooting RF Unit Faults

8. Troubleshooting License Faults

Transmission Hardware Configuration RF

ALM-29240 Cell Unavailable alarm is reported.

 Abnormal transport resources

 Limited capacity or capability

 Incorrect data configuration usually leads to a failure in the setup of a

 Common incorrect data configuration causes

 Incorrect cell bandwidth configuration

 Incorrect cell network-related configuration

Cell1 & cell 2

Cell configuration: Band 2

RRU hardware installation:

RRU data configuration:

RRU status is abnormal

2 RRU networking is un-consistent

What we observed: Possible Cause:

activated because of  There is no license DSP LICINFO

Collect the fault info

Observe the panel

Fault cleared? No Contact Huawei

2. Troubleshooting Cell Unavailable Faults

3. Troubleshooting IP Transmission Faults

4. Troubleshooting Application Layer Faults

5. Troubleshooting Synchronization Faults

6. Troubleshooting Transmission Security Faults

7. Troubleshooting RF Unit Faults

8. Troubleshooting License Faults

User Plane layer PTN

 Hierarchical fault location idea

 In the actual network failure troubleshooting, firstly try

Access network IP/MPLS

Ping successful Ping successful

 The source device sends ICMP request packet to the destination

ICMP Echo Reply

IP address, Mask, Routing table

Cables, connectors, signal levels,

 VLAN has the following advantages:

 Improves transmission security