WLC Failure scenario: Flexconnect in Standalone Mode

Flexconnect in Standalone Mode


I recently came with a situation where a site with two old 2504 AireOS WLCs in N+1 redundancy with APs in Local mode lost one of the controllers. They were using both SSIDs with WPA2 Personal, and WPA2 Enterpise. The site was concerned about having a disruption if the remaining controller went down too. 

During the conversation with the site I pointed out that on the Flexconnect mode, when using local authentication, the WPA2 Personal SSID would work, and although I personally never really tested it, I knew you can add the Radius servers to that configuration. 

The site after finding an old 2504 WLC with licenses, finally opted for getting that old WLC and keep the existing configuration. That is probably the best option, since it doesn´t need any change, and moving to Flexconnect required testing and validation. 


In any case, I wanted to test this solution for the WPA2 Enterprise (the WPA2 Personal I´ve tested in the past and I know it works).


Flexconnect in Standalone Mode AireOS

For this test, I deployed a vWLC with version 8.5.182. On that WLC, in addition to the normal Flexconnect configurations, like mapping WLAN IDs to VLAN IDs, you will need to add the Radius servers in the Flexconnect group:

Once done, you have to add the APs to your Radius server (it can be added a whole subnet, but in my case I´m adding device per device):
I also created a different policies for each of my scenarios, being, from top to bottom for my
    9800 WLC (IOS XE)
    AireOS WLC
    Flexconnect APs
    Autonomous APs


As we can see on the below "Live" Logs from Cisco ISE, I turned on and off my devices until no WLC was available, so my Cisco 1702 AP had to be my Authenticator while in Flexconnect Standalone Mode. 


Flexconnect in Standalone Mode IOS XE

The procedure is exactly the same, just "translated" to IOS XE WLC. In this case, is configuring the Radius server in "configuration-->aaa"

And assign the Radius Server Group to the corresponding Flexconnect Group
For testing, this time, instead of powering off my WLC, I created a rule in my Firewall preventing my AP to join the WLC:
And, as expected, it also worked fine:


It probably needs some validation on your environment, but it can be an option if you are concerned of losing your WLCs

I hope this helps








Comentarios

Entradas populares de este blog

Cisco 9800 Roam Type 802.11i Slow vs 802.11i Fast vs 802.11r

Captura de paquetes desde el móvil con ANALITI

Configurar Cisco WLC y Aruba Clearpass para Guest con Mac Caching