AOS-8.11.x.x
Release Overview
General information about a major release is described in this page. Click on each heading to display the relevant information. For version-specific release notes, select the desired version from the All Versions dropdown menu above.
Important
-
Upgrading from AOS-8.11.1.0 or earlier versions on 9000 Series and 9200 Series controllers will take longer than usual as we will be automatically upgrading the BIOS version to support additional functionality in the future. This upgrade is estimated to take up to 15 minutes and should not be interrupted for any reason. Power failures and interruptions during the upgrade may make the controller unusable. Please use caution and plan accordingly.
Cluster Rolling Upgrade is not supported when a BIOS upgrade is required. AOS-8 must be manually upgraded for these controllers. In a (very rare) scenario where, post reload command, the unit does not come up in 15-20 minutes, apply power cycle only once and wait for a minimum of 15 minutes without re-applying power cycle again.
-
As mandated by the Wi-Fi Alliance, AOS-8.10.0.0 and later versions require Hash-to-Element (H2E) for 6 GHz WPA3-SAE connections. H2E is supported on Android 12 or later versions, Linux wpa_supplicant version 2.10 or later versions, macOS Catalina or later versions, Windows 11 or later versions. Users must upgrade their clients to support successful 6 GHz WPA3-SAE connections.
- The factory-default image of APs introduced in AOS-8.9.0.0 or later versions use aruba-conductor as the host name instead of aruba-master to identify a target managed device or stand-alone controller during DNS discovery. However, the factory-default image of APs that were introduced prior to AOS-8.9.0.0 still use aruba-master during DNS discovery. The usage of aruba-conductor is to align with the Inclusive Language Initiative.

RADIUS Authentication Server Profile Configurations Added to AirGroup Version 2
The AirGroup version 2 module now accepts RADIUS authentication profile changes such as nas-IP and source-interface through the aaa authentication-server radius command. Rather than depending on the Mobility Conductor's settings, this feature allows for specific authentication-related configurations to be applied to managed devices.
The configuration varies depending on the AirGroup mode used:
- Centralized mode requires configurations to be applied on both the Mobility Conductor and managed device. In the case of having different profiles configured, the managed device's profile will take priority.
- Distributed mode requires node-specific configuration. In the case of having governing managed devices, the configuration will apply to all member nodes. However, node-specific configuration can still be applied to member nodes if needed.
Enhancement to VAPs
The processing time for manually created VAPs to transition from interfering to valid has been enhanced.
The denylist-sco-attack Parameter is Disabled by Default
The denylist-sco-attack parameter under the aaa-profile command is set to Disabled by default when upgrading to AOS-8.11.2.1 or later versions.
show ap tech-support ap-name Command Enhancement
Starting with AOS-8.11.2.1, the output of the show ap arm split-scan-history <ap-name> command is added in the show ap tech-support ap-name <ap-name> command. This reduces the turn around time during data collection, improving customer service experience.
Added Support for Telematrix IP Phones with AP-505H Access Points
Improved AP-505H PSE port compatibility with early generation Telematrix IP phones.
Support for AP-654 Access Points
The AP-654 access point is the external antenna platform variant of the 650 Series, supporting two sets of antenna interfaces for 2.4 GHz and 5 GHz (A, left side) as well as 6 GHz (B, right side). The Aruba 650 Series access points are high performance, multi-radio access points that can be deployed in either controller-based (AOS-8) or controller-less (Aruba Instant) network environments. These APs deliver comprehensive tri-band coverage across 2.4 GHz, 5 GHz, and 6 GHz 802.11ax Wi-Fi (Wi-Fi 6E) functionality with concurrent 4x4 MU-MIMO radios for both uplink and downlink in the 5 GHz and 6 GHz bands. The APs also support 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, and 802.11ax wireless services.
Additional features include:
- Up to 7.8 Gbps combined peak datarate
- Dual wired 5 Gbps Smart Rate ethernet ports for hitless failover
- Orthogonal Frequency Division Multiple Access (OFDMA)
- Aruba Advanced Cellular Coexistence (ACC)
- IoT-ready (integrated Bluetooth 5 and 802.15.4 radio for Zigbee support)
- Ultra Tri-Band (UTB) filtering
- Maximum ratio combining (MRC)
- Intelligent Power Monitoring (IPM)
- Dynamic frequency selection (DFS)
For complete technical details and installation instructions, see the Aruba 650 Series Access Points Installation Guide.
Support for AP-634 Access Points
The AP-634 access point is the external antenna platform variant of the 630 Series, supporting two sets of antenna interfaces for 2.4 GHz and 5 GHz (A, left side) as well as 6 GHz (B, right side). The Aruba 630 Series access points are high performance, multi-radio access points that can be deployed in either controller-based (AOS-8) or controller-less (Aruba Instant) network environments. These APs deliver comprehensive tri-band coverage across 2.4 GHz, 5 GHz, and 6 GHz 802.11ax Wi-Fi (Wi-Fi 6E) functionality with concurrent 2x2 MIMO radios for both uplink and downlink in the 5 GHz and 6 GHz bands. The APs also support 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, and 802.11ax wireless services.
Additional features include:
- Up to 3.9 Gbps combined peak datarate
- Dual wired 2.5 Gbps Smart Rate ethernet ports for hitless failover
- Orthogonal Frequency Division Multiple Access (OFDMA)
- Aruba Advanced Cellular Coexistence (ACC)
- IoT-ready (integrated Bluetooth 5 and 802.15.4 radio for Zigbee support)
- Ultra Tri-Band (UTB) filtering
- Maximum ratio combining (MRC)
- Intelligent Power Monitoring (IPM)
- Dynamic frequency selection (DFS)
For complete technical details and installation instructions, see the Aruba 630 Series Access Points Installation Guide.
Denylist clients in case of a security context override attempt with the denylist-sco-attack parameter
The aaa-profile command now accepts the denylist-sco-attack parameter, which enables denylisting for clients that attempt to perform a security context override, improving security against malicious authenticated clients. For the AOS-8.11.2.0 release, the default value of this parameter is set to Enabled.
Wi-Fi Stats Enhancement
Several 802.11ax performance metrics statistics have been enhanced in this release.
Support for 503 Series Campus AP Platforms
The Aruba 503 Series access points (AP-503) are high performance, dual-radio indoor access points that support the IEEE 802.11ax standard for High Efficiency Wi-Fi, and can be deployed in either controller-based (AOS-8) or controller-less (Aruba Instant) network environments. These APs deliver high performance 2.4 GHz and 5 GHz 802.11ax Wi-Fi (Wi-Fi 6) functionality with 2x2 radios, while also supporting 802.11a, 802.11b, 802.11g, 802.11n, and 802.11ac wireless services.
Additional features include:
- Spectrum analysis (dedicated or hybrid mode)
- Wireless air monitor
- 1000Base-T uplink Ethernet port
- IEEE 802.3af (class 3) PoE support
- Mesh
- Thermal shutdown function
For complete technical details and installation instructions, see Aruba 503 Series Access Points Installation Guide.
Configure Dump Auto Uploading Profile
The dump-auto-uploading-profile parameter is introduced to configure settings for automatically uploading dump files to the controller when Transfer Enable is open and when the Server IP is not configured in the dump collection profile.
Enhancement to CLI Commands
show ap monitor ap-list command
A new sub-parameter, verbose is added to the show ap monitor ap-list ap-name <ap-name> command. The output of the show ap monitor ap-list ap-name <ap-name> verbose command displays additional information about flags and the flag, W is introduced to identify the Wi-Fi direct devices. This flag will be displayed only if the detection of WIFI-Direct P2P groups is enabled in the IDS unauthorized device profile.
show stm perf-history commands
Starting from AOS-8.11.1.0, the show stm perf-history duration and show stm perf-history interval commands can be used to view the output for the specified time interval.
ISO Mounting to Install AOS-8
Starting from AOS-8.11.1.0 the ISO mounting procedure can be used for installing AOS-8.
Support for Open vSwitch with DPDK on KVM Hypervisor
AOS-8 now provides support for configuring Open vSwitch with DPDK on Oracle Linux 7.9 using KVM Hypervisor.
Support for Station-based RADIUS Accounting Session ID
AOS-8 now supports station-based RADIUS accounting session IDs. This feature ensures that a single session ID is used for stations that use multiple IP addresses such as IPv6 deployments. The station-based account session ID feature is now the default for Hotspot 2.0-enabled SSIDs. It is also enabled when the radius-station-based-acct-session parameter or the radius-acct-session-id-in-access parameter of the aaa-profile command is enabled.
UNII-4 Support for 610 Series Access Points
The UNII-4 channels (channels 169-177) are now supported on 610 Series access points (AP-615) only when the operational mode of the AP is set to 2.4GHz-and-5GHz static mode. In the Managed Network node hierarchy, navigate to Configuration > System > Profiles > AP system menu, and select 2.4GHz-and-5GHz option from the Flex Dual Band Mode drop-down list.
Short Supported Release
AOS-8.11.0.0 is a Short Supported Release (SSR).
Support for 610 Series Campus AP Platforms
The Aruba 610 Series access points (AP-615) are high performance, dual-radio, tri-band indoor access points that can be deployed in either controller-based (AOS-8) or controller-less (Aruba Instant) network environments. These APs deliver high performance 2.4 GHz, 5 GHz, and 6 GHz 802.11ax Wi-Fi (Wi-Fi 6E) functionality with dual radios (2x2 in 2.4 GHz, 5 GHz, and 6 GHz), with the ability to operate these radios on any two out of three bands simultaneously. Additionally, these APs deliver capacity with OFDMA (Orthogonal Frequency Division Multiple Access) technologies while also supporting 802.11a, 802.11b, 802.11g, 802.11n, and 802.11ac wireless services.
Additional features include:
- One Ethernet port, ENET0, capable of data rates up to 2.5 Gbps.
- Compatible with IEEE 802.3bt, IEEE 802.3at, and IEEE 802.3af PoE standards on the Ethernet port.
- High power BLE
- Mesh
- Thermal management
|
AP-615 access points operate in 2.4 GHz and 5 GHz radio bands by default. To enable the AP to broadcast on 6 GHz radio band, set the flexible dual band radio mode to either 5 GHz and 6 GHz or 2.4 GHz and 6 GHz mode |
For complete technical details and installation instructions, see Aruba 610 Series Access Points Installation Guide.
AirMatch Support for 610 Series Access Points
AirMatch provides support for dynamic selection of the opmode, in addition to assigning channel and EIRP to the current opmode in 610 Series access points (AP-615). AirMatch selects the opmode dynamically depending on the RF coverage for each radio band—2.4 GHz, 5 GHz and 6 GHz.
BLE Daemon Support for Per-AP Calibrated RSSI Tables
Starting from this release, APs with Gen-2 BLE/IoT radios will adjust the calibrated RSSI values for iBeacon advertisements when BLE transmit power levels are modified using the ble-txpower setting in the IoT Radio Profile configuration. The calibrated values can then be verified using the show ap debug ble-advertisement-info command.
Changes to the Default Setting for Max Clients in an SSID Profile
AOS-8 now supports a maximum of 1024 wireless clients per radio. The maximum number of clients can be configured using the max-client parameter of the wlan ssid-profile command.
Cipher Suites in Web Server Configuration
The cipher-suite parameter is introduced to replace ciphers parameter. This feature allows users to select specific ciphers from the supported list of ciphers. Cipher suites are streamlined in such a way that only strong cipher suites are enabled by default. This is compatible with the FIPS mode as well. As a part of this enhancement, users are given the option to selectively enable and disable the remaining cipher suits while configuring the web server profile.
Concurrent VIA VPN Sessions Limit
The maximum number of concurrent VIA VPN session per user is restricted. The admin is enabled to configure a value between 1-32 to restrict the concurrent VIA VPN sessions per user.
Configuring the Default Gateway on the OOB Management Port
AOS-8.11.0.0 supports configuring the default gateway for dedicated OOB management Ethernet port on 7000 Series controllers by using the ip default-gateway mgmt <nexthop> command.
Default ARP Rate Set for Global Firewall Parameter - ARP Attack
Starting from this release, the default value for global firewall parameter
is set to 100.Enable or Disable BLE Periodic Telemetry
The BLE Telemetry setting can now be enabled or disabled in the AOS-8. webUI. A new parameter blePeriodicTelemetryDisable is introduced in the iot transportProfile command to disable periodic telemetry reporting.
Enabling Fast Initial Link Setup (FILS) for an AP in 6 GHz Only Mode
AOS-8.11.0.0 now supports an AP in a 6GHz only mode. If 2.4GHz and 5GHz VAPs are unavailable, then FILS will be automatically enabled for the 6GHz VAPs configured on the AP allowing the 6GHz clients to obtain the SSID information by FILS. When 2.4GHz and 5GHz VAPs are available again, FILS will be automatically disabled allowing the 6GHz clients to obtain the SSID information over the Reduced Neighbor Report (RNR) in the 5 GHz or 2.4 GHz beacons.
Enhancement to the wlsxWlanStationTable MIB
As an enhancement, a new wlanStaApName MIB object is added to the wlsxWlanStationTable MIB to simplify the correlation of APs and Stations.
Flex Dual Band Support for AP-615 Access Points
AOS-8.11.0.0 now supports dual band support on Aruba AP-615 that provides flexibility for the radios of AP-615 to operate on different radio bands. The AP-615 access points do not support tri-radio mode or split 5 GHz mode. For example, radio 0 can operate on 2.4 GHz or 5 GHz band and radio 1 can work on 2.4 GHz or 6 GHz band. AP-615 access points operate in 2.4 GHz and 5 GHz radio bands by default. To enable the AP to broadcast on 6 GHz radio band, set the flexible dual band radio mode to either 5 GHz and 6 GHz or 2.4 GHz and 6 GHz mode.
The following command enables the flex dual band support for an AP on stand-alone controllers.
(host) [mynode] (AP system profile "default") #flex-dual
The following command enables the flex dual band support for an AP in a Mobility Master-Managed Device topology.
(host) [mynode] (AP system profile "default") #flex-dual-mode
The following command provides the status of the flex dual band support for an AP.
(host) [mynode] #show ap active
Grouping AirGroup Servers based on the Username
AirGroup, with enforce registration enabled, allows the 802.1X authenticated users to view the list of all servers that share the same username. Users need not add any CPPM policy to view the list of servers that share the same username.
The following CLI command enables enforce registration in the AirGroup profile:
(host) [md] (config) #airgroupprofile <profile-name> enforce-registration
The output of the show airgroup servers and show airgroup cppm entries commands display the D flag to indicate that the servers share the same username.
|
Username-based policy entries are automatically added for servers with username and no CPPM policy. This policy is displayed in the output of the show airgroup cppm entries command along with the D flag. |
The show airgroup servers username <username> command also displays the list of servers that have the same username.
Improvements to Health Messages Reported during IoT Transport
The health messages sent during IoT transport have been updated to include more information on the health statuses of the devices.
-
Radio health message now includes information about the Up or Down status of the radio mode, BLE mode or Zigbee Mode etc.
-
USB health message now reports as healthy, only if the dongle is up-and-running. The USB device includes USB Nordic APB and Serial-Data USB device such as Enocean device.
-
AP health message will now include the AP layer's metrics status which are related to reporting data.
IoT Audit Trail
The show ap debug iot-audit-trail command is introduced to display all the action commands executed in the CLI and report the Southbound API messages received from the server.
IPM Radio Power Reduction Steps
Starting from AOS-8.11.0.0, the IPM radio power reduction steps use radio indices (0,1, and 2) to refer to the radios that are restricted. Prior to AOS-8.11.0.0, the IPM radio power reduction steps referred to the operating bands of the radio. This enhancement removes the association between the power reduction steps and the operating bands to simplify the IPM feature design. The association between the radio index and the operating band is displayed in the output of the show ap active command.
Mesh Support for AP-615 Access Points
AOS-8.11.0.0 now extends mesh support for AP-615 access points. In the mesh cluster profile, the a, g, 6GHz, and all mesh bands will allow the mesh nodes to operate on 5 GHz, 2.4GHz, 6GHz, and all radio bands. The mesh link and Wi-Fi uplink features continue to operate on the band configured in the AP system profile. When the radio modes are changed, the mesh and wifi uplink modules will restart and resume on the radio defined in the existing configuration. If the provisioned rf-mesh band is not available on the flex-dual band, it will let the AP use the all rf-mesh band all to instead of the rf band you configured. It means that if the rf band configuration is not in the flex-dual mode, it will let the AP open all the mesh radios to connect. For example, when the rf-mesh band is g and the flex-band is 5GHz-and-6GHz, the rf-mesh band will automatically change to all and radio 0 will operate on 5 GHz and radio 1 will operate on 6 GHz radio bands.
Modifications to CLI Commands
The write erase all, halt, and reload commands can be issued only from the /mm/mynode and /mm nodes of the Mobility Conductor.
Modifications to CLI command Parameters
The active-client-rebalance-threshold, standby-client-rebalance-threshold, and unbalance-threshold parameters of the lc-cluster group-profile command are not supported from AOS-8.11.0.0.
No Support for WEP Configuration in Wi-Fi Uplink Profile
AOS-8 no longer supports WEP parameters for configuring Wi-Fi uplink profile. The following parameters have been removed from Wi-Fi uplink profile:
-
Static WEP
-
WEP Key 1
-
WEP Key 2
-
WEP Key 3
-
WEP Key 4
-
WEP Transmit Key Index
OOB 6 GHz Scanning for AP-615
AOS-8 allows users to configure OOB 6 GHz scanning settings for AP-615 access points. The oob-switch parameter is introduced in the regulatory domain profile to enable and disable OOB 6 GHz scanning for AP-615 access points. Disabling oob-switch, disables 6 GHz scanning and it is applicable only when AP-615 access points are in the 5GHz-and-2.4GHz operation mode.
Opmode-transition Support for WPA3
AOS-8 allows users to disable the opmode-transition parameter for virtual APs to be deployed on 6 GHz bands using MFP.
Organizational Unit (OU) as an Optional Parameter
Organizational Unit (OU) is no longer a mandatory parameter for VIA Domain Name profiles. This is because the OU parameter is now deprecated by various certificate authorities. Hence, OU is an optional parameter under Add New window of Configuration > Authentication > L3 Authentication > VIA Connection > default > VIA Domain Name Profiles in the WebUI. In the CLI, the OU parameter is optional under the following command.
(host) [mynode] (config) #aaa authentication via connection-profile > dn-profile
RTS Frame Transmission to the Clients
AOS-8 allows users to control RTS frame transmission to the clients. The rf dot11a-radio-profile, rf dot11g-radio-profile, rf dot11a-secondary-radio-profile, and rf dot11-6GHz-radio-profile commands allow users to enable or disable RTS mode based on their network requirement.
Support of 1024 clients on 2G and 5G Bands
AOS-8.11.0.0 now supports 1024 clients on the 2G and 5G bands of an AP-655.
Support for Active Client Rebalance Threshold Feature
Starting with AOS-8.11.0.0, the Active client rebalance threshold feature is not supported and can no longer be configured using the AOS-8 WebUI or CLI.
Support for All Flags in the AP Database
AOS-8 now includes all available flags associated with an AP in the show ap database flags <flags> command.
Support for Bucket Based Client Load Balancing
AOS-8.11.0.0 now supports the bucket based client load balancing feature that distributes the buckets based on the platform capacity in a cluster. In bucket based client load balancing, the cluster manager intermittently checks for the proportionate distribution of the bucketmap among the cluster nodes, and if required, re-balances 8 buckets of one ESSID in one iteration. The periodicity of rebalancing of the buckets among the cluster nodes is at every 20 seconds.
The following CLI command displays the current bucket distribution for all the ESSIDs.
(host) [mynode] #show lc-cluster bucket distribution all
The following CLI command displays the current bucket distribution for a specific ESSID.
(host) [mynode] #show lc-cluster bucket distribution essid
The following CLI command displays the details of the bucketmap publish counters.
(host) [mynode] #show lc-cluster bucketmap publish counters
The following CLI command clears the details of the bucketmap publish counters.
(host) [mynode] #clear lc-cluster bucketmap publish counters
Support for CentOS 7.9 and Ubuntu 20.04
AOS-8.11.0.0 now supports deploying a Mobility Controller Virtual Appliance or a Mobility Master Virtual Appliance using CentOS 7.9 or Ubuntu 20.04 KVM Hypervisor.
Support for Ethernet 0 as Downlink Port
Starting from AOS-8.11.0.0, Ethernet Port 0 can be assigned as the downlink port if Ethernet Port 1 is configured or running as the primary uplink on AP-318, AP-374, AP-375, AP-375ATEX, AP-377, AP-584, AP-585, AP-585EX, AP-587, and AP-587EX.
Support for Hyper-V Version Windows Server 2019
AOS-8.11.0.0 now supports deploying a Mobility Controller Virtual Appliance or a Mobility Master Virtual Appliance using Hyper-V Version Windows Server 2019.
Support for Multiple Long-Lasting Connections with Nordic Chip Radio
Starting from this release, Instant supports concurrent scanning and bleConnect connections to the IoT devices. A maximum of ten concurrent connections can be established. This function is currently supported only on Instant APs with nordic radios —500 Series, 510 Series, 530 Series, 550 Series, 560 Series, 570 Series, 610 Series, and 630 Series access points, along with an external USB dongle.
Support for New ABB Sensors
The following two new ABB sensors are supported by Aruba APs. Listed below are details on how to identify the sensor type and and work out the sensor identifier from the advertisement packets:
-
DFU Target Device—The DFU target is the device that runs the DFU having at least one active DFU transport. It can be the bootloader in DFU mode, or an application with DFU running in the background. To be able to perform an update using the AP the sensor must be discovered when it enters the bootloader mode.
-
Sensor Identifier—The DFU target device sensor is recognized by service class UUID : 0xFE59. This service UUID needs to be configured under Filters in the IoT transport profile.
The following procedure describes how to configure DFU Target Device on an AP:
-
When configuring the IoT transport profile, ensure that the Server Type is either set to Telemetry Https, Telemetry Websocket, or Azure IoT Hub.
-
Under Filters, click Company Identifier, and the click +.
-
Enter the sensor identifier FE59 in the text box and click Ok.
-
-
The following CLI command is used to configure DFU Target Device on an AP:
(AOS-8 AP)[Mode]# iot transportProfile example
(AOS-8 AP)(IoT Transport Profile "example")# companyIdentifierFilter FE59
-
SALT Star Vario—The SALT Star Vario sensor is recognized by local name : perma. When the local name is parsed to the Instant AP, the identity of the sensor is assigned as SALT + MAC Address. For example, if device's MAC address is 00:80:25:FB:1A:73, then its identity is SALT008036FB1A73. This sensor identifier can be configured under Filters in the IoT transport profile.
The following procedure desccribes how to configure SALT Star Vario on an AP:
-
When configuring the IoT transport profile, ensure that the Server Type is either set to Telemetry Https, Telemetry Websocket, or Azure IoT Hub.
-
Under Filters, click Local Name, and the click +.
-
Enter the sensor identifier Perma in the text box and click Ok.
The following CLI command is used to configure SALT Star Vario on an AP:
(AOS-8 AP)(Config)# iot transportProfile example
(AOS-8 AP)(IoT Transport Profile "example")# localNameFilter perma
For more information, see Configuring an IoT Transport Profile in the AOS-8.11.0.0 User Guide.
-
Support for Packet Debugging Functionality on APs
AOS-8. introduces the following two commands that support packet debugging functionality to troubleshoot the data packets through the AP datapath:
-
ap remote-debug-pkt
-
show ap remote-debug-pkt
Support for UNII-4 Channels
AOS-8. supports UNII-4 (channels 169-177) on 530 Series, 550 Series, 630 Series, and 650 Series access points.
Support to Enable Frame Bursting
AOS-8 allows users to control frame bursting even if there is only one active client associated to the AP. Users can enable or disable frame bursting using the rf dot11a-radio-profile frame-bursting-mode , rf dot11-6Ghz-radio-profile frame-bursting-mode, rf dot11a-secondary-radio-profile frame-bursting-mode, and rf dot11g-radio-profile frame-bursting-mode commands.
Vendor Specific IE based Containment
AOS-8 allows to configure exclusions for IDS containment based on vendor specific IE information. This feature allows APs to be exempted from containment even when the devices use randomized MAC addresses. To exempt APs from containment, users should configure the vendor OUI and OUI type in the IDS unauthorized device profile. A maximum of five vendor OUI and OUI types can be defined for confinement exclusion.
VLAN Derivation Support to Clients using Split-Tunnel Forwarding Mode
VLAN derivation support is extended to wired and wireless clients using split-tunnel forwarding mode along with tunnel, bridge and decrypt-tunnel modes.
Wi-Fi Uplink Support for 610 Series Access Points
AOS-8 supports Wi-Fi uplink feature on 610 Series access points for 2.4 GHz, 5 GHz, and 6 GHz radio bands.
Zero-Wait DFS Support for 650 Series Access Points
AOS-8 supports zero-wait DFS feature on the 650 Series access points for 5 GHz radio band.

Removal of ssh-rsa Signature Scheme from SSH Cryptographic Settings
The ssh-rsa parameter has been removed to eliminate any security concerns with the SHA-1 hash algorithm and RSA public key algorithm.

This section includes the known limitations in 8.11.x.x releases.
Title |
Description |
Applicable to |
---|---|---|
Port-Channel Limitation in 7280 Controllers |
The 7280 hardware architecture consists of two Network Acceleration Engines (NAEs). The ethernet ports are split between the NAEs according to this mapping:
When configuring a port-channel, it is recommended that member ports are distributed between the two different NAEs (e.g., 0/0/0 and 0/0/4) . This is to ensure hitless operation if one of the member ports experiences a link flap either due to a network event or a user-driven action. If member ports are on the same NAE, a link flap will be observed for less than a second. It is not recommended to form a 10 Gbe based port-channel larger than 2x 10 Gbe due to this hardware limitation. |
AOS-8.11.x |
AP-615, AP-635, and AP-655 Access Points Limitations |
|
AOS-8.11.x |
No Support for Airtime Fairness Mode |
Airtime Fairness Mode is not supported in 802.11ax access points. |
AOS-8.11.x |
cpboot command in 7000 Series and 7200 SeriesControllers |
The cpboot command does not upgrade the AOS-8 software version of 7000 Series and 7200 Series controllers. |
AOS-8.11.x |
AP-654 and AP-634 Access Points |
AP-654 and AP-634 access points do not support 6 GHz band operation. |
AOS-8.11.2.x |

Supported Platforms in AOS-8.x
This section displays the supported platforms in AOS-8.x. The minimum version supported column displays the minimum AOS-8.x version that can be run on a platform. The latest version supported column displays the newest AOS-8.x version that can be run on a certain device. Patch releases do not affect platform support. For example, a device which latest supported version is 8.10.0.x can run on any 8.10.0.x version, such as 8.10.0.2 or 8.10.0.10.
Mobility Conductor Platforms
Mobility Conductors |
AOS-8.x Versions Supported |
||
---|---|---|---|
Conductor Family |
Conductor Model |
Minimum |
Latest |
Hardware Mobility Conductor |
MCR-HW-1K, MCR-HW-5K, MCR-HW-10K |
8.1.0.x |
8.12.0.x |
Virtual Mobility Conductor |
MCR-VA-500, MCR-VA-1K, MCR-VA-5K, MCR-VA-10K |
8.0.0.x |
8.12.0.x |
MCR-VA-50 |
8.1.0.x |
8.12.0.x |
Mobility Controller Platforms
Mobility Controllers |
AOS-8.x Versions Supported |
||
---|---|---|---|
Controller Family |
Controller Model |
Minimum |
Latest |
9200 Series |
9240 |
8.10.0.x |
8.12.0.x |
9000 Series |
9012 |
8.7.0.x |
8.12.0.x |
9004 |
8.5.0.x |
8.12.0.x |
|
7200 Series |
7280 |
8.3.0.x |
8.12.0.x |
7205, 7210, 7220, 7240, 7240XM |
8.0.0.x |
8.12.0.x |
|
7000 Series |
7005, 7008, 7010, 7024, 7030 |
8.0.0.x |
8.12.0.x |
Virtual Mobility Controllers |
MC-VA-50, MC-VA-250, MC-VA-1K |
8.0.0.x |
8.12.0.x |
MC-VA-10 |
8.4.0.x |
8.12.0.x |
Access Point Platforms
Access Points |
AOS-8.x Versions Supported |
|||
---|---|---|---|---|
AP Family |
AP Series |
AP Model |
Minimum |
Latest |
6xx |
670 Series |
AP-675, AP-675EX, AP-677, AP-677EX, AP-679, AP-679EX |
8.12.0.x |
8.12.0.x |
650 Series |
AP-655 |
8.10.0.x |
8.12.0.x |
|
AP-654 |
8.11.2.x |
8.12.0.x |
||
630 Series |
AP-635 |
8.9.0.x |
8.12.0.x |
|
AP-634 |
8.11.2.x |
8.12.0.x |
||
610 Series |
AP-615 |
8.11.0.x |
8.12.0.x |
|
600 Series |
AP-605H |
8.12.0.x |
8.12.0.x |
|
5xx |
580 Series |
AP-584, AP-585, AP-585EX, AP-587, AP-587EX |
8.10.0.x |
8.12.0.x |
570 Series |
AP-574, AP-575, AP-577. AP-575EX, AP-577EX |
8.7.0.x |
8.12.0.x |
|
560 Series |
AP-565, AP-567, AP-565EX, AP-567EX |
8.7.1.x |
8.12.0.x |
|
550 Series |
AP-555 |
8.5.0.x |
8.12.0.x |
|
530 Series |
AP-534, AP-535 |
8.5.0.x |
8.12.0.x |
|
510 Series |
AP-518 |
8.7.0.x |
8.12.0.x |
|
AP-514, AP-515 |
8.4.0.x |
8.12.0.x |
||
500 Series |
AP-504, AP-505 |
8.6.0.x |
8.12.0.x |
|
AP-505H, AP-505HR |
8.7.0.x |
8.12.0.x |
||
AP-503H, AP-503HR |
8.7.1.x |
8.12.0.x |
||
AP-503 |
8.11.1.x |
8.12.0.x |
||
3xx |
380 Series |
AP-387 |
8.4.0.x |
8.10.0.x |
370 Series |
AP-374, AP-375, AP-377, AP-375EX, AP-377EX, AP-375ATEX |
8.3.0.x |
8.12.0.x |
|
360 Series |
AP-365, AP-367 |
8.3.0.x |
8.12.0.x |
|
340 Series |
AP-344, AP-345 |
8.3.0.x |
8.10.0.x |
|
330 Series |
AP-334, AP-335 |
8.1.0.x |
8.10.0.x |
|
320 Series |
AP-324, AP-325 |
8.0.0.x |
8.10.0.x |
|
310 Series |
AP-318 |
8.3.0.x |
8.12.0.x |
|
AP-314, AP-315 |
8.1.0.x |
8.12.0.x |
||
300 Series |
AP-304, AP-305 |
8.1.0.x |
8.12.0.x |
|
AP-303H, AP-303HR |
8.2.0.x |
8.12.0.x |
||
AP-303P |
8.4.0.x |
8.12.0.x |
||
AP-303 |
8.3.0.x |
8.12.0.x |
||
2xx |
270 Series |
AP-274, AP-275, AP-277 |
8.0.0.x |
8.10.0.x |
220 Series |
AP-224, AP-225, AP-228 |
8.0.0.x |
8.10.0.x |
|
210 Series |
AP-214, AP-215 |
8.0.0.x |
8.10.0.x |
|
200 Series |
AP-207 |
8.1.0.x |
8.10.0.x |
|
AP-204, AP-205, AP-205H |
8.0.0.x |
8.10.0.x |
||
AP-203H, AP-203R, AP-203RP |
8.2.0.x |
8.10.0.x |
||
1xx |
170 Series |
AP-175AC, AP-175AC-F1, AP-175DC, AP-175DC-F1, AP-175P, AP-175P-F1 |
8.0.0.x |
8.6.0.x |
130 Series |
AP‑134, AP-135 |
8.0.0.x |
8.6.0.x |
|
110 Series |
AP-114, AP-115 |
8.0.0.x |
8.6.0.x |
|
100 Series |
AP-103, AP‑104, AP‑105 |
8.0.0.x |
8.6.0.x |
|
AP-103H |
8.0.0.x |
8.3.0.x |
||
9x |
90 Series |
AP‑92, AP‑93, AP-93H |
8.0.0.x |
8.2.0.x |

The following browsers are officially supported for use with AOS-8 WebUI:
Web Browser |
Operating System |
---|---|
Microsoft Edge (Microsoft Edge 92.0.902.62 and Microsoft EdgeHTML 18.19041) or later |
|
Firefox 107.0.1 or later |
|
Apple Safari 15.4 (17613.1.17.1.13) or later |
|
Google Chrome 108.0.5359.71 or later |
|