FlexConnect Local Switching - Client roaming issues.

[sardarjion]

I have a simple setup of WLC 2504 v8.3.150.0 + 1142 + 2702 + RVS 4000 router with no VLAN. 

My requirement is to setup these two APs in FlexConnect mode. I have provided the snapshots of settings for the SSID. 

I have created a separate AP group for these two APs in FlexConnect mode. My main problem is client roaming is not working. I have Win 10 Lenovo T490s laptop where I start a continuous ping to one wired machine on network. The laptop connects to 2702 and pings start. Now I move the laptop to different room closer to 1142 and 2702 completely goes away as I move to one corner of the room. The expectation is that laptop should connect to 1142 and pings should continue. I see initial request timeouts and then general failures as I lose the IP address. The only way to reconnect is to turn of the laptop wifi and then turn on again. 

I did another experiment where I simply just disabled the option "FlexConnect Local Switching" and roaming works flawlessly. So maybe I am missing some setting which is causing this roaming failure. 

Any help would be appreciated. Thanks. 

[m.george]

Thanks for the suggestion. Unfortunately entering the command resulted in Error: WLAN <your_wlan_id> enabled. My struggle is with an older facility we have inherited running a pair of 2504 WLCs with a mixture of 1532, 1562, 2702 and 2802 access points with the outdoor access points working in a below freezing environment, in case the added detail is useful to you. I can see the host associate with the access point but I haven't yet managed to track the mechanism by which the roam failure occurs. I have taken a third party access point to site and confirmed the behaviour also occurs when roaming between vendor devices. Now I'm feeling like I am highjacking someone else's ticket!

[Mark Elsen]

                         >...Error: WLAN <your_wlan_id> enabled.
 - You may want to temporarily disable the WLAN and then execute the command suggested , 

 M.

[JPavonM]

You can also try disabling PMK caching on the wireless profile in Windows machine to see how it works.