X2 link failure

investigation
Tigo LTE Tanzania
X2 link failure investigation

› REASON1
Initiating eNodeB unware of the candidate eNodeB’s CP IP

› REASON2
The reachability between initiating/candidate eNodeB with issue

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 2

REASON 1 : Initiating eNodeB unware
of the candidate eNodeB’s CP IP

› Basic information
When the initiating eNodeB knows the address of the candidate eNodeB, SCTP connectivity can
be established and the X2 interface can be set up between the eNodeBs.

› Network Requirements
A Domain Name System (DNS) server is available in the network and configured with DNS
resolutions for involved eNodeBs.

› In Tigo LTE project,no DNS server provided.

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 3

 CONT.1_phenomenons
› Take LDAR269 as example.
TermPointToENB OP. state and alarm got from eNodeB

› All the 9 TermPointToENB

created by ANR are all
disable,due to unware of
the candidate eNodeB CP
IP.

› As per alarm, 9 candidate

sites X2 interface with
alarm,refer to the MO
TermPointToENB OP. state. It
can conclude that the alarm
caused by MO
TermPointToENB OP. state is
disable.Not possible to setup
the X2 link.

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 4

Cont.2_phenomenons
› Reachability between LDAR269 & LDAR002

› Even the X2 setup failure between LDAR269&LDAR002,but when try to ping from
269 to 002,the IP layer reachability is no problem.

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 5

Cont.3_phenomenons
› L3 logs got from eNodeB
As per 3GPP 36.413,the standard message “eNB Configuration Transfer”&”MME Configuration
Transfer” bw eNodeB and MME.And the SON Configuration Transfer IE contained.
From the log got from eNodeB,the message with SON Configuration Transfer IE sent to Huawei
MME,but no any response from MME.

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 6

CONT.4 : REASON 1 CONCLUsION

› After discuss with Huawei side,a Huawei MME (USN9810)optional feature “eNodeB
SON Configuration Transfer” not activated,and it can relay the message between the
initiating and candidate eNodeBs,so no “MME Configuration Transfer” response to
eNodeB.

› Hence,even the router reachability is ok,but initiating eNodeB cannot aware the
candidate eNodeB IP,it causes the X2 setup failure.

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 7

REASON 2 : The reachability between
initiating/candidate eNodeB with issue
› Still take LDAR269 as example
› Reachability between LDAR269 & LDAR043

› The reachability between LDAR269&LDAR043 is not ok,so need to first solve the
transmission IP layer problem.

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 8

CONT.1 : REASON 2 CONCLUsION
› Because the reachability has problem,it’s caused by transmission network,need to
double check the transmission first.

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 9

Feasibility study | © Ericsson AB 2014 | 2014-11-17 | Page 10