Flex connect issue

[qsosan20]

Hello Experts , 

I have an AP that's operating in Flex mode and registered to 9800 WLC , 

After complaining from clients that random disconnections happening to wifi , i took debugs for one of the clients at the disconnection time and found that client has been disconnected due to AP was unregistered from WLC due to a connectivity issue , now my question if AP operating in Flex mode and SSID policy also in Flex mode , hence even if ap disconnected from wlc , client should continuo operating normally as per my understanding to how FLEX mode works , is that correct ?

[Leo Laohoo]

Reboot the AP.  

If problem persists, reboot the controller. 

It could be CSCvx56223.

[qsosan20]

Hi Leo , 

Thanks for your reply , 

I will reboot the AP for now and see ,

For the bug its affecting 17.3.3 and earlier , however my AP is 

17.3.5.43,

[Leo Laohoo]

Always assume the bug affects all version.

[JPavonM]

@qsosan20 yes your assumption is right, clients should keep connected to a Flexconnect AP even when the AP is disconnected from WLC, but new clients won't be able to connect unless you have configured local-authentication in the Flex profile.

[qsosan20]

Thanks for your conformation @JPavonM  

[marce1000]

  - Yes , client should be able to continue working on a flexconnect based AP
     Check controller software version installed and consider 17.12.3 as latest advisory version
     especially if you are on an older release currently

  + Always useful :  -  Have an overall checkup of the  9800  WLC controller's configuration with the CLI command
       show tech wireless and feed the output from that into Wireless Config Analyzer
      use the full command as denoted in green , do not use a simple show tech as input for this procedure
                   (Actually you may consider the above mandatory when working with 9800 controllers)

 M.

[Rich R]

IOS-XE 17.3 is effectively end of life:
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/ios-xe-17/ios-xe-17-3-x-eol.html
Upgrade as per the TAC recommended link below.

If the WLAN is using local switching, authentication, association and DHCP then it should continue operating in standalone mode.  You should have:
no central association
no central authentication
no central dhcp
no central switching
configured in the wireless profile policy for the WLAN.

What type of authentication are you using on the WLAN?