FlexConnect AP reboot when WLC down

[SPKV]

In case the Flex AP loses contact with WLC ok, it will convert to standalone mode and still serve the client normally.

But while WLC is going down and Flex AP reboots, after the AP is back. Will it be able to continue working in standalone mode? (If WLC has not returned yet)

Thanks

[Scott Fella]

The ap will continue to try to join the controller and once there is a response, the ap/controller will go through the join process and the ap will re-join the controller.

[SPKV]

In case AP reboots once the controller is still down? What will AP be like? Can't work at all because it can't find controller or can resume working in standalone mode until controller is back ?

[Scott Fella]

The ap will resume to work, but please refer to the FlexConnect guides to show you the limitations of FlexConnect, especially if using 802.1x as an example.  It is always best to test this yourself, especially that code versions and or ap/controller models can have different effects (bugs).  You can always console into one, change the vlan on the switchport to a non routable vlan or a vlan that can't reach the controller and see what the console output shows you.  Then you can also test to see what SSID's you see.

[jonathga94]

When an AP disconnects from a WLC, it will continue providing WiFi service to any clients that were already connected. However, it will not accept new associations (this is true if the SSID is configured for local switching central association). If the AP reboots, it will not provide WiFi service to any clients until it reconnects to a WLC.

[SPKV]

"If the AP reboots, it will not provide WiFi service to any clients until it reconnects to a WLC."

I've understood that before. but in my test when AP reboots once the controller is still down, AP is back from reboot can resume working in standalone mode and provide Wi-Fi service to clients normally via PSK

[Rich R]

Yes, you're right it CAN provide service without a WLC - it really depends on how the WLAN is configured and what version of code you're running as @Scott Fella mentioned - because there've been various improvements over the years.  It can even handle 802.1x (with some caveats like no accounting) if there's a local radius server configured in your flex profile.