Difference between revisions of "UE connectivity troubleshooting guide"
(→Confirm the RF environment)
|Line 84:||Line 84:|
=== Confirm Radio Configurations ===
=== Confirm Radio Configurations ===
[https://wiki.yatebts.com/index.phpUE_connectivity_troubleshooting_guide#Confirm_Radio_Configurations Confirm Radio Configurations]
Revision as of 10:32, 16 January 2019
- 1 All UEs cannot see the network
- 2 One or more UE cannot see the network
- 3 UE doesn't register
All UEs cannot see the network
Confirm the unit is connected to the HC
Check for wrong IP configurations
Telnet to the unit will show messages like:
<ys1ap:WARN> Timeout connecting to 100.127.0.5:36412 [0x7f735c003630] <enb:WARN> mme1: S1-MME SCTP link DOWN <enb:NOTE> mme1: S1-MME SCTP connecting
Verify the IP configurations in the unit (GUI: ENB configuration -> core -> GTP / MME)
- Check GTP tab: The unit needs to have IP in the subnet 100.127.x.x
- Check MME tab: The HC IP should be 100.127.0.1 or 100.127.128.1 , the unit should be able to learn about this IP from DNS ; in case it couldn't we need to add it manually.
Verify the VPN
Kindly refer to VPN Tshooting
The Hosted Core accepts values for MCC = 001 and MNC =01 only.
PLMN mismatch will show similar logs in the telnet console:
<enb:NOTE> mme1: S1-MME SCTP connecting <ys1ap:NOTE> Connected 3 streams to 100.127.0.1:36412 [0x7efe7c003610] <enb:NOTE> mme1: S1-MME SCTP link UP <enb:WARN> mme1: PLMN mismatch <enb:WARN> mme1: S1-MME SCTP link DOWN
To edit PLMN configurations: (GUI: ENB Configurations -> Radio -> eNodeB)
Check the Antenna
- Check the antenna is connected correctly to the unit.
- Verify the hardware of the antenna using loopback test: DL PHY Loopback Test
Confirm the RF environment
- Verify the interference using the frequency scanner module for both GSM and LTE.
- Verify the noise value, telnet to eNB and apply (enb phy trxstats)
The reported UL noise level should be < -45 dB. If there is bad RF environment, try to change the channel.
Confirm clock calibration
The Basestation is using NTPclient (chronyd) , if the NTP client is not working this might cause some calibration issues. NTP client needs to be running for at least 6 hours when the unit is powered up at the first time to correct the calibration.
- Confirm NTP, from linux sell:
- Confirm chronyd is running (systemctl status chronyd), if its not running you can start it (systemctl start chronyd).
- Confirm chronyd is configured correctly (chronyc sources) , if there is no NTP server edit the configuration file (/etc/chrony.conf ).
- To verify the clock calibration , from the basestation telnet: (control bladerf/<> freqoffs)
- To manually trigger the calibration, from the basestaion telnet: control bladerf/<> freqcalstart & control bladerf/<> freqcalstop
Confirm Radio Configurations
- Check Tx gain value (GUI -> ENB configuration -> advanced -> system -> TxGain2)
- If the power is too low, the UE might be out of the coverage
- If the power is too high, it might cause some internal interference
- Check the receiver gain: Check the value for Receiver gain (GUI -> ENB configuration -> advanced -> system -> RxGain1 / RxGain2)
One or more UE cannot see the network
Confirm that the band in use is supported by the UE/ UEs in the netowk (GUI: ENB Configurations -> Radio -> eNodeB )
UE doesn't register
Confirm the SIM card
SIM error message
If you see a message on the UE like ( your SIM doesn't allow connection to the Network): Make sure you are using the SIM card sent with the unit. Shipped SIMs are added to the HC and tested to work correctly.
UE doesn't try to register
If the UE is throwing a fast error without trying to connect this might happen due to previous failure Try to either put the UE in airplane mode and take it off or to restart the UE.