Controller Discovery and Standalone Operation

Ruckus Access Points can operate in standalone mode, be managed by Unleashed Multi-site Manager (previously FlexMaster) server, or be managed by any of the Ruckus controller products.

How Standalone APs Learn Controller Addresses

If your APs will be managed by a controller, you will need some way to ensure that the APs can discover the controller on the network. There are several different ways to do this, and the specific controller user documents contain more details on discovery for that particular controller product family.

This section provides a brief overview of the options available for controller discovery.

Ruckus Cloud

Ruckus APs discover Ruckus Cloud controllers by querying the Ruckus Cloud AP Registrar (ap-registrar.ruckuswireless.com) via HTTPS to learn the Ruckus Cloud address. APs will search for a Ruckus Cloud controller more frequently after initial boot up, and less frequently after the first 14 days.

Standalone APs will query the Registrar with the following frequency:

How often APs query the Registrar to learn Ruckus Cloud controller addresses

Query Frequency AP Uptime
15 seconds < 1 hour
5 minutes 1 hours ~ 48 hours
1 hour 2 days ~ 14 days
12 hours 14 days ~ forever

SmartZone

APs discover SmartZone controllers using any of the following methods:

  • mDNS discovery on local IP subnet
  • DHCP Option 43 sub-option 6
  • DHCPv6 Option 17 sub-option 6
  • DHCPv6 Option 52
  • DNS entry named "ruckuscontroller.<local domain>"
  • AP CLI command "set scg ip"

ZoneDirector

APs discover ZoneDirector controllers using any of the following methods:

  • IP subnet broadcast
  • DHCP Option 43 sub-option 3
  • DHCPv6 Option 17 sub-option 3
  • DHCPv6 Option 52
  • DNS entry named "zonedirector.<local domain>"
  • AP CLI command "set director ip"

For more information on AP controller discovery, refer to the user documentation for the respective Ruckus controller (Ruckus Cloud, SmartZone or ZoneDirector).