Client roaming issue between APs

[girish_gavandi]

Hello,

I have a wireless network built with Cisco WLC 5520 (in HA), AP 3702 and AP 3802. WLC is running code 8.5.135.0.

APs are placed in the bldg. considering user density and after a proper site survey. Distance between APs is not more than 15m.

When the client is roaming between the AP, (while in a corridor) the client device is not connecting to the next closest AP. Client device sticks to the same old AP to which it got connected first. This causes the client device to disconnect from the network even though it is in an excellent coverage.

This behavior is not seen in another network with Cisco WLC 8510 running code 8.2.151.0 and AP 3702.

Attaching client debug while roaming between APs in the corridor.

Any help is much appreciated.

regards,

Girish

[Haydn Andrews]

Ultimately the decision to roam is the clients decision. When you say  no issues running 8.2.151.0 was that this network or another one? Because the RF is not going to be exact for each of them.

Is this happening to all clients or just this one or one type of device?

8.5.135.0 is not TACs recommended version, they recommend 8.5.140.0 can you upgrade? https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html

Can you share show WLAN <ID> of the SSID that the client is having trouble roaming, also be good to share the same from the site its not having trouble

[Leo Laohoo]

---

@girish_gavandi wrote:

When the client is roaming between the AP, (while in a corridor) the client device is not connecting to the next closest AP.

---

What kind of clients?  Are these smartphones, tablets or laptops? 

If they are laptops are the drivers to the wireless NIC updated? 

[girish_gavandi]

Hi,

I did some testing using few different endpoints and found that the Android with code 9.0 are having issues. Client details are below.

------------------------------------

Endpoint: Samsung Galaxy Note8, Android Pie 9

While walking in the corridor this phone sticks to the farthest AP to which it got connected first until the signal from that AP fades away. Then connects to the new nearest AP. There is a disconnection here.

------------------------------------

Endpoint: iPhone 8, iOS version: 12.1.4 (16D57)

Works fine while walking in the corridor with this device. No disconnection is seen and connects to the nearest AP with good signal strength.

------------------------------------

Samsung Galaxy (model: SM-G531F), Android 5.1.1

Works fine while walking in the corridor with this device. No disconnection is seen and connects to the nearest AP with good signal strength.

------------------------------------

Endpoint: Windows 10 Laptop

No disconnection seen.

------------------------------------

I will test with a Macbook and post results soon.

This test shows that only one type of endpoint is showing unexpected behavior. Wonder what has changed?

[Leo Laohoo]

If the problematic client is an Android, then download the app WiFi Roaming Fix and see if it makes any difference.

[ksohan4730]

This this get sorted out?