Wireless Access

Reply
Highlighted
Occasional Contributor I

Client won't roam with very poor signal

Hi:

I've got ap335,ap225,ap207 and mobility controller 7010 running arubaos 8.6.0.2.

I've enabled client match, and 802.11r/k/v.

But the client just refused to roam, and stuck on the ap.

what should I do to let it roam?

iShot2020-03-0823.51.01.png

Highlighted
New Contributor

Re: Client won't roam with very poor signal

Chop the 1,2 basic rates in the SSID config if there are no legacy devices connecting to the SSIDs for eg. Scanners. This will help in preventing the Sticky Client issue.

 

Highlighted
Guru Elite

Re: Client won't roam with very poor signal

Ultimately the client makes the decision to roam.  Protocols like 802.11v, x,k and Clientmatch just encourage a client if it even supports these protocols.   Many consumer devices are not designed to roam, so they don't.

 

What kind of device is this?  That is the biggest determining factor.


*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Learning Videos
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: