airmatch profile
airmatch profile
he-pooling-client-density
dfs-ch-deploy-interval
deploy-hour <0-23>
no ...
noise-event-period-2g
noise-event-period-5g
quality-threshold
radar-event-period-5g
schedule enable|disable
solver-feas-deploy-threshold
Description
This command configures the AirMatch profile.
The AirMatch channel and EIRP optimization features deprecate the channel planning and EIRP optimization features in the legacy ARM feature. AirMatch is supported onMobility Conductoronly, while legacy ARM channel optimization and EIRP features continue to be supported by stand-alonecontrollersrunningArubaOS8.x.
AirMatch通道规划横通道distributions in any size of network, and in any subset of the contiguous network (as much as allowed by the network configuration, regulatory domain and AP hardware capability). AirMatch also minimizes channel coupling, where adjacent radios are assigned to the same channel. The computing power ofMobility Conductorimpacts channel distribution calculations, so channel coupling may occasionally be allowed in complex networks to keep the computing time practical.
AirMatch EIRP planning automatically considers the local density of the network to manage the APs' coverage and modulation and coding scheme (MCS) operation, and optimizes EIRP changes across neighboring AP radios in order to offer users the best roaming experience.
The AirMatch
setting is different from the ARM setting of or . The ARM setting changes the AP radio channel and EIRP values back to the default values specified in 802.11a and 802.11g radio profiles for that radio. The ARM setting freezes current channel and EIRP settings for that radio. In contrast, the AirMatch option simply means the centralized algorithm will stop selecting a new channel, bandwidth, or EIRP setting; the network operator still can override the previous settings assigned by AirMatch with static channel or EIRP values, and the AP radio can continue to voluntarily change channels to avoid radar interference or high noise levels.AirMatch Channel Assignments
Each AP in aMobility Conductordeployment measures its RF environment for a five minute period, every 30 minutes, by default. The AP then sends AMON messages about the radio feasibility to themanaged devicebased on thehardware capability for the AP, radio and regulatory domain, and RF neighbors. Themanaged deviceforwards these messages to theMobility Conductor. TheMobility Conductoradds this information to a database, computes an optimal solution, and deploys the latest RF plan by sending updated settings to the APs. By default, this configuration update is sent at 5 AM (as per theMobility Conductorsystem clock), but time of this configuration update can be modified via the AirMatch profile.
An exception to this daily update is an automatic channel change due to a radar detection event or high noise interference. If an AP detects a radar event on its current operating channel, that AP automatically changes to another supported channel to avoid radar interference, and does not wait for the daily RF configuration update from theMobility Conductor. An AP may also automatically change channels if a very high noise level is detected on the current channel, if at least one other channel is free of noise.
InArubaOS8.0, AirMatch moves a radio to a random channel when a radar event is detected, or if a high noise floor is detected on a non-static channel. Starting withArubaOS8.0.1, AirMatch uses the criteria described inTable 1, Channel Assignment Logicto assign a new channel.
Issue Prompting Channel Change |
Channel Selection Criteria |
---|---|
Detected radar |
AirMatch selects a channel with a minimum interference index from the channels without high noise or a radar condition. |
High channel noise |
The channel selection criteria varies between static and non-static channels. If static channel is configured, the channel does not change due to a high noise condition. For a non-static channel, AirMatch selects a channel with a minimum interference index from the channels without high noise or a radar condition. |
Channel Quality Improvement Thresholds
ArubaOS8.0.1 introduces the AirMatch channel quality improvement threshold, which allows you to select the minimum channel improvement that can trigger a new scheduled channel solution. The default threshold value is a 15% improvement. If a proposed channel change will not produce an improvement that meets or exceeds this threshold, AirMatch will not trigger a channel change.
EIRP settings are not impacted by the channel quality improvement threshold. A new EIRP plan is deployed at the scheduled deployment hour every day, regardless of channel quality improvement levels.
这个通道质量设置唯一的美联社plies to scheduled updates. If you manually trigger an update using theairmatch runnow
command, AirMatch will deploy the new solution regardless of the level of improvement.
Parameter |
Description |
deploy-hour <0-23> |
Specify a number from 0-23 to select the hour during which AirMatch updates are sent to the APs (in 24-hour format). If themanaged deviceto which the AP is associated is in a different time zone thanMobility Conductor,AirMatch solution will be deployed according to the time zone of themanaged device. If this parameter is set in both the AirMatch profile and the 802.11a radio profile, the setting in the 802.11a radio profile will take precedence. 0-23 5 |
he-pooling-client-density |
Specify a HE pooling client density in percentage to be considered for 802.11ax pooling. Va HE pooling client density of 0 disables HE pooling. 0-100 20 |
dfs-ch-deploy-interval |
Configures the time interval (in minutes) between the deployment of radios assigned to operate on DFS channels. 0,1 0 |
no ... |
Negates any configured parameter |
noise-event-period-2g |
Use this advanced configuration parameter under the supervision ofArubasupport only. |
noise-event-period-5g |
Use this advanced configuration parameter under the supervision ofArubasupport only. |
quality-threshold |
Use the This setting only applies to scheduled updates. If you manually trigger an update using the If scheduled updates are enabled, the new channel plan is deployed on the specified deployment hour only if it is improved by greater than this threshold value. A new EIRP plan is deployed on the deployment hour every day. 0-100 8 |
radar-event-period-5g |
Use this advanced configuration parameter under the supervision ofArubasupport only. |
schedule enabled|disabled |
If the AirMatch schedule updates are changed from the defaultMobility Conductorcontinues to receive RF updates from the APs, but no channel and EIRP changes are executed byMobility Conductorat the scheduled time. setting to ,When AirMatch schedules are disabled, the centralized algorithm stops selecting a new channel, bandwidth, stops EIRP setting. A network operator still can override the previous settings assigned by AirMatch with static channel or EIRP values, and the AP radio can continue to voluntarily change channels to avoid radar interference or high noise levels. enabled |
solver-feas-deploy-threshold |
Use this advanced configuration parameter under the supervision ofArubasupport only. |
Example
To hold the existing AirMatch RF configuration :
(host)[mynode](config)# airmatch profile schedule disabled
To change the time of the daily AirMatch RF updates from the default 5 AM to 2 AM:
(host)[mynode](config)# airmatch profile deploy-hour 2
Related Commands
Command |
Description |
A radio set with the |
|
This command creates a dump of the database used by AirMatch. The dump file can be exported using the |
|
Manually initiate AirMatch RF computations and solution deployment instead of waiting for the next scheduled update period. |
|
This command displays the configuration settings in the AirMatch profile. |
Command History
Release |
Modification |
ArubaOS8.10.0.0 |
Thedfs-ch-deploy-intervalparameter was introduced. |
ArubaOS8.7.0.0 |
The |
ArubaOS8.2.1.0 |
The default value of the |
ArubaOS8.1.0.0 |
The |
ArubaOS8.0.1.0 |
The |
ArubaOS8.0.0.0 |
This command was introduced. |
Command Information
Platforms |
License |
Command Mode |
All platforms |
Base operating system. |
Configuration mode onMobility Conductor. |