AirMatch

How can I configure AirMatch?

AirMatch can be configured only in Classic Central at this time. The AirMatch service configuration option has not yet been introduced in HPE Aruba Networking Central.

Does AirMatch use client density to compute channel bandwidth?

No. AirMatch does not currently use client density to compute channel bandwidth. It relies on RF conditions and telemetry data from APs to determine optimal bandwidth allocation.

Why does AirMatch assign the same channels to nearby APs?

AirMatch may assign the same channels to adjacent APs due to:

• High AP density, which limits the number of non-overlapping channels available.

• Restricted RF profiles, where the configured channel list is too narrow, reducing flexibility in channel assignment.

Does AirMatch support 320 MHz channel bandwidth in the 6 GHz band?

Yes. AirMatch supports 320 MHz channel bandwidth for the 6 GHz band, provided the feature is enabled in the configuration. This allows for higher throughput in environments where such wide channels are feasible.

Can AirMatch assign non-PSC channels in the 6 GHz band?

Yes. If non-PSC (non-Preferred Scanning Channels) are enabled in the configuration, AirMatch can assign them dynamically. This provides greater flexibility in channel planning, especially in environments with limited PSC availability.

How does AirMatch optimize EIRP across APs?

AirMatch fine-tunes Effective Isotropic Radiated Power (EIRP) levels to ensure consistent coverage and minimize interference. It avoids large power fluctuations between neighboring APs to maintain network stability.