Debugging Performance Issues
Q: What are the commonly reported issues?
After provisioning LTE AP and enabling transmission, there may be rare scenarios that can cause performance issues.
The following table is a list of typical performance issues and suggested corrective actions.
|1||Poor data rate||Poor data rate measured in DL/UL or both directions compared to expected throughput.||
|2||UE disconnects frequently from network.||UE connection is dropped frequently and reconnects after unplugging.||If using a USB dongle/Wi-Fi Device over USB, check the dongle USB connection.|
|3||EPC connection down.||S1 connection disconnected after successful connection during initial setup.||
|4||AP not transmitting although all connection are successful.||All LEDs are solid Green but LTE is dark - transmission stopped.||
|5||Timing sync lost/ SYNC LED starts to blink.||In general, when a timing sync is lost, the SYNC LED is dark/blinking indicating it is trying to regain connection with timing master/GPS.||
Case 1: LTE AP is in sync but has disconnected from the ACS and/or Mgmt SecGW
Review the following information.
- An AP reboots 24 hours after disconnection with the AP management platform when it is unable to reach LTE AP Management.
- After reboot, an AP connects to the SC-R.
- The SC-R sets relevant IP address of the SecGW and LTE AP management (ACS) on an LTE AP.
- The LTE AP attempts to connect to the LTE AP Management
- If an LTE AP is unable to connect, it keeps on retrying for 24 hours. On completion of 24 hours, steps 1, 2, and 3 mentioned above are repeated.
- An AP repeats the above steps for a total of 3 times, one each reboot after 24 hours.
- After a total of 96 hours from the first disconnection, AP reverts to the factory reset. In this case, any configuration that was set from ACS or using the CLI, get reset and in this case the earlier AP configuration is erased.
Note: The above-mentioned behavior is for the disconnection/not reachable case only. SC-R: sc-registrar - A database/ service in the management platform that provides each AP important connectivity information upon power up.
Case 2: LTE AP is in not in sync and has disconnected from the ACS and/or Mgmt SecGW:
Review the following information.
- If after startup, the PTP hard sync does not occur, the behavior for network disconnection mentioned in case I above should be used.
If an external PTP device is configured (not using a Ruckus AP as the Timing Master) to provide timing information to the network, ensure that the following settings are set on the PTP source:
- Ensure that the PTP source and rest of the APs are on the same Layer 2 network and the PTP traffic is allowed on any firewalls in between.
- Select the 8275.2 profile on your timing source administration/ configuration page.
- Set Domain to 44.
- If GPS synchronization is does not occur from startup or the PTP phase sync is not achieved (but the PTP hard sync has been achieved), RSC reboots every hour till the synchronization is achieved. The timers mentioned in case I above does not apply in this case that is the LTE AP does not go to SC-R or perform a factory reset.
- If AP was already synchronized when the network disconnected, and if it loses synchronization that is goes into holdover.
a. LTE AP reboots after 1 hour in the case of the PTP master assuming that 24 hours of the network disconnection have not occurred
b. LTE AP reboots after 2 hours in the case of the PTP slave assuming that 24 hours of the network disconnection have not occurred
- If after reboot, AP achieves synchronization, but is still disconnected from the network, in that case behavior for network disconnection mentioned in case I above shall be used. Note that the disconnect reboot timer is applicable from the reboot in such a case.
- If after a reboot, AP does not achieve synchronization, the behavior mentioned in this case II is applicable.