User guide
Table Of Contents
- Introduction
- Hardware setup
- Connection to AMARI UE Simbox
- LTE service
- Initial setting
- Create scenario using WebGui
- Run UE scenarios with WebGui
- Create scenario without WebGui
- Downlink and Uplink transfer using iperf
- NB-IOT devices
- Channel simulator
- logging
- Advanced options
- Troubleshooting
Chapter 14: Troubleshooting 46
• If Downlink transfer is run with iperf, verify that bitrate set in iperf is higher than expected
throughput (at least 10%)
14.4 RRC STATE locking value
When running NB-IOT test, the RRC state may report "Locking" value . This is visible when
typing "ue" command in LTE UE screen. This state means that LTE UE has not been able to
synchronize on eNodeB side. This is likely due to wrong EARFCN or RX signal level
14.5 Connection to webGui fails
If your browser fails to load the webGui page (xx.xx.xx.xx/lte), check that :
• httpd service is running on LTE UE SIM side (service httpd status)
• Test with another web browser (Firefox, Chrome or Internet Explorer). Avoid beta version
of web browser
If the main page can be loaded but connection to server fails, check that
• LTE service is running on LTE UE side (service lte status)
• Server configuration is correctly set, i.e ip address and port com. Port com default value is
9002
• No firewall blocks the IP traffic between PC and LTE setup
14.6 TRX discontinuity too wide
TRX discontinuity too wide means that frames number on cell 1 and 2 are misaligned . This
may have several root causes.
• Simply reboot your setup. This can solve the problem otherwise, follow steps below.
• If you have more than one SDR cards, check that SDR cards are synchronized with each
other with the USB cable. You must also identify the sdr mapping to know which connector
shall be used (input or output). Please see installguide.pdf for more details
• Check that both eNodeB cells are synchronized (frame boundary and Frame number) . LTE
UE simulator doesn’t support asynchronous cells.
• If problem occurs during data transfer test, this can happen when PC is running out of
CPU. To check it:
-Run lte init.sh script available under /root/ue directory.
-Run the Linux top - H command to check if unexpected process are loading the CPU.
-Remove unnecessary drivers and peripherals such as WiFi dongle.
-If you use a HDMI monitor, disconnect it and access the system remotely by SSH for
instance.
-Ensure that your CPU is fast enough. It should be at least a Intel 4 Core i7 with a clock
running at 3.6 GHz.
-Remove unused daemons or cron jobs.