Ruckus vSZ – Manual AP pointing to vSZ

As we delve deeper into Ruckus as a WLAN vendor, more information about how their vSZ platform works will be divulged here.

There are several ways to get an AP to communicate with the vSZ.  Assuming that the traditional DHCP option or DNS are not working, accessing the AP via SSH/serial may be the last hope.

To view the current connected state, issue the command:

get scg

You’ll see something like the following

rkscli: get scg

—— SCG Information ——
SCG Service is enabled.
AP is managed by SCG.
AP is registered in SCG.
State: DISCONNECTED
Server List: a.b.c.d, 1.2.3.4
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
—————————–
OK
rkscli:

The server list is the list of known servers that the AP has discovered by any means – or a server that has been manually entered.

To assign an IP to for the server, use set scg ip x.x.x.x

After that you can do a set scg disable and then a set scg enable to stop/start the discovery process.

If all works as it should, the next get scg will show something like this:

rkscli: get scg

—— SCG Information ——
SCG Service is enabled.
AP is managed by SCG.
AP is registered in SCG.
State: CONNECTED
Server List: a.b.c.d, 1.2.3.4,
SSH tunnel connected to 1.2.3.4
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
—————————–
OK

Note the State: CONNECTED now and the SSH tunnel connected.  The AP should not be in the Staging Zone of your vSZ and ready to be assigned to a Domain or Zone.