ap mesh-ht-ssid-profile
ap mesh-ht-ssid-profile {default | <profile-name>}
40MHz-enable
80MHz-enable
ba-amsdu-enable
clone {default | <source>}
high-efficiency-enable
high-throughput-enable
ldpc
legacy-stations
max-rx-a-mpdu-size {8191 | 16383 | 32767 | 65535}
max-tx-a-mpdu-size <max-tx-a-mpdu-size>
max-tx-a-msdu-count-be <max-tx-a-msdu-count-be>
max-tx-a-msdu-count-bk <max-tx-a-msdu-count-bk>
max-tx-a-msdu-count-vi <max-tx-a-msdu-count-vi>
max-tx-a-msdu-count-vo <max-tx-a-msdu-count-vo>
max-vht-mpdu-size {3895 | 7991 | 11454}
min-mpdu-start-spacing {0.25 | 0.5 | 0 | 1 | 2 | 4 | 8 | 16}
mpdu-agg
no
short-guard-intvl-20MHz
short-guard-intvl-40MHz
short-guard-intvl-80MHz
stbc-rx-streams {0 | 1}
stbc-tx-streams
supported-mcs-set
temporal-diversity
very-high-throughput-enable
vht-supported-mcs-map <supported-mcs-set>
vht-txbf-explicit-enable
Description
The mesh HT SSID profile defines settings unique to 802.11n-capable, high-throughput APs. If none of the APs in your mesh deployment are 802.11n-capable APs, you do not need to configure a HT SSID profile.
If you modify a currently provisioned and running high-throughput SSID profile, your changes take effect immediately. You do not reboot the Mobility Conductor or the AP.
Parameter |
Description |
ap mesh-ht-ssid-profile <profile-name> |
Configures a Mesh HT SSID profile. Enter the name of an existing mesh high-throughput SSID profile to modify that profile, or enter a new name or create a new mesh HT profile. The mesh HT profile can have a maximum of 32 characters. To view existing HT SSID radio profiles, use the command default |
40MHz-enable |
Enable or disable the use of 40 MHz channels. enabled |
80MHz-enable |
Enable or disable the use of 80 MHz channels. enabled |
ba-amsdu-enable |
Enable or Disable Receive AMSDU in BA negotiation. enabled |
clone <source> |
Copy configuration information from a source profile into the currently selected profile. |
high-efficiency-enable
|
Enables high-efficiency (802.11ax) features on this SSID. |
high-throughput-enable |
Enable or disable HT (802.11n) features on this SSID. enabled |
ldpc |
If enabled, the AP will advertise Low-density Parity Check (LDPC) support. LDPC improves data transmission over radio channels with high levels of background noise. enabled |
legacy-stations |
Allow or disallow associations from legacy (non-HT) stations. By default, this parameter is enabled (legacy stations are allowed). enabled |
max-rx-a-mpdu-size |
Maximum size of a received aggregate MPDU, in bytes. 8191, 16383, 32767, 65535 |
max-tx-a-mpdu-size <max-tx-a-mpdu-size> |
Maximum size of a transmitted aggregate MPDU, in bytes. 1576-65535 |
max-tx-a-msdu-count-be <max-tx-a-msdu-count-be> |
Maximum number of MSDUs in a TX A-MSDU on best-effort AC. TX-AMSDU disabled if 0. 0-15 2 |
max-tx-a-msdu-count-bk <max-tx-a-msdu-count-bk> |
Maximum number of MSDUs in a TX A-MSDU on background AC. TX-AMSDU disabled if 0. 0-15 2 |
max-tx-a-msdu-count-vi <max-tx-a-msdu-count-vi> |
Maximum number of MSDUs in a TX A-MSDU on video AC. TX-AMSDU disabled if 0. 0-15 2 |
max-tx-a-msdu-count-vo <max-tx-a-msdu-count-vo> |
Maximum number of MSDUs in a TX A-MSDU on voice AC. TX-AMSDU disabled if 0. 0-15 0 |
max-vht-mpdu-size |
Maximum size of a VHT MPDU. 3895, 7991, 11454 11454 |
min-mpdu-start-spacing |
Minimum time between the start of adjacent MPDUs within an aggregate MPDU, in microseconds. 0, 0.25, 0.5, 1, 2, 4, 8, 16 0 |
mpdu-agg |
Enable or disable MPDU aggregation. HT mesh APs are able to send aggregated MDPUs, which allow an AP to receive a single block acknowledgment instead of multiple ACK signals. This option, which is enabled by default, reduces network traffic overhead by effectively eliminating the need to initiate a new transfer for every MPDU. enabled |
no |
Delete command. |
short-guard-intvl-20Mhz |
Enable or disable use of short (400 ns) guard interval for 130 Series APs in 20 MHz mode. A guard interval is a period of time between transmissions that allows reflections from the previous data transmission to settle before an AP transmits data again. An AP identifies any signal content received inside this interval as unwanted inter-symbol interference, and rejects that data. The 802.11n standard specifies two guard intervals: 400 ns (short) and 800 ns (long). Enabling a short guard interval can decrease network overhead by reducing unnecessary idle time on each AP. Some outdoor deployments, may, however require a longer guard interval. If the short guard interval does not allow enough time for reflections to settle in your mesh deployment, inter-symbol interference values may increase and degrade throughput. enabled |
short-guard-intvl-40Mhz |
Enable or disable use of short (400 ns) guard interval in 40 MHz mode. A guard interval is a period of time between transmissions that allows reflections from the previous data transmission to settle before an AP transmits data again. An AP identifies any signal content received inside this interval as unwanted inter-symbol interference, and rejects that data. The 802.11n standard specifies two guard intervals: 400 ns (short) and 800 ns (long). Enabling a short guard interval can decrease network overhead by reducing unnecessary idle time on each AP. Some outdoor deployments, may, however require a longer guard interval. If the short guard interval does not allow enough time for reflections to settle in your mesh deployment, inter-symbol interference values may increase and degrade throughput. enabled |
short-guard-intvl-80Mhz |
Enable or disable use of short (400 ns) guard interval in 80 MHz mode. A guard interval is a period of time between transmissions that allows reflections from the previous data transmission to settle before an AP transmits data again. An AP identifies any signal content received inside this interval as unwanted inter-symbol interference, and rejects that data. The 802.11n standard specifies two guard intervals: 400 ns (short) and 800 ns (long). Enabling a short guard interval can decrease network overhead by reducing unnecessary idle time on each AP. Some outdoor deployments, may, however require a longer guard interval. If the short guard interval does not allow enough time for reflections to settle in your mesh deployment, inter-symbol interference values may increase and degrade throughput. enabled |
stbc-rx-streams
|
Controls the maximum number of spatial streams usable for STBC reception. 0 disables STBC reception, 1 uses STBC for MCS 0–7. Higher MCS values are not supported. (Supported on the 130 Series, 170 Series and AP‑105 only. The configured value will be adjusted based on AP capabilities.) 0-1 1 |
stbc-tx-streams
|
Controls the maximum number of spatial streams usable for STBC transmission. 0 disables STBC transmission, 1 uses STBC for MCS 0–7. Higher MCS values are not supported. (Supported on 170 Series, 130 Series and AP‑105 only. The configured value will be adjusted based on AP capabilities.) 0-1 1 |
supported-mcs-set <supported-mcs-set> |
A list of Modulation Coding Scheme (MCS) values or ranges of values to be supported on this SSID. The MCS you choose determines the channel width (20 MHz vs. 40 MHz) and the number of spatial streams used by the mesh node. The default value is 0–31—16–23 are supported on 130 Series/RAP-15x/802.11ac APs only; 24–31 are supported on 320 Series/330 Series only. To specify a smaller range of values, enter a hyphen between the lower and upper values. To specify a series of different values, separate each value with a comma. 0–31 0-31 |
temporal-diversity |
Shows if temporal diversity has been enabled or disabled. When this feature is enabled and the client is not responding to 802.11 packets, the AP will launch two hardware retries; if the hardware retries are not successful then it attempts software retries. disabled |
very-high-throughput-enable |
Shows if very-high-throughput (820.11ac) features are enabled or disabled. enabled |
vht-supported-mcs-map <supported-mcs-set> |
Comma-separated list of max supported MCS for spatial streams 1 through 4. Valid values for max MCS are 7, 8, 9, and - (if spatial stream is not supported). Max MCS of a spatial stream cannot be higher than the MCS of the previous stream. If an MCS is not valid for a particular combination of bandwidth and number of spatial streams, it will not be used for Tx and Rx. 9,9,9,9 |
vht-txbf-explicit-enable |
Enable or Disable use of VHT Explicit Transmit Beamforming. enabled |
Example
The following command configures a mesh HT SSID profile named “HT1” and sets some non-default settings for MPDU aggregation:
(host) [mynode] (config) #ap mesh-ht-ssid-profile HT1
(host) [mynode] (Mesh High-throughput SSID profile "HT1") #max-rx-a-mpdu-size 32767
(host) [mynode] (Mesh High-throughput SSID profile "HT1") #max-tx-a-mpdu-size 32767
(host) [mynode] (Mesh High-throughput SSID profile "HT1") #min-mpdu-start-spacing .25
Related Commands
Command |
Description |
View a complete list of mesh HT SSID profiles and their status. |
|
View the settings of a specific mesh radio profile. |
Command History
Release |
Modification |
ArubaOS 8.6.0.0 |
The |
ArubaOS 8.0.0.0 |
Command introduced. |
Command Information
Platforms |
License |
Command Mode |
All platforms |
Base operating system. |
Config mode on Mobility Conductor. |