rf arm-profile default-6ghz

rf arm-profile default-6ghz

160MHz support {Auto|Contiguous-only|Non-contiguous-only|None}

40MHz-allowed-bands {2.4GHz-and-5GHz|2.4GHz-and-6GHz|5GHz-and-6GHz|6GHz-only|a-only|All|g-only|none}

80MHz support

acceptable-coverage-index <acceptable-coverage-index>

active-scan

aggressive-scan

assignment {disable|maintain|multi-band|single-band}

backoff-time <backoff-time>

channel-quality-aware-arm

channel-quality-threshold <channel-quality-threshold>

channel-quality-wait-time <channel-quality-wait-time>

client-aware

client-match

clone

cm-6ghz-band-steer

cm-band-a-min-signal <cm-band-a-min-signal>

cm-band-g-min-signal <cm-band-g-min-signal>

cm-dot11v

cm-he-min-signal <cm-he-min-signal>

cm-he-pooling-signal-delta <cm-he-pooling-signal-delta>

cm-he-pooling-snr-thresh <cm-he-pooling-snr-thresh>

cm-lb-client-thresh <cm-lb-client-thresh>

cm-lb-interval <cm-lb-interval>

cm-lb-signal-delta <cm-lb-signal-delta>

cm-lb-snr-thresh <cm-lb-snr-thresh>

cm-lb-thresh <cm-lb-thresh>

cm-max-steer-fails <cm-max-steer-fails>

cm-mu-client-thresh <cm-mu-client-thresh>

cm-mu-snr-thresh <cm-mu-snr-thresh>

cm-report-interval <cm-report-interval>

cm-stale-age <cm-stale-age>

cm-steer-backoff <cm-steer-backoff>

cm-steer-timeout <cm-steer-timeout>

cm-sticky-check-interval <cm-sticky-check-interval>

cm-sticky-min-signal <cm-sticky-min-signal>

cm-sticky-snr <cm-sticky-snr>

cm-sticky-snr-delta <cm-sticky-snr-delta>

cm-unst-ageout

cm-unst-ageout-intvl days <days> hours <hours>

dynamic-bw

dynamic-bw-beacon-failed-thresh <dynamic-bw-beacon-failed-thresh>

dynamic-bw-cca-ibss-thresh <dynamic-bw-cca-ibss-thresh>

dynamic-bw-cca-intf-thresh <dynamic-bw-cca-intf-thresh>

dynamic-bw-clear-time <dynamic-bw-clear-time>

dynamic-bw-wait-time <dynamic-bw-wait-time>

error-rate-threshold <error-rate-threshold>

error-rate-wait-time <error-rate-wait-time>

free-channel-index <free-channel-index>

gateway

geolocation

gsm

guest-access-email

ideal-coverage-index <ideal-coverage-index>

interfering-ap-weight <interfering-ap-weight>

load-aware-scan-threshold <load-aware-scan-threshold>

max-tx-power {12|127|15|18|21|24||27|3|30|33|6|9}

min-scan-time <min-scan-time>

min-tx-power {12|127|15|18|21|24||27|3|30|33|6|9}

mode-aware

multi-band-scan

no

ota-updates

ps-aware-scan

rogue-ap-aware

scan-interval <scan-interval>

scan mode {all-reg-domain|reg-domain

scanning

telnet {cli|soe}

threshold {controlpath-cpu|controlpath-memory|datapath-cpu|no-of-APs|no-of-locals|no-of-VAPs|total-tunnel-capacity|user-capacity}

time-range {absolute|periodic}

time-range-profile <profile-name>

traceoptions

tunnel-group <tungrpname>

tunnel-loop-prevention

tunnel-node-mtu <tnode-mtu>

tunneled-node-address <tnode-ip-address>

ucc {custom-sip|facetime|h323|ich|jabber|noe|rtpa-config|sccp|session-idle-timeout|sip|skype4b|teams|vocera|webrtc|wificalling}

upgrade-profile

uplink {cellular|health-check|load-balance|wired}

user-role <string>

video-aware-scan

voip-aware-scan

voip-aware-scan-timer

web-cc global-bandwidth-contract {web-cc-category <string>|web-cc-reputation {high-risk {downstream|upstream}|low-risk {downstream|upstream}|moderate-risk{downstream|upstream}|suspicious {downstream|upstream}|trustworthy {downstream|upstream}}}

web-proxy server <name>

web-server profile

webcc {connectiontype|distributed}

websocket clearpass

wlan {}

Description

This command configures the Adaptive Radio Management (ARM) default-6 GHz profile. Adaptive Radio Management (ARM) is a radio frequency (RF) resource allocation algorithm that allows each AP to determine the optimum channel selection and transmit power setting to minimize interference and maximize coverage and throughput. This command configures an ARM profile that you apply to a default-6 GHz radio profile.

Parameter

Description

160MHz support

Auto

Contiguous-only

Non-contiguous-only

None

Specifies which 160 MHz mode is assigned. Does not apply to the 2.4 GHz radio.

Default: None

40MHz-allowed-bands

2.4GHz-and-5GHz

2.4GHz-and-6GHz

5GHz-and-6GHz

6GHz-only

a-only

All

g-only

none

Specifies on which bands (802.11a or 802.11g) the 40 MHz channels may be used:

  • 2.4GHz-and-5GHz: Allows the use of the 40 MHz channels on both 2.4 GHz and 5 GHZ frequency band only.
  • 2.4GHz-and-6GHz: Allows the use of the 40 MHz channels on both 2.4 GHz and 6 GHZ frequency band only.
  • 5GHz-and-6GHz: Allows the use of the 40 MHz channels on both 5 GHz and 6 GHZ frequency band only.
  • 6GHz: Allows the use of the 40 MHz channels on the 6 GHZ frequency band only.
  • A-only: Allows the use of the 40 MHz channels on the 5 GHZ (802.11a) frequency band only.
  • All: Allows the 40 MHz channels on both the 5 GHZ (802.11a) and 2.4 GHZ (802.11b/g) frequency bands.
  • G-only: Allows the use of the 40 MHz channels on the 2.4 GHZ (802.11b/g) frequency band only.
  • None: Disallows the use of the 40 MHz channels

Default: a-only

80MHz support

If enabled, the 80 MHz channels are used on the 5 GHz radio. Does not apply to the 2.4 GHz radio.

Default: Enabled

acceptable-coverage-index

The minimal coverage that the AP should try to achieve on its channel. The denser the AP deployment, the lower this value should be. This setting applies to multi-band implementations only.

active-scan

When active-scan is enabled, an AP initiates active scanning via probe request. This option elicits more information from nearby APs, but also creates additional management traffic on the network. This feature is disabled by default, and should not be enabled except under the direct supervision of HPE Aruba Networking Technical Support.

Default: Disabled

aggressive-scan

If enabled, an AP radio with no clients will scan channels every second.

Default: Enabled

assignment

disable

maintain

multi-band

single-band

Specify one of four ARM channel/power assignment modes:

Disable: Disable ARM channel/power assignments.

Maintain: Maintain existing channel assignments.

Single-band: Compute ARM assignments for a single band.

Multi-band: Compute ARM assignments for both 5 GHZ (802.11a) and 2.4 GHZ (802.11b/g) frequency bands.

Default: Single-band

backoff-time

Time, in seconds, when an AP backs off after requesting a new channel or power.

Range: 120-3600

Default: 240

channel-quality-aware-arm

If enabled, ARM changes are based upon an internally calculated channel quality metric. When this feature is disabled, ARM initiates channel changes based on thresholds defined in this profile, and chooses the channel based on the calculated interference index value.

Default: Disabled

channel-quality-threshold

Channel quality percentage below which ARM initiates a channel change.

Range: 0-100

Default: 70

channel-quality-wait-time

If channel quality is below the specified channel quality threshold for this wait time period, ARM initiates a channel change.

Range: 1-3600

Default: 120

client-aware

If the Client Aware option is enabled, the AP does not change channels if there is active client traffic on that AP. If Client Aware is disabled, the AP may change to a more optimal channel, but this change may also disrupt current client traffic.

Default: Enabled

client-match

ClientMatch helps optimize network resources by balancing clients across channels, regardless of whether the AP or the controller is responding to the wireless client’s probe requests.

If enabled, the controller compares whether or not an AP has more clients than its neighboring APs on other channels. If an AP’s client load is at or over a predetermined threshold as compared to its immediate neighbors, or if a neighboring HPE Aruba Networking AP on another channel does not have any clients, load balancing will be enabled on that AP.

clone

Name of an existing ARM profile from which parameter values are copied.

cm-6ghz-band-steer

Enable Client Match band steers to the 6 GHz radio.

cm-band-a-min-signal

Minimum signal level required for the targeted A band radio in a Client Match band steer move (-dBm).

Range: 0-255 dbm

Default: 75

cm-band-g-max-signal

Maximum signal level of the G band radio that can trigger a Client Match band steer move (-dBm)

Range: 0-255 dbm

Default: 45

cm-dot11v

Client Match steers using 802.11v BSS Transition Management.

Default: Enabled

cm-he-min-signal

Minimum signal required for the targeted HE move (-dbm).

Range: 0-255 dbm

Default: 55

cm-he-pooling-signal-delta

Target radio should not have weaker signal strength than current source radio by the configured value.

cm-he-pooling-snr-thresh

Client match HE pooling SNR threshold (dB) at target radio

cm-lb-client-thresh

If an AP radio has fewer clients than the client match load balancing threshold defined by this parameter, the AP will not participate in load balancing.

Range: 0-100

Default: 30

cm-lb-interval

Specify, in minutes, how often client load balancing is performed.

Range: 0-255

Default: 5

cm-lb-signal-delta

Client match will not move a client to a new radio if the signal strength of the target AP is this dB value lower than the radio to which the client is currently associated. This parameter works differently than the cm-lb-snr-thresh value, which imposes a definite value on the target AP's signal-to-noise radio. the cm-lb-signal-delta imposes a relative constraint based upon the signal strength of the radio to which the client is currently associated.

Range: 0-20

Default: 5

cm-lb-snr-thresh

Clients must detect a SNR from an underutilized AP radio at or above this threshold before ClientMatch considers load balancing a client to that radio.

Range: 0-100

Default: 25

cm-lb-thresh

Client Match load balancing client distribution threshold between channels, as a percentage of clients.

cm-max-steer-fails

The controller keeps track of the number of times ClientMatch failed to steer a client to a different radio, and the reason that each steer attempt was triggered. If ClientMatch attempts to steer a client to a new radio multiple consecutive times for the same reason but client steering fails each time, the controller notifies the AP to mark the client as unsteerable for that specific trigger.

This parameter defines the maximum allowed number of client match steering fails with the same trigger before the client is marked as unsteerable for that trigger.

Range: 0-100

Default: 5

cm-mu-client-thresh

Total number of clients that can be associated to a radio, in which the radio can still be considered for multi-user (MU) steering.

Range: 0-255

Default: 15

cm-mu-snr-thresh

Minimum SNR value of a client on the target radio, in which the radio can still be considered for multi-user (MU) steering.

Range: 0-255

Default: 30

cm-report-interval

This interval defines how often an AP sends an updated client probe report to the controller. Each client probe report contains a list of MAC addresses for clients that have been active in the last two minutes, and the AP radio SNR values seen by those clients.

Range: 0-255

Default: 30

cm-stale-age

The controller can maintain client match data for the maximum number of supported clients for that controller platform, showing the detected SNR values for up to 16 candidate APs per client. This table is periodically updated as APs send client probe reports to the controller. This parameter defines the amount of time, in seconds, that the controller should retain client match data from each client probe report.

Different controller types support varying numbers of clients.

7005: 1024 client

7010: 2048 clients

7030: 4096 clients

7240: 32000 clients

7220: 24000 clients

7210: 16000 clients

Range: 0-65535

Default: 120 seconds

cm-steer-backoff

Client Match will attempt one IOS steer at the configured backoff time interval.

cm-steer-timeout

When a client is steered from one AP to a more desirable AP, the steer timeout feature helps facilitate the move by defining the amount of time that any APs to which the client should NOT associate will not respond to the AP.

Range: 0-255

cm-sticky-check-interval

Frequency at which the AP checks for client's received SNR values. If the SNR value drops below the threshold defined by the cm-sticky-snr parameter for three consecutive check intervals, that client may be moved to an different AP.

Range: 0-255

Default: 3

cm-sticky-min-signal

A client triggered to move to a different AP may consider an AP radio a better match if the client detects that the signal from the candidate AP radio is at or higher than the minimum signal level defined by this parameterand the candidate radio has a higher signal strength than the radio to which the client is currently associated. (The required improvement in signal strength can be defined using the cm-sticky-snr-delta command.)

Range: 0-255

Default: 65

cm-sticky-snr

If the client's received signal strength indicator (RSSI) is above this signal-to-noise ratio (SNR) threshold, that client will be allowed to stay associated to its current AP. If the client's received signal strength is below this threshold, it may be moved to a different AP.

Range: 0-255

cm-sticky-snr-delta

A client triggered to move to a different AP may consider an AP radio a better match if the client detects that the signal from the AP radio is stronger than its current radio by the dB level defined by the cm-sticky-snr-thresh parameter, and the candidate radio also has a minimum signal level defined by the cm-sticky-min-signal parameter.

Range: 0-100

Default: 10

cm-unst-ageout-intvl days

The client entries in an unsteerable client list remain in effect for the interval, in days and hours, defined by this parameter before they age out.

Range: 2

cm-unst-ageout

When client match and the client match unsteerable client ageout feature are enabled, the controller periodically sends APs that are not a desired AP match for a client in a list of unsteerable clients. These lists contain a list of MAC addresses for up to 128 clients that should not be steered to that AP.

The following controller types support a aggregate maximum of unsteerable clients for all APs associated to that controller.

7005: 256 unsteerable clients

7010: 512 unsteerable clients

7030: 1024 unsteerable clients

7240: 8000 unsteerable clients

7220: 6000 unsteerable clients

7210: 4000 unsteerable clients

dynamic-bw

Issue the dynamic-bw parameter to enable the ARM dynamic bandwidth switch feature. When enabled ARM can detect 20 MHz interferers that can impact an AP radio using an 80 MHz channel and move the AP radio to another 80 MHz channel. For more information, see rf arm-profile default-6ghz on page 1

Default: Default: Disabled

dynamic-bw-beacon-failed-thresh

The ARM dynamic bandwidth switch feature may trigger a change in the radio channel bandwidth if the number of failed beacons exceeds this value during the observation window.

Range: 1-500

Default: 30

dynamic-bw-cca-ibss-thresh

The ARM dynamic bandwidth switch feature may trigger a change in the radio channel bandwidth if the clear channel assignment IBSS percentage drops below this value during the observation window.

Range: 1-100

Default: 10

dynamic-bw-cca-intf-thresh

The ARM dynamic bandwidth switch feature may trigger a change in the radio channel bandwidth if the clear channel assignment interference percentage exceeds this value during the observation window.

Range: 1-100

Default: 30

dynamic-bw-clear-time

The ARM dynamic bandwidth switch feature returns the AP radio to 80 MHz channel after this clear time period , in seconds, if there is no high volume of traffic.

Range: 1-300

Default: 30

dynamic-bw-wait-time

Minimum time in seconds dynamic bandwidth switch indicators have to be true to trigger a 80 MHz to 40MHz bandwidth change.

Range: 1-300

Default: 30

error-rate-threshold

The percentage of errors in the channel that triggers a channel change. Recommended value is 50%. A value of 0% disables this feature.

Range: 0-100

Default: 70

error-rate-wait-time

Time, in seconds, that the error rate has to be at least the error rate threshold to trigger a channel change.

Recommended values are 1-100.

Default: 90

free-channel-index

The difference in the interference index between the new channel and current channel must exceed this value for the AP to move to a new channel. The higher this value, the lower the chance an AP will move to the new channel.

Range: 0-100

Default: 40

gateway

Specify the default gateway to use.

geolocation

Specify the geographical location of the device.

gsm

Specify the GSM related tracing.

guest-access-email

Specify the guest-access email profile.

ideal-coverage-index

The coverage that the AP should try to achieve on its channel. The denser the AP deployment, the lower this value should be. Recommended value is 10.

Range: 2-20

Default: 6

interfering-ap-weight

The weight of the interfering APs in interference index calculation.

Range: 0-100

Default: 25

load-aware-scan-threshold

Load aware ARM preserves network resources during periods of high traffic by temporarily halting ARM scanning if the load for the AP gets too high.

The Load Aware Scan Threshold is the traffic throughput level an AP must reach before it stops scanning. The supported range for this setting is 0-20000000 bytes/second. (Specify 0 to disable this feature.)

Range: 1250000 bytes/second

max-tx-power

Maximum effective isotropic radiated power (EIRP) from 3 to 33 dBm in 3 dBm increments. You may also specify a special value of 127 dBm for regulatory maximum to disable power adjustments for environments such as outdoor mesh links. This value takes into account both radio transmit power and antenna gain.

Higher power level settings may be constrained by local regulatory requirements and AP capabilities.

Range: 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 127

Default: 18

min-scan-time

Minimum number of times a channel must be scanned before it is considered for assignment. The supported range for this setting is 0-2,147,483,647 scans. Best practices are to configure Minimum Scan Time between 1-20 scans.

Range: 1-20.

Default: 8

min-tx-power

Minimum effective isotropic radiated power (EIRP) from 3 to 33 dBm in 3 dBm increments. You may also specify a special value of 127 dBm for regulatory minimum. This value takes into account both radio transmit power and antenna gain. Higher power level settings may be constrained by local regulatory requirements and AP capabilities.

Range: 3, 6, 9, 12, 15, 18, 21, 24, 27, 30, 33, 127

Default: 12

mode-aware

If enabled, ARM will turn APs into Air Monitors (AMs) if it detects higher coverage levels than necessary. This helps avoid higher levels of interference on the WLAN. Although this setting is disabled by default, you may want to enable this feature if your APs are deployed in close proximity (e.g. less than 60 feet apart).

Default: Disabled

multi-band-scan

When enabled, single-radio APs try to scan across bands for rogue AP detection.

Default: Enabled

no

Negates any configured parameter.

ota-updates

The ota-updates option allows an AP to get information about its RF environment from its neighbors, even the AP cannot scan. If this feature is enabled, when an AP on the network scans a foreign (non-home) channel, it sends other APs an Over-the-Air (OTA) update in an 802.11 management frame that contains information about the scanning AP's home channel, the current transmission EIRP value of its home channel, and one-hop neighbors seen by that AP.

Default: Enabled

ps-aware-scan

When enabled, the AP will not scan if Power Save is active.

Default: Disabled

rogue-ap-aware

When enabled, the AP will try to contain off-channel rogue APs.

Default: Disabled

scan-interval

If scanning is enabled, the scan interval defines how often the AP will leave its current channel to scan other channels in the band. Off-channel scanning can impact client performance. Typically, the shorter the scan interval, the higher the impact on performance. If you are deploying a large number of new APs on the network, you may want to lower the Scan Interval to help those APs find their optimal settings more quickly. Raise the Scan Interval back to its default setting after the APs are functioning as desired.

Range: 0-30

Default: 10

scan-mode

Select the scan mode for the AP:

all-reg-domain: The AP scans channels within all regulatory domains. This is the default setting.

reg-domain:Limit the AP scans to just the regulatory domain for that AP.

Default: Default: All-reg-domain

scanning

The Scanning check box enables or disables AP scanning across multiple channels. Disabling this option also disables the following scanning features:

Multi Band Scan

Rogue AP Aware

Voip Aware Scan

Power Save Scan

Do not disable Scanning unless you want to disable ARM and manually configure AP channel and transmission power.

Default: Enabled

telnet

Enable the telnet port.

threshold

Specify the threshold.

time-range

Specify the time range.

time-range-profile

Specify the time range profile.

traceoptions

Specify the trace options.

tunnel-group

Specify the tunnel group.

tunnel-loop-prevention

Prevent forwarding loops between the tunnels from the tunneled nodes on the managed device.

tunnel-node-mtu

Specify the MTU for the tunneled node.

tunneled-node-address

Specify the IP address of the managed device to terminate the tunnels. An IP address of th 0.0.0.0 disables the configuration.

ucc

Specify the UCC configuration.

upgrade-profile

Specify the upgrade profile.

uplink

Specify the uplink manager configuration.

user-role

Specify the user role.

video-aware-scan

As long as there is at least one video frame every 100 mSec the AP will reject an ARM scanning request. Note that for each radio interface, video frames must be defined in one of two ways:

Classify the frame as video traffic via a session ACL.

Enable WMM on the WLAN’s SSID profile and define a specific DSCP value as a video stream. Next, create a session ACL to tag the video traffic with the that DSCP value.

Default: Enabled

voip-aware-scan

HPE Aruba Networking’s VoIP Intelligent Call Handling (ICH) prevents any single AP from becoming congested with voice calls. When you enable ICH, you should also enable voip-aware-scan parameter in the ARM profile, so the AP will not attempt to scan a different channel if one of its clients has an active VoIP call. This option requires that scanning is also enabled.

Default: Disabled

voip-aware-scan-timer

When enabled, the AP will not scan if the scan request falls within the scan timer, in milliseconds, of the last voice frame.

Range: 50-1000

Default: 50

Example

The following command configures VoIP-aware scanning for the arm-profile named “voice-arm:”

(host) [mynode] (config) #rf arm-profile default-6ghz

Command History

Release

Modification

AOS 8.9.0.0

Command introduced.

Command Information

Platforms

License

Command Mode

All platforms

Base operating system.

Config mode on Mobility Conductor.