LTE TROUBLESHOOTING

1.
2.
3.

ENODEB TRACE............................................................................................2
Signalling traces on wireshark.........................................................................6
Scheduler trace...............................................................................................7

1. ENODEB TRACE
At enodeb call trace can be taken via flowfox. Flowfox will take a decoded call
trace log, and produce a visual sequence diagram indicating the flow of
message exchange.
Below is the procedure to take enodeb call trace via flowfox :

Prerequisite to start the activity is that Cygwin should be installed at

laptop
download
lteflowfox
from
http://utran01.epa.ericsson.se/flowfox/#lteflowfox
Keep the flowfox decoder at C:\cygwin\home\<signum> & extract here
Install the flowfox by running below command from cygwin at home dir.
bash INSTALL . Now Flowfox tool is ready to use.

The activation of traces is done by using the trace & error functionality. To get a
description of the commands, just type man te at the prompt of the eNodeB.

There are several Trace Groups which could be activated

Warning: Activate all trace groups usually gives an overflow in the tracelog or
even worse it can lead to system overload causing a crash

Launch cygwin window 1

Connect the laptop to LMTB port of DUL & assign ip 169.254.1.11 subnet mask
255.255.0.0 ( Internal ip of DUL is 169.254.1.10 )
Login to DUL :
moshell 169.254.1.10
Login/passwd
( By default user name & passwd in rbs/rbs )
Activate LTE trace Track :
te default
te e all Ft_S1AP_ASN
te e all Ft_RRC_ASN

te e all Ft_X2AP_ASN
For Handover :
te e all INCOMING_HANDOVER
te e all OUTGOING_HANDOVER
Verify activated trace :
In order to verify what traces are activated in the CPP node can be used the command
lh all fte s
User attached in enodeb:
In order to observe the number of users attached to each cell use the folllowing
command:
ue print admitted
Activate Ue monitoring
Once the traces are activated in the CPP node the UE monitoring must be activated.
Otherwise, only LTE signalling will appear (not UE signalling). For help type h ue
ue enable -allcell -allUe
Also run below command
secmode -m u
tm -status
tm -udp <ip address of lptop>
tm -attach 2 000100
tm save
Launch cygwin window 2
cd ltetools ( Change the path to ltetools )
./terouter <ip address of enodeb>
Launch cygwin window 3
cd ltetools
./teviewer |tee <filename1.txt>

(In this window , user will get the call trace in raw format)
Launch Cygwin window 4
cd ltetools
tail
f
<filename1.txt>
/home/<signum>/ltetools/lteflowfox.pl

|/home/<signum>/ltetools/ltng

Connect UE & try to make attach

Above command will give the graphical representation of message exchange
between UE & ENODEB.
Below is call trace for successful attach . One can easily find out the attach failure reason
from below messages :

Disable UE monitoring
ue disable allcell
Deactivate cell trace
te d all Ft_S1AP_ASN
te d all Ft_RRC_ASN
te d all Ft_X2AP_ASN

2. Signalling traces on wireshark

Wireshark traces will gives detailed analysis of message exchange between
enodeb,MME,HSS,SGW.
Wirehark tarces can be taken via mirror port for enodeb & MME.
Donwload the Wireshark tool from below link & install at your laptop.
https://ericoll.internal.ericsson.com/sites/wireshark_at_ericsson/Download
s/default.aspx
Connect the laptop at mirror port via Ethernet cable.
Launch wireshark.
Go to interfaces option & start traces on interface specified.
Connect UE & try to make attach & capture wireshark traces.
Go to interface option & stop traces on interface specified & analyze the trace.
Below is the call trace for successful attach for your reference.

3. Scheduler trace ( For Throughput )

Below is the procedure to take enodeb call trace via flowfox :

Prerequisite to start the activity is that Cygwin should be installed at

laptop & Tet.pl is also installed , which gets installed as p