Troubleshooting APs

In this section:

1. Entering the AP CLI
   The AP command line interface (CLI) is the primary access interface for individual APs. It can be used for debugging AP issues, gathering data, configuration, and troubleshooting tasks.
2. Changing the AP Password
   If the AP has already been onboarded in the SmartZone controller, the AP has inherited the access credentials from the Zone where it belongs. If the AP is online in the controller, you can configure a new password to the Zone or individual AP.
3. Changing the AP IP Address
   You can configure an access point (AP) to use either a static IP address or obtain one dynamically via DHCP. This section explains how to change the AP IP address using the controller web UI or the AP CLI.
4. AP Cannot Onboard the Controller
   Onboarding an AP to the SmartZone controller is a straightforward process; however, specific scenarios can complicate the procedure. This topic describes the methods for collecting diagnostic data when an AP fails to onboard to a SmartZone controller. The collected data enables RUCKUS Support to identify the root cause and recommend corrective actions.
5. AP Cannot Update Configuration Changes
   Normally, after pushing a configuration change to an AP, the AP Configuration Status will transition from New Configuration, to Updating..., and Up-to-date. This topic describes the methods for collecting diagnostic data when an AP fails to apply configuration changes pushed from a SmartZone controller. The collected data enables RUCKUS Support to identify the root cause and recommend corrective actions.
6. AP Reboot Issues
   Access Points could experience unexpected reboot issues, which can disrupt network stability and performance. This topic describes the methods for collecting diagnostic data from SmartZone-managed APs that encounter such reboots. The collected data enables RUCKUS Support to analyze and resolve the issue efficiently.
7. AP PoE Issues
   Power over Ethernet (PoE) issues can manifest in various ways, ranging from an AP failing to power on to intermittent reboots or connectivity loss. These symptoms often point to underlying problems in the switch configuration, AP power negotiation, or physical cabling. Diagnosing PoE issues requires a layered approach—starting from the physical layer and progressing through switch and AP configurations.