How to Enable Client Match and Sticky Client Mitigation in Aruba WLAN

Summary

Aruba ClientMatch actively steers clients to the best AP/radio based on signal quality, load, and policy, resolving “sticky client” behavior. In AOS 10, ClientMatch is orchestrated in Aruba Central; in AOS 8, it’s configured per AP Group on the controller. Below are enablement steps, verification, tuning tips, and FAQs.

1) What ClientMatch Does

  • Maintains a per-client candidate list (AP/radio, RSSI/SNR, health) and issues steers when a better radio is available.
  • Sub-features: Sticky steer, Band steer (to 5/6 GHz), Load balancing, MU steer, and voice/HE-related optimizations.

2) Enable on Aruba Central (AOS 10)

In AOS 10, ClientMatch control is in Central; configure at Group/Site scope and monitor via Events.

  1. Go to Aruba Central → Network Operations and pick the Group/Site.
  2. Open Configure → Services (or RF/Radio) → Client Match.
  3. Toggle Enable Client Match; enable sub-features (e.g., Band Steering, Load Balancing, Sticky Mitigation).
  4. Save/Deploy changes.
  5. Validate at Analyze/Monitoring → Alerts & Events; filter for Client Match Steer to see completed/attempted steers.

3) Enable on ArubaOS 8 (Controller)

WebUI (AOS 8.x)

  1. Configuration → AP Groups
  2. Select your AP Group → Radio tab
  3. Expand Client Control
  4. For 2.4 GHz and 5 GHz, set Client-Match = Enable
  5. Submit → Pending Changes → Deploy

Useful CLI (monitoring)

show ap arm client-match summary
# (Some builds) show ap arm client-match summary advanced

Outputs show totals and success ratios by steer type: SM (Sticky), B5G/B6G (Band-steer), LM (Load-balance), MU, VoM (Voice), HE types, including accept/reject reasons.

4) Aruba Instant (IAP) Note

For Aruba Instant, enable ClientMatch/RF options via the Virtual Controller WebUI or Instant CLI per your Instant version’s command reference.

5) Verification & Observability

  • AOS 10 (Central): Use Events (and Client Details) to view Client Match Steer attempts/completions.
  • AOS 8 (Controller): Use show ap arm client-match summary to confirm steers and reasons for rejections.

6) RF Hygiene for Better Sticky-Client Mitigation

  • Prefer 20/40 MHz channels in dense areas; avoid blanket 80 MHz to reduce co-channel contention.
  • Cap AP TX power near client capability (e.g., start around 18 dBm max, 12 dBm min; tune by survey).
  • Favor 5 GHz/6 GHz with band-steer; minimize 2.4 GHz reliance in busy spaces.
  • Design for controlled overlap; excessive power/overlap tends to increase “stickiness”.

7) Quick Checklist

  • AOS 10: Client Match Enabled at Group/Site; sub-features toggled
  • AOS 10: Events filtered for Client Match Steer show activity
  • AOS 8: AP Group → Radio → Client Control → Client-Match: Enable
  • AOS 8: show ap arm client-match summary shows steers/outcomes
  • RF basics applied (channel width, EIRP caps, band preference)

8) AOS 10 vs AOS 8 (At a Glance)

Topic AOS 10 (Central) AOS 8 (Controller)
Orchestration Central-managed Controller/Conductor
Where to enable Configure → Services/RF → Client Match AP Group → Radio → Client Control
Monitoring Analyze/Monitoring → Events → “Client Match Steer” show ap arm client-match summary

9) FAQ

What is a “sticky client”? A device that stays associated to a suboptimal AP even when a better candidate exists; ClientMatch counteracts this by steering.

Does ClientMatch need a client agent? No. When available, 802.11v/kv assist; otherwise deauth-based moves may apply depending on OS/feature.

Why might some clients still stick? Roaming is ultimately the client’s decision. Clean RF design and 5/6 GHz preference help.

10) Troubleshooting Tips

  • No steers visible: Check config scope (Group/Site), deploy status, and Events filter/time window.
  • Many rejects/timeouts: Audit target AP suitability and expected SNR gain; review power/channel plan and min-RSSI.
  • Band-steer conflicts: Prefer ClientMatch as the authority on older code; avoid overlapping legacy steers.

References

  • AOS 10 TechDocs — ClientMatch (Central-orchestrated)
  • AOS 8 Web Help — Configuring ClientMatch
  • CLI: show ap arm client-match summary (+ advanced)
  • Central — Client Match events/monitoring
  • Sticky client background concepts