Aruba IAP-335 User Manual page 256

When the client match feature is enabled on an IAP, the IAP measures the RF health of its associated clients. In
the current release, the client match feature is supported only within an IAP cluster. If any of the following
trigger conditions is met, clients are moved from one IAP to another for better performance and client
experience:
Dynamic Load Balancing—Client match balances clients across IAPs on different channels, based on the
l
client load on the IAPs and the signal to noise ration (SNR) levels the client detects from an underutilized
IAP. If an IAP radio can support additional clients, the IAP will participate in client match load balancing and
clients can be directed to that IAP radio, subject to the predefined SNR thresholds. For better load
balancing, clients are steered from busy channels to idle channels.
Sticky Clients—The client match feature also helps mobile clients that tend to stay associated to an IAP
l
despite low signal levels. IAPs using client match continually monitor the client's RSSI as the client roams
between IAPs, and move the client to an IAP when a better radio match can be found. This prevents mobile
clients from remaining associated to the IAPs with less than ideal RSSI, which can cause poor connectivity
and reduce performance for other clients associated with that IAP.
Band Steering—IAPs using the client match feature monitor the RSSI for clients that advertise a dual-band
l
capability. If a client is currently associated to a 2.4 GHz radio and the IAP detects that the client has a good
RSSI from the 5 GHz radio, the IAP steers the client to the 5 GHz radio, as long as the 5 GHz RSSI is not
significantly worse than the 2.4 GHz RSSI, and the IAP retains a suitable distribution of clients on each of its
radios.
Channel Utilization—Based on the percentage of channel utilization, clients are steered from a busy channel
l
to an idle channel.
Client Capability Match—Based on the client capability match, clients are steered to appropriate channel, for
l
example, HT20, HT40, or VHT80.
Starting from the Instant 6.3.1.1-4.0 release, spectrum load balancing is integrated with the client match
feature. Client match allows the IAPs in a cluster to be divided into several logical IAP RF neighborhood called
domains, which share the same clients. The VC determines the distribution of clients and balances client load
across channels, regardless of whether the IAP is responding to the probe requests of wireless clients.
You can configure client match parameters in the Instant UI or the CLI. When client match is enabled, the
dashboard in the main window displays the Client Match link on selecting an IAP in the Access Points tab or
a client in the Clients tab. Clicking this link provides a graphical representation of radio map view of an IAP and
the client distribution on an IAP radio. For more information, see
In the Instant UI
1. For client match configuration, specify the following parameters in the RF > ARM > Show advanced
options tab:
256 | Adaptive Radio Management
Client Match on page 51.
Aruba Instant 6.5.0.0-4.3.0.0 | User Guide