Question: How does ClientMatch handle unsteerable clients?
Controller keeps track of successive steer failures for the respective steer reasonto the desired destination radioUpon 5 consecutive failed steer attempts, controller notifies the associated APto 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 deemednon band steerable, the AP can still continue to do a sticky health check rather thancompletely 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 minsExample:Enable debugging for the client:#logging level debugging arm-user-debug <client-mac>To Show the logs:(Aruba3600) #show log arm 50 | include 18:46:17:eb:ab:40Jan 3 14:37:53 :700101: <DBUG> |stm| |client-mgmt| Tracking unsuccessful failure for client 18:46:17:eb:ab:40 num fails 2Jan 3 14:38:21 :700101: <DBUG> |stm| |client-mgmt| Tracking unsuccessful failure for client 18:46:17:eb:ab:40 num fails 3Jan 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:40Jan 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:40Jan 3 14:38:33 :700101: <DBUG> |stm| |client-mgmt| Client Match: Unsteerable STA 18:46:17:eb:ab:40 consec_fails 3, giving upJan 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 steerJan 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
© Copyright 2024 Hewlett Packard Enterprise Development LPAll Rights Reserved.