Configure Lightweight WAPs to automatically go autonomous if WLC goes down

[Dean Romanelli]

Hi All,

I am designing the wireless standard deployment for my company. I have some push from management to go the WLC route for all sites.  However, I am not a big fan of WLC's unless deployed in a high availability architecture; Something that is already not approved - meaning that 1 WLC per site is the maximum.

Due to this, I am recommending a standalone solution, but I am being told that there is a way to configure the WLC and/or the lightweight WAPs to automatically become standalone/autonomous in the event of a controller failure so that the wireless network doesn't go down with the controller.  I tried to look this information up but am not having any luck finding it.

Can anyone verify if this is true?

[Saurav Lodh]

In an WLC failure, the Lightweight should look for a join process with the secondary Controller. It can't be automatically become standalone. It revert back to autonomous , in following way

Reverting from Lightweight Mode to Autonomous Mode

http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01101110.html

[Dean Romanelli]

Hi Saurov,

So it looks like the only way to do it according to this document would be:

A) Perform an IOS installation on the WAP via TFTP locally

or

B) Log into the Controller and issue config ap tftp downgrade command.

So if I don't have physical access to the Access Point & the Controller is down (i.e. GUI/CLI inaccessible), then there is no way to convert the AP to standalone mode right?

[Leo Laohoo · Accepted solution]

meaning that 1 WLC per site is the maximum.

Have a look at these latest Cisco promo bundles (until July 31, 2015). 

• AIR-AP1702I-WLC
• AIR-AP2702I-WLC
• AIR-AP3702I-WLC

Each of these bundles are composed of two APs (either 1702, 2702 or 3702).  The bundle also includes, FOR FREE, a WLC 2504 with 25 AP license.  So your client can now deploy APs to a site with WLC to boot.  

Option 2:  Have you tried FlexConnect?  If the WLC should go down or if the WAN link should go down, the APs can continue to service existing wireless clients even without an authentication server at the site.  With an on-site authentication server, when the WLC goes down or the WAN link goes down, the on-site can service and accept new wireless clients.  

[Dean Romanelli]

Thanks Leo, Flexconnect sounds exactly like what I'd need.  It basically makes the WAPs act like standalone AP's that are still managed by the controller right?

[Leo Laohoo]

It basically makes the WAPs act like standalone AP's that are still managed by the controller right?

Thanks for the ratings, Dean. 

Sorry for the late response as I was attending Cisco Live 2015.

That is correct, Dean.  You have three scenarios: 

1.  Without a local authentication server:  The APs will continue to service existing wireless clients.  New clients will not be able to authenticate;

2.  With an local authentication server:  The APs will continue to service existing wireless clients.  New clients will be able to authenticate; and

3.  Without a local authentication server but with FlexConnect Group:  You can create up to 100 local accounts and these local accounts can be pushed to an AP to the site.  When this happens the APs will continue to service existing wireless clients.  New clients will be able to authenticate.