Skip to content

Ruckus Unleashed Administration

Unleashed is Ruckus's controller-less deployment mode: the controller software runs on the APs themselves, so there is no ZoneDirector or SmartZone appliance to buy, power, or fail. One AP acts as the Master (hosting the web UI and config), the rest join as members. Same AP hardware as controller-managed deployments — the difference is which firmware image the AP runs.

Where It Fits

Unleashed ZoneDirector SmartZone
Controller None — runs on the APs Hardware appliance Appliance or virtual (vSZ)
Scale ceiling Release-dependent, up to 128 APs / 2,048 clients (see below) ZD1200: 150 APs licensed Thousands of APs
Newest APs Actively developed — recent releases add Wi-Fi 7 AP support Frozen at Wi-Fi 6 Full current lineup
Licensing None Per-AP licenses Per-AP licenses

Scale & Limits

The AP ceiling depends on release and topology, not just a single number:

  • 128 APs / 2,048 clients per network in bridge mode from release 200.8 onward
  • Running the Master as the network gateway (Unleashed doing NAT/routing) drops the ceiling sharply — keep the Master in bridge mode behind a real firewall for anything beyond a handful of APs
  • Any older Wave 1 (802.11ac gen-1) AP in the network caps the whole network at 25 APs
  • From release 200.15, a Dedicated Master mode (Master serves management only, no clients) raises support to 150 APs, 16 Ruckus ICX switches, and 4,000 clients

On a mixed-generation estate, the oldest AP sets the rules — check the release notes for the model mix before assuming the ceiling.

Master AP & Elections

  • The Master holds the configuration and serves the web UI; members sync from it
  • A Standby Master is elected automatically — there is no GUI option to choose it. If the Master fails, the standby takes over with the synced config, and clients keep working through the transition
  • The CLI can influence roles where needed:

Unleashed CLI (SSH to the Master) — privileged mode:

! Prefer this AP as Master, or pin it as member-only
ruckus# set election role master
ruckus# set election role member

Per Ruckus KB 000006295, the standby specifically cannot be forced — only Master/member preference can be set.

First-Time Setup

A factory-fresh Unleashed AP boots, takes a DHCP address (DHCP is the default IP mode), and broadcasts a temporary unencrypted 2.4GHz SSID named Configure.Me-[xxxxxx]:

  1. Connect to the Configure.Me SSID
  2. Browse to unleashed.ruckuswireless.com — this resolves to the AP's setup wizard while on that SSID
  3. The wizard walks through: system name → first WLAN → management IP settings → admin credentials
  4. Additional Unleashed APs on the same network discover the Master and join automatically, subject to approval settings

The RUCKUS Unleashed mobile app (iOS/Android) can run the same initial setup and day-to-day monitoring — genuinely usable for quick checks, not just a marketing checkbox.

The Configure.Me SSID is open — do initial setup somewhere controlled, not with the AP already broadcasting in a public space.

Day-to-Day Management

  • Everything is managed from the Master's web UI — WLANs, AP list, clients, mesh, upgrades. The WLAN model (WLANs, AP groups, VLAN mapping) matches the concepts on Ruckus AP & WLAN Administration
  • Firmware upgrades are network-wide from the Master — upload once (or use the online upgrade), and the Master distributes to all members. Members must run the same release as the Master; a joining AP on different firmware gets re-imaged to match
  • SSH to the Master gives a ZoneDirector-style CLI (enable/config modes); member APs have a limited local CLI. Syntax is documented in the Unleashed CLI Reference Guide for the running release — verify with ?/tab-completion rather than assuming ZD commands carry over

Firmware Images & Conversion

The same physical AP can run three different firmware personalities:

Image Behavior
Unleashed Controller-less, as this page describes
Solo / standalone Single independent AP, local web UI at 192.168.0.1 default, no clustering
Controller-managed (ZoneDirector/SmartZone) AP joins a controller and is managed there

Converting between personalities means flashing the corresponding image for that AP model from the Ruckus support downloads — e.g. an AP bought as ZoneDirector-managed must be re-flashed with the Unleashed image before it can join an Unleashed network, and vice versa. Check the AP model's supported-releases matrix first: not every model has an image in every personality and release.