Details on client match feature IAP 4.0:-
------------------------------------------------
• Problem:
– Similar to AOS, IAP clients could experience connectivity and performance issues due to stickiness, improper band usage, and improper load balancing
• Challenge:
– IAP must solve this problem without depending on any external, centralized data structure, and we cannot burden the VC
• Solution:
– A distributed algorithm that group APs into RF-neighborhoods and co-decide which AP should service which clients
How does client-match works;-
--------------------------------------------
- • Only the client’s associated AP attempts to match the client to a better AP
- • Only other APs identified to be in the same RF neighborhood can become a candidate target AP for client match
- • Once associated AP finds a better AP for a client, it will send to all neighboring APs an adoption request that identifies the matched AP
- • Once an AP receives such a request, it will send a reply if it can hear that client
- • Only after all APs have replied would the associated AP deauth the client
- • To other APs, only the matched AP would allow the client to associate
- • The originally associated AP would allow the client to associate back if the client makes more than 8 attempts in 10 seconds
- • After a successful client match event, the new AP will not attempt to re-match the client for 15 minutes
Propagation:-
----------------
- Probe request
- Vendor_IE
- ARUBA_OUI_VERSION
- ARUBA_OUI_TYPE_SLB
- Density map, channel, client count, vckey, channel utilization
Comparison:-
------------------
Compare each byte in density map
If similarity > nb_matching, the two APs are in same RF neighborhood
— Click the “RF” link, enable/disable Client Match in default page.
— Click “advanced” to configure Client Match parameters
— In “RF” page, Band Steering can still be configured separately
From WEBUI:-
------------------
From CLI;-
------------
arm
…
…
…
…
scanning
client-match
client-match nb-matching 75
client-match calc-threshold 2
client-match calc-interval 30
client-match slb-mode 1
arm
(no) client-match calc-interval Calculating Interval for SLB
(no) client-match calc-threshold Calculating Threshold for SLB
(no) client-match nb-matching Neighbor matching percentage for SLB
(no) client-match slb-mode Three Balancing strategies: channel, AP, channel+AP
And there are two advanced commands which are not exposed in the UI
(no) client-match max-adoption Max simultaneous client match adoption count
(no) client-match max-request Max simultaneous client match request count
The default value of these two commands are “5”, the range of the values is from “0” to “100”. The value “0” means “no limit”.
When the Client Match is disabled, lots of clients connect to one IAP.
After enabling Client Match for about 5 minutes, the clients connect to the IAPs evenly.
Debugging:-
------------------
d8:c7:c8:cb:d4:28# show ap debug client-match 0
Client Match Status:: RUNNING
Associated:12, Threshold:13
Leaving:0, Coming:0
d8:c7:c8:cb:d4:28# show ap debug client-match 1
Client Match Status:: RUNNING
Associated:0, Threshold:MAX
Leaving:0, Coming:0
d8:c7:c8:cb:d4:28#
d8:c7:c8:cb:d4:28# show ap client-view
Client Match Neighbor Table
---------------------------
MAC Channel RSSI Clients Threshold Channel Util (%) VC Key Flags Received
--- ------- ---- ------- --------- ---------------- ------ ----- --------
d8:c7:c8:5e:d0:a8 157+ 12 0 0 1 e41fcd44 B 10m:20s
00:0b:86:c3:00:00 0- 0 0 - - - VR 18s
6c:f3:7f:c5:a1:e0 1+ 9 0 2 61 e41fcd44 S 5m:42s
d8:c7:c8:5e:d1:e8 157+ 9 0 0 33 e41fcd44 B 9m:57s
6c:f3:7f:c5:a1:f8 157+ 9 61 0 27 e41fcd44 B 8m:24s
d8:c7:c8:14:1e:28 157+ 9 0 0 0 e41fcd44 B 11m:0s
Neighbor Flags: V - Valid; R - In RF Neighborhood; S - Same Channel;
B - Balancing; C - Client Match Enabled; I - In Same Swarm
Total 109 Neighbors
d8:c7:c8:cb:d4:28# show ap client-view | include I
MAC Channel RSSI Clients Threshold Channel Util (%) VC Key Flags Received
6c:f3:7f:ef:19:00 1 61 0 0 3 40e162eb VRICSB 1s
6c:f3:7f:ef:19:10 161 97 11 11 3 40e162eb VRICB 1s
Neighbor Flags: V - Valid; R - In RF Neighborhood; S - Same Channel;
B - Balancing; C - Client Match Enabled; I - In Same Swarm
d8:c7:c8:cb:d4:28# show ap virtual-beacon-report
Virtual Beacon Table
--------------------
Station CM State Triggered Succeeded Owner AP RSSI Received
------- -------- --------- --------- ----- -- ---- --------
02:10:00:00:00:21 Normal 1 1 No d8:c7:c8:3d:42:90 (Local 0) 43 29s
Normal No d8:c7:c8:3d:42:80 (Local 1) 58 1m:7s
No 6c:f3:7f:ef:19:00 49 13s
Yes 6c:f3:7f:ef:19:10 30 6s
02:20:00:00:00:12 Normal 1 1 No d8:c7:c8:3d:42:90 (Local 0) 49 17s
Normal No d8:c7:c8:3d:42:80 (Local 1) 51 33s
Yes 6c:f3:7f:ef:19:10 46 14s
No 6c:f3:7f:ef:19:00 49 13s
...
...
...
0a:17:00:00:00:03 Failed 1 0 Yes d8:c7:c8:3d:42:90 (Local 0) 51 0s
No 6c:f3:7f:ef:19:10 53 6s
Normal Working well
Home Current AP found a better AP for the client
Deny Current AP is not the better AP
Target Current AP is the better AP
Voice Ready to move, but client is doing voice
Refused Too many clients try to move to me
Done Current AP just deauth the client
Adopted Client has moved to me successfully
Total 20 VBRs
d8:c7:c8:cb:d4:28# show ap client-match-live
Client Match Table
------------------
Station CM State RSSI Radio Home AP Target AP Time
------- -------- ---- ----- ------- --------- ----
02:16:00:00:00:09 Adopted 46 0 - - 7m:43s
98:fe:94:b0:4b:01 Adopted 50 0 - - 7m:35s
…
02:18:00:00:00:21 Failed 52 0 - 6c:f3:7f:ef:19:10 6m:52s
Total 6 Client Matches
d8:c7:c8:cb:d4:28# show ap client-match-history
Client Match Action Table
-------------------------
Station Old State New State Reason Radio Time
------- --------- --------- ------ ----- ----
98:fe:94:b6:82:7d Normal Target I am the better AP 0 28m:44s
…
02:18:00:00:00:21 Deny Normal State aged out 1 7m:25s
Total 150 Records
d8:c7:c8:cb:d4:28# show ap client-match-history client-mac 02:25:00:00:00:01
Client Match History for 02:25:00:00:00:01
------------------------------------------
Old State New State Reason Radio Time
--------- --------- ------ ----- ----
Normal Refused Too many clients are coming to me 0 35m:48s
Refused Normal Client match failed 0 35m:34s
Normal Refused Too many clients are coming to me 0 17m:1s
Normal Deny I am not the better AP 1 17m:1s
Refused Normal Client match failed 0 16m:47s
Deny Normal Client match failed 1 16m:47s
Total 6 Records
d8:c7:c8:cb:d4:28# show ap client-probe-report
AP Client Probe Report for Wifi0
--------------------------------
MAC RSSI In Swarm Received
--- ---- -------- --------
60:67:20:41:0d:10 45 No 47s
...
84:85:06:b6:1e:ad 51 No 4m:37s
b8:e8:56:01:bb:5e 50 No 2m:45s
Total 81 Stations