Migrating to AOS 10

Guidance on moving an HPE Aruba Networking mobility infrastructure from AOS 8 or InstantOS 8 to AOS 10.

Migrating existing hardware to HPE Aruba Networking Operating System AOS 10 (AOS 10) will require some consideration and planning before firmware can be loaded. While Mobility Controllers that, now known as Gateways in AOS 10, are currently running HPE Aruba Networking Wireless Operating System AOS 8 (AOS 8) have a straightforward path to AOS 10, access points (APs) can be deployed in multiple ways:

  • An AP operating in campus mode, running AOS 8 with a Mobility Conductor and/or Mobility Controller
  • HPE Aruba Networking Instant Operating System AOS 8 (IAP 8) managed by HPE Aruba Networking Central (Central)
  • IAP 8 with local management, i.e., the virtual controller
  • IAP 8 managed by HPE Aruba Networking AirWave

How the APs are currently deployed, the software type and version, and the management and operation tool used, will determine the required path for successfully migrating to AOS 10. In the case of an AOS 8 deployment with APs deployed in Campus mode and directly controlled by Mobility Controllers, migrating to AOS 10 also introduces a major architectural change as Central is now required to operate and manage the APs and Gateways. With this change, the migration to AOS 10 requires the entirety of the AOS 8 configuration be recreated in Central.


Familiarity with AOS 10 is a requirement for success with the adoption process; if necessary, review these helpful articles for further information:


Make sure to validate that all of the applicable prerequisites are met before attempting to migrate any hardware to AOS 10.

  • The device hardware (AP or Gateway) is supported on AOS 10.
  • Devices are present within the inventory of HPE GreenLake Edge-to-Cloud Platform (GLCP) and have a valid application and subscription applied; see Setting up Your Aruba Central Instance for assistance.
    • The pre-validate option for conversion of Campus APs requires pre-provisioning the AP into an AOS 10 Access Point Group in Central.
  • Devices can resolve all applicable FQDNs and reach those targets on required ports; refer to the guide “Opening Firewall Ports for Device Communication” for assistance.
  • Access Points must be running IPv4 or dual stack mode; native IPv6 on APs is not supported
  • Instant APs must be running Aruba Instant OS,, or later releases for a successful firmware upgrade.
  • A cluster of Instant APs must not contain any AP models not supported by AOS 10.
  • Instant APs must not have the uplink native VLAN configured.
  • To convert Campus APs, the associated gateway should be running AOS,, or a later release.
    • If using release of AOS 8.10 prior to, transferring an image to the controller using SCP will result in incorrect permissions applied to the image; upload the image to the controller using a method other than SCP.
    • If using release of AOS 8.10 prior to and CPSec is enabled, the pre-validate operation will fail due to the packet routing used for CPSec; bypassing the validation process will allow the upgrade to complete at the risk of incomplete setup of the APs.
  • Mobility Controllers/Gateways that have previously undergone a firmware upgrade will not contact Aruba Activate for an upgrade to a Central-enabled firmware version and must be manually upgraded to AOS 10. After upgrade, the Gateway must have the configuration erased and the appliance must be rebooted before they can be provisioned in Central.
  • Mobility Controllers/Gateways to be upgraded must be removed from any Activate folder with existing provisioning rules before attempting the upgrade or connecting to Central.
  • Using AirWave or later to perform a firmware upgrade to AOS 10 is not possible.

Last modified: May 28, 2024 (b627a62)