Preparing Central for AOS 10 Migration
2 minute read
Migrating to AOS 10, regardless of the starting point, requires some initial configuration within Central for the best outcome during migration.
Prepare an AOS 10 Group in Central
-
Create a new group on the Aruba Central account. Go to Global > Organization > Network Structure > Groups. A new group must be created; do not attempt to use a cloned or existing group with IAP 8.X configuration for AOS 10. Use the + (plus sign) button to add a new group.
-
Choose the hardware the Group will administer. A single group can contain a single type or a mixture of hardware.
Group dedicated to APs:
Group dedicated to Gateways:
NoteIf there is a need to preserve the naming convention for this new AOS 10 group for a particular customer requirement, clone the original group with a different name, move devices to the temporary group, and delete the original. As a good practice, avoid deleting the temporary group until you are completely satisfied with the AOS 10 conversion. -
Choose ArubaOS 10 as the architecture to use for the new group and select the appropriate Network Role for the APs:
If creating a group including or dedicated to Gateways, the role for the gateways must be indicated:
NoteThe VPN Concentrator (VPNC) role is available only when configuring a Gateway-only group, the VPNC group cannot contain APs or switches. -
Select the newly created group and choose the desired hardware type. In the left menu, use the Firmware option to set the firmware compliance to an AOS 10 firmware version. Click Set Compliance in the upper right.
-
Enable the Set firmware compliance toggle and choose a version of AOS 10 from the dropdown to ensure that devices added to the group will be upgraded appropriately.
-
Prepare the configuration for this new AOS 10 group by configuring System settings such as country code, time zone, NTP, WLAN configuration, etc. For AP groups, refer to Configuring ArubaOS 10 APs in Aruba Central. Gateway configuration information can be found at Gateway Deployment.
Mixed Model Aruba Instant Cluster
Before migrating a cluster of Aruba Instant APs to AOS 10, any models unsupported in AOS 10 must be removed or moved to a separate management network to split the cluster. Attempting to upgrade firmware to AOS 10 when unsupported models are in the cluster will result in an error for the download and none of the APs will be upgraded.
Feedback
Was this page helpful?
Glad to hear it!
Sorry to hear that.