Controller Based WLANs

 View Only
last person joined: one year ago 

APs, Controllers, VIA
Back to Library

How does client match handle unsteerable clients? 

Jun 26, 2014 06:00 PM

Applicable for 6.2 and above ArubaOS which features ARM 3.0

 

Client Match – Handling unsteerable clients


Controller keeps track of successive steer failures for the respective steer reason 
to the desired destination radio

Upon 5 consecutive failed steer attempts, controller notifies the associated AP 
to mark the client as unsteerable (with reason)

AP will not attempt to steer that client for that specific reason (e.g. if a client is deemed 
non band steerable, the AP can still continue to do a sticky health check rather than 
completely overlooking the client)

Controller logs the client in a unsteerable list that can be read using 
“show ap arm client-match unsupported”

Default Unsteerable client ageout 2880 mins

Example:

(Aruba3600) #show log arm 50 | include 18:46:17:eb:ab:40

Jan 3 14:37:53 :700101:  <DBUG> |stm| |client-mgmt| Tracking unsuccessful failure for client 18:46:17:eb:ab:40 num fails 2 
Jan 3 14:38:21 :700101:  <DBUG> |stm| |client-mgmt| Tracking unsuccessful failure for client 18:46:17:eb:ab:40 num fails 3 
Jan 3 14:38:31 :700101:  <DBUG> |stm| |client-mgmt| AP d8:c7:c8:80:08:40 Adding new vbr_nbr d8:c7:c8:80:08:40 for client 18:46:17:eb:ab:40
Jan 3 14:38:31 :700101:  <DBUG> |stm| |client-mgmt| AP d8:c7:c8:80:08:40 Adding new vbr_nbr d8:c7:c8:80:08:50 for client 18:46:17:eb:ab:40 
Jan 3 14:38:33 :700101:  <DBUG> |stm| |client-mgmt| Client Match: Unsteerable STA 18:46:17:eb:ab:40 consec_fails 3, giving up 
Jan 3 14:39:04 :702001:  <DBUG> |AP ap135@10.3.136.245 sapd| |client-mgmt| Unsteerable client 18:46:17:eb:ab:40 Reason: Band steer 
Jan 3 14:39:07 :702001:  <DBUG> |AP ap135@10.3.136.245 sapd| |client-mgmt| Unsteerable client 18:46:17:eb:ab:40 Reason: Band steer

 

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Related Entries and Links

No Related Resource entered.