Configuring ClientMatch

Use the following procedures to disable or re-enable ClientMatch, and upload a Rules-Based ClientMatch update package.

Enabling and Disabling ClientMatch

ClientMatch is enabled by default. The procedure to disable and re-enable ClientMatch varies, depending upon whether your deployment consists of multiple managed devices managed by a Mobility Conductor, or whether your APs are all associated to a stand-alone controller.

Mobility Conductor Deployments

The following procedure describes how to enable or disable the 2.4 GHz Gigahertz. and 5 GHz Gigahertz. radio settings for an AP:

  1. In the Managed Network node hierarchy, navigate to the Configuration > AP Groups page.
  2. Select the AP group from the AP Groups table.
  3. Click the Radio tab below the AP Groups table to display the AP radio settings.
  4. Expand the Client Control section.
  5. Click the Client match checkbox to enable or disable both 2.4 GHz Gigahertz. and 5 GHz Gigahertz. radio settings. Click Submit.
  6. Click Pending Changes.
  7. In the Pending Changes window, select the check box and click Deploy changes.

For more information on managing 2.4 GHz Gigahertz. and 5 GHz Gigahertz. radio settings, see 2.4 GHz and 5 GHz Radio RF Management .

Stand-alone Controller Deployments

For stand-alone controllers that do not have any associated managed devices, the ClientMatch feature is enabled and disabled in the ARM Adaptive Radio Management. ARM dynamically monitors and adjusts the network to ensure that all users are allowed ready access. It enables full utilization of the available spectrum to support maximum number of users by intelligently choosing the best RF channel and transmit power for APs in their current RF environment. profile used by the AP, as described in Configuring ARM Profiles. Although default ClientMatch settings are recommended for most users, advanced ClientMatch settings can be configured using rf arm-profile commands in the command-line interface.

6 GHz Radio

ArubaOS supports ClientMatch for 6 GHz Gigahertz. radio. This enables 6 GHz Gigahertz. capable clients to be matched with 6 GHz Gigahertz. radios and also supports spectrum load balancing on the 6 GHz Gigahertz. channels.

Band-Steer: If a client is capable of operating in 6 GHz Gigahertz. and if it is currently associated to a 2.4 GHz Gigahertz. radio, then ClientMatch steers the client to the 6 GHz Gigahertz. radio on the same AP provided the 2.4 GHz Gigahertz. signal is weaker than the configured limit. The cm-6ghz-band-steer configuration parameter in the rf arm-profile command controls if band-steer is allowed. The configuration parameter is enabled by default.

ClientMatch supports band-steer only from 2.4 GHz Gigahertz. to 6 GHz Gigahertz. for the 6 GHz Gigahertz. capable clients and not from 5 GHz Gigahertz. to 6 GHz Gigahertz..

If a 6 GHz Gigahertz. capable client rejects multiple requests to move to 6 GHz Gigahertz. or does not respond to multiple requests, it is marked as unsteerable.

Sticky-Steer: If a client is capable of operating in 6 GHz Gigahertz. but is not in good health, then ClientMatch finds a potential 6 GHz Gigahertz. radio for the client to move and ensures that the new radio is in good health. The existing thresholds for sticky steer work for client capable of operating in 6 GHz Gigahertz..

Spectrum Balance: Periodically, the load balancing algorithms are run to ensure that the clients capable of operating in 6 GHz Gigahertz. are distributed evenly across the available channels. The existing thresholds for spectrum balancing work for the clients capable of operating in 6 GHz Gigahertz..