AP no longer showing SSID when disconnected from ZoneDirector

[jonathan_marlow]

I have Ruckus products in all of my offices... we have a few sites that are connected via VPN to the main site and others are on an MPLS connection... When any of the sites loses connectivity to the main site, the ZD becomes unreachable... When this happens, nobody can connect to the wireless network until connections to the main site are restored... I understand that this may be the proper behavior by design, but it's a bit of a problem...

I need to have some sort of a backup plan for when someone comes into the office and the network is unavailable... is there a way to have the AP's use their last config until the ZD comes back?

here's a very similar topic, but it was almost a year old, so I thought it best to open another...
https://forums.ruckuswireless.com/ruc...

[michael_brado]

Try to keep your MPLS VPN up/connected is the best advice. Your APs will lose
heartbeat connectivity with the ZD and eventually reboot after the Auto-Recovery
period of time you may have set on Configure/APs page, AP Policies.

More importantly, your remote clients will not be able to use any back-end auth
methods that involve the ZD, AAA servers, HotSpot, WebAuth, or communicate
over any Tunneled WLANs, however your clients using any L2 type of connection,
like WPA2-PSK will still have access to local resources (servers/printers), until the
APs reboot. Clients connected by the other methods will have local resource
access, until they roam (and cannot re-authenticate).

[jonathan_marlow]

so, in other words, the only way to keep my wireless up at those sites that lose connectivity is to not lose connectivity? That's pretty rough... I have an Airnet from Cisco that happily continues working when the internet is out at one of my sites even though it cannot contact its controller, which happens to be across the country... I guess I just thought that Ruckus should be able to do this if Cisco can...

[michael_brado]

Yes, WLANS configured with Open or PSK authentication, which are not tunneled
back to the ZD, will still continue to provide service at the remote sites, to local
resources, just not the Internet too.

They will continue to do so for at least as long as your auto-recovery reboot period.

[jonathan_marlow]

but once they reboot for auto-recovery, if the ZD isn't available, it won't even revert back to any sort of defaults? No matter what the configuration is, once the ZD is unavailable, the clock is ticking... once the clock counts down and it attempts to reboot, that's it until the ZD comes back, right?