How does the Aruba controller determine if a client is a sticky client and needs to be steered to a different AP?

Aruba Employee
Aruba Employee

This article applies to all the controllers running AOS version and above.


This article explains the parameter called “Sticky Client Trigger” that is a part of Client Match feature introduced in ARM 3.0 in AOS version
As soon as ARM sees the sticky client trigger, it tried to steer the client to another Access Point that is in a better position to serve the client and has a better SNR.
Here is a flow diagram explaining the sticky client algorithm followed by the controller:



Version history
Revision #:
2 of 2
Last update:
‎07-01-2014 04:04 AM
Updated by:
Labels (1)
Search Airheads
Showing results for 
Search instead for 
Did you mean: