We have a very stock client-match config. However, investigating a handful of performance complaints I noticed that client-match is aggressively trying (and mostly failing) to push users to either 5ghz or to another AP. The best commands I've found to investigate this are:
show ap arm client-match summary
show ap arm client-match history client-mac <mac-address>
I had to run
clear ap arm client-match summary
as it seems like the counters are never reset so I had data from years ago.
For example:
Client Match Summary
---------------------
MAC SM (T/S) LM (T/S) BM (T/S) MU (T/S) VoM (T/S) Moves (T/S) Last Move (Time/Rsn/Dur)) Device Type 11v Moves
--- -------- -------- -------- -------- --------- ----------- ------------------------- ----------- ---------
e4:2b:34:94:c6:e6 15/0 0/0 27/4 0/0 0/0 42/4 Aug 25 12:54:35 2020/Sticky/X iPhone 41/11/1/0/0/0/0/15/1/0/13/0
In the last ~20hrs Aruba tried to push this iPhone to a new AP 15 times and tried to push it to 5ghz 27 times and only succeeded 4 times. The last 5 times were all within 10mins of each other.
As I understand how all this active handling works is the AP actually disassociates the client from the AP to try to convince it to move (to either the new frequency or new AP). Such an aggressive and repetitive model for client-match *has* to be having a negative effect on clients.
Does anyone else see something similar? Does anyone think I'm missing something and it's not a problem?