Wireless client bouncing between two AP's even though it's not moving

[Christopher Rudi]

Stumbled upon an odd issue. I have a 5508 running 8.0.133 with 2702i AP's attached. According to Prime 3.1 I see clients connect to AP1 then 25 minutes later connect to AP2 then 25 minutes later connect back to AP1. This goes on over and over and over even when the device is sitting on a desk not moving or being used. I did find that TPC was set to optimize for interference and not coverage so I changed it because power output on the AP's was just going crazy and I thought that was confusing the clients but the issue still persists. We'll get random complaints of weak signal or unexpected drops even though we were surveyed for 5ghz at -62dbm throughout and I can't help but wonder if the issues are related somehow. Any thoughts? I hope this isn't a code bug because I still have some older AP's on this controller that I can't upgrade any further. Thanks!

[Flavio Miranda]

Hi

 I dont believe this is a bug at all. Sounds like the signal strength is varying and the client is taking decision to join the better AP. This is a typical interference problem.

 Try to take a look on the client driver configuration and change roam behavior. Try to let this less sensitivity as possible. Roam is a client decision no AP decision.

-If I helped you somehow, please, rate it as useful.-

[Christopher Rudi · Accepted solution]

Thanks for the reply! I've been doing some more digging and found that the Session Timeout value is set to 1440 seconds (24 min) instead of 14400 seconds (4 hours) so I think that also explains why I see clients connecting for 25 min +/- then re-associating even in the middle of the night. We'll check the roaming settings on the devices and adjust the sensitivity as well so hopefully between the two I should see more stable connections. Thanks again!