Converting a Ruckus AP that is in a vSZ to an Unleashed AP is not something I do often, and it is one of those things that I always forget. I decided to put a quick how-to this time.
If you have a Ruckus AP in the vSZ you can SSH into it but you are not able to access the web GUI. I tried to disable and reset the “scg” service, but that did not work. SSH Tunnel shows that it is still up and connected to the vSZ.
SCG Service is disabled.
AP is not managed by SCG.
State: Not Available – busy or not running.
Server List: 192.168.10.11
SSH tunnel connected to 192.168.10.11
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 intervals: 300|30
SCG gwloss|serverloss timeouts: 1800|7200
It’s possible that I may have to wait for it to time out but I don’t have all that time. So I simply deleted the AP from the vSZ and ran the “get scg” command again.
SCG Service is disabled.
AP is not managed by SCG.
State: Not Available – busy or not running.
Server List: Not found
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 intervals: 300|30
SCG gwloss|serverloss timeouts: 1800|7200
SSH Tunnel is no longer connected and I can successfully access the web UI.
This was something important. I tried the default credentials, thinking that AP may have reset them. But it actually kept its last known credentials. Once logged in, I had access to the following menu:
From here, I can simply access the “Upgrade” section and load the unleashed code.
