Controller Based WLANs

Client-Match configuration related to Sticky Clients (AOS 6.3 and above)

by on ‎07-08-2014 02:56 PM
Client-Match configuration related to Sticky Clients (AOS 6.3 and above)
 
Sticky clients are clients that do not try to roam, even if the signal strength from the current AP decreases. This client may experience poor performance as it moves far away from the AP it is stuck to.
 
To handle this, client-match feature set in AOS 6.3 and above code versions, contains an algorithm to deauth clients from an AP, if it has poor signal, and if there is a better AP nearby.
 
In the rf arm profile, following are the parameters related to handling stick clients:
 
  • Client Match - default is Enabled, and needs to be enabled for sticky client algorithms to work.
  • Client Match Sticky Client Check Interval (sec) - How often SNR is checked to see if client is sticky. Default is 3.
  • Client Match Sticky client check SNR (dB) - If client's SNR drops below 25, then controller will search for a better candidate AP. Default is 25.
  • Client Match SNR threshold(dB) - Minimum SNR improvement between current AP and desired target AP for the move. Default is 10.
  • Client Match Sticky Min Signal - Minimum signal level required for target AP. Default is 70.
 
Note: the parameters related to sticky client can only be configured through controller CLI and not from UI.
 
To check if a client has been sent a deauth and has connected to a candidate AP, the following CLI command can be used:
 
Show ap arm client-match history client-mac <client-mac>
 
ARM Client match History
 
------------------------
 
Time of Change       MAC                Reason  From (Radio/AP/Phy/Signal(dBm))                      To (Radio/AP/Phy/Signal(dBm))                 Status (Status/Radio/AP/Phy/Essid/Bssid/Roam Time)
 
--------------       ---                ------  -------------------------------                      -----------------------------                 --------------------------------------------------
 
2014-01-09 12:01:13  b8:e8:56:1f:ec:0c  Sticky  9c:1c:12:80:75:f0/DBST-MeetingRm142-BX0021140/a/-72  9c:1c:12:80:89:10/DBST-Rm126-BX0021293/a/-61  Success/9c:1c:12:80:89:10/DBST-Rm126-BX0021293/a/YRDSB-A/9c:1c:12:80:89:11/4
 
 
 
The differences between client-match sticky client feature versus station handoff-assist feature, are as follows:
 
- Station handoff assist is disabled by default.
- For station handoff assist to work, client-match needs to be disabled.
- Station handoff assist is configured on a per-ap-group basis (instead of per-radio-basis) in the rf optimization profile.
- Station handoff assist does not take into consideration if there is no nearby AP with better signal strength. Even if there are no candidate AP’s, it still sends the client deauth if the SNR drops below 20.

 

Comments
james.heyworth

It is my understanding that only one of these technologies should be used. Is there anyone out there that recommends one over the other? What issues or problems would arise not having at least two enabled? Some clients do not support client-match and need some sort of station/client roaming solution. Has anyone else ran into an issue with running more than one client roaming solution?

Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.