Wireless Access

The 6.3x user guide states the following:

"When client match is enabled on 802.11ncapable

access points, the client match feature overrides any settings configured for the legacy bandsteering, station
handoff assist or load balancing features."

Does this include the  local probe request threshold in the SSID profile?

Is there a doc somehwere that lays out exactly what is enabled when you turn on client match? 

---

@jclingan wrote:

The 6.3x user guide states the following:

 

"When client match is enabled on 802.11ncapable

access points, the client match feature overrides any settings configured for the legacy bandsteering, station
handoff assist or load balancing features."

 

Does this include the  local probe request threshold in the SSID profile?

 

Is there a doc somehwere that lays out exactly what is enabled when you turn on client match? 

 

---

The local probe request threshold parameter is honored, even if you have client match enabled.  There is nothing that says exactly what is enabled besides the statement above.  Maybe that statement should be more succint.

Ok thanks. I did find this article https://arubanetworkskb.secure.force.com/pkb/articles/HowTo/Client-Match-configuration-related-to-Sticky-Clients-AOS-6-3-and-above

So that doc states:

• Client Match Sticky client check SNR (dB) - If client's SNR drops below 25, then controller will search for a better candidate AP. Default is 25.

But that is configured in the ARM profile, not SSID. So I would think you would want both the local probe request threshold = client match stick SNR? 

---

@jclingan wrote:

Ok thanks. I did find this article https://arubanetworkskb.secure.force.com/pkb/articles/HowTo/Client-Match-configuration-related-to-Sticky-Clients-AOS-6-3-and-above

 

So that doc states:

 

• Client Match Sticky client check SNR (dB) - If client's SNR drops below 25, then controller will search for a better candidate AP. Default is 25.

But that is configured in the ARM profile, not SSID. So I would think you would want both the local probe request threshold = client match stick SNR? 

---

I would turn on ClientMatch by itself and leave everything else to the defaults.  If the client's SNR drops below 25, the controller will search for a better candidate, but it must be at least 10 better than the one it is connected to by default.  Configuring local-probe request threshold adds complexity to this and should be left at zero.

We're an all wireless office running MS Lync and enabled a local probe threshold of 25.  We were advised to do this by an Aruba corp engineer we had on site recently.  The suggestion may have been based on our specific environment so I wouldn't necessarily advise anyone else do this unless instructed to.  That being said, we haven't noticed any issues - yet.

ClientMatch overrides the following :

- Band Sterring

- Spectrum Loadbalancing

(HOME-MASTER-CONTROLLER) #show rf arm-profile HOME-ARM-11a-PROFILE

Adaptive Radio Management (ARM) profile "HOME-ARM-11a-PROFILE"
--------------------------------------------------------------------
Parameter                                                                    Value
---------                                                                    -----
Assignment                                                                   single-band
Allowed bands for 40MHz channels                                             a-only
80MHz support                                                                Enabled
Client Aware                                                                 Enabled
Max Tx EIRP                                                                  15 dBm
Min Tx EIRP                                                                  9 dBm
Rogue AP Aware                                                               Disabled
Scan Interval                                                                10 sec
Aggressive scanning                                                          true
Active Scan                                                                  Disabled
ARM Over the Air Updates                                                     Enabled
Scanning                                                                     Enabled
Multi Band Scan                                                              Enabled
VoIP Aware Scan                                                              Enabled
Power Save Aware Scan                                                        Disabled
Video Aware Scan                                                             Enabled
Ideal Coverage Index                                                         10
Acceptable Coverage Index                                                    4
Free Channel Index                                                           25
Backoff Time                                                                 240 sec
Error Rate Threshold                                                         50 %
Error Rate Wait Time                                                         30 sec
Channel Quality Aware Arm                                                    Disabled
Channel Quality Threshold                                                    70 %
Channel Quality Wait Time                                                    120 sec
Minimum Scan Time                                                            8
Load aware Scan Threshold                                                    1250000 Bps
Mode Aware Arm                                                               Disabled
Scan Mode                                                                    all-reg-domain
Cellular handoff assist                                                      Disabled
Client Match                                                                 Enabled
Client Match report interval (sec)                                           30
Allows Client Match to automatically clear unsteerable clients after ageout  Enabled
Client Match Unsteerable Client Ageout Interval                              2 0
Client Match Sticky Client Check Interval (sec)                              3
Client Match Sticky client check SNR (dB)                                    25
Client Match SNR threshold(dB)                                               10
Client Match Sticky Min Signal                                               70
Client Match Restriction timeout (sec)                                       10
Client Match Load Balancing threshold (%)                                    20
Client Match VBR Stale Entry Age (sec)                                       120
Client Match Max steer failures                                              3
Client Match Load Balancing client threshold                                 10
Client Match Load Balancing SNR threshold (dB)                               30

You can adjust some of the ClientMatch thresholds

SNR

Load balance

And the Max signal you want your devices to get steer to another AP

Another thing to note is that the sticky client functionality of client match helps clients roam/move to better AP's, whereas the local-probe threshold feature makes sure that the AP does not encourage clients to connect with probe requests below SNR of the configured value.  Client match is configured in the ARM profile, and so is applied to the radio - regardless of SSID.

I agree that the recommendation is to leave local probe threshold in SSID profile as 0 (disabled) unless suggested by TAC based on deployment/need.