Ruckus AP not connecting to Virtual SmartZone

Here are a list of things to troubleshoot when a Ruckus AP is not registering to a Virtual SmartZone (VSZ) cloud controller.

1. Ensure that the public IP address of the site where the AP resides is permitted through the firewall protecting the VSZ.
2. Check that the AP has a valid private IP address and is pingable from the router at that site.
3. SSH into the AP.  default credentials are super/sp-admin).  If those credentials don’t work then the AP has received its config from the controller and the zone credentials must be used.

1. 1. Ping an external IP address to confirm the AP can reach the internet.
   2. Run “get scg”
      

      rkscli: get scg
       ------ SCG Information ------
       SCG Service is disabled.
       AP is not managed by SCG.
       State: Not Available - busy or not running.
       SCI is disabled.
       Server List: (IP or FQDN of VSZ shows here)
       No SSH tunnel exists
       Failover List: Not found
       Failover Max Retry: 2
       DHCP Opt43 Code: 6
       Server List from DHCP (Opt43/Opt52): Not found
       SCG default URL: RuckusController
       SCG config|heartbeat|mesh status|status intervals: 300|30|300|900
       SCG gwloss|serverloss timeouts: 1800|7200
       ----------------------------

      1. If you see “SCG Service is disabled” Then run “set scg enable” and this should start the SCG service.
      2. If the Server List is incorrect or empty run “set scg ip {IP or FQDN goes here}” to point the AP to the VSZ