I have inherited a 5 year old WLAN deployment where clients have never successfully roamed. There is a 10 - 20 second delay when moving between AP. During this break the wifi icon disappears from devices and connectivity is lost. We have a mix of iOS, Android, SurfacePro and the odd laptop on the network and all encounter the same issue. I do not see any disassociation events in the debug when this happens.
Where do I troubleshoot from here to track down the root cause? have attached a debug log
5508 (188.8.131.52) controller and mix of 3502 & 3602 AP. Dual 2.4/5Ghz
I have a similar question. We are running two WLC 5508 controllers with software release 8.3 in a HA configuration and Cisco 2802E 802.11ac Wave 2 access points.
All access points placed in the same building are attached to the same controller so that Intra-Controller-Roaming does not occur when moving in the building.
However, we sometimes observe that clients (mostly Windows notebooks with Intel 8265 wireless NIC) stay too long connected to the same AP, whereas they should already have moved to another access point that is closer.
We never have configured anything special regarding to roaming. However, is there something we can do in order to increase the roaming time to make sure clients roam to a closer AP more quickly?
After Reading the following blog post about sticky MacOS wireless clients:
I have enabled Optimized Roaming in our environment:
I'm curious about whether this will help! Will let you know in a few days.
Thanks. We will test and observe this. Fortunately, all our laptops are quite new and therefore have new chips and wireless drivers install. It it causes issues, we will disable it.
The WLC/Aps has been through many version over the years and none have made a difference.Is there a reason for you thinking upgrading to that version will resolve this?
So if the clients are sticking to previous AP, how can I validate that is indeed what is happening? On the iphones it appears disconnected but debug shows a reassociation not disconnection/association. Is a 20-30 second (sometimes minute) delay normal in these cases?
How can I tune the system to make the clients more likely to decide to roam faster instead of hanging on to an AP that it cant communicate with. Can I adjust rssi so signal strength between AP is lower?
Is there a reason for you thinking upgrading to that version will resolve this?
No point spending lot of time in troubleshooting, if current code you running have known issues. As of today 184.108.40.206 is the recommended code in 8.2 train. So let's do that first & then spend time on troubleshooting if issues is there.
Is a 20-30 second (sometimes minute) delay normal in these cases?
It is not normal taking that long to roam.
Pls give more information about how your WLAN is configured (WPA2-PSK or WPA2-Enterprise, what encryption methods, etc), is any fast roaming methods configured (like FT)
I have enabled and tested Optimized Roaming and it seems that it is indeed makes roaming faster. I just tested with a new Windows 10 laptop with Intel 8265 and wandered through the building. Each time I crossed another AP the client quickly associated with the AP.
Should be enable CleanAir in order to make things more smooth? We currently have CleanAir completely disabled, however, all 2802E access points are capable of this.