SELECTION & PROCUREMENT
AOS 8 to AOS 10: an Aruba expansion and migration checklist
Prepared by Xunhui Information · English publication: 2026-11-20
Map hardware, management, forwarding, authentication, licensing and rollback before an Aruba wireless migration.
On this page
Map existing dependencies
List exact APs, controllers/gateways, management, software, identity, DHCP/DNS/NTP, VLANs and exits. Show management, authentication and client traffic separately and establish the current forwarding model.
Verify the target support matrix
Validate each AP/gateway against the intended release, features, Central platform and subscriptions. Do not carry AOS 8 architectural assumptions into AOS 10 or assume a newer AP will join an older control platform.
| Stage | Deliverable |
|---|---|
| Plan | Current/target topology, gaps, licensing and ownership |
| Pilot | Representative clients, authentication, isolation, applications and roaming |
| Cutover | Window, owner, backups, monitoring and stop conditions |
| Rollback | Executable restoration procedure, dependencies and time boundaries |
| Handover | Software/configuration records, policy matrix and operational ownership |
Stop conditions are part of the plan
Stop expansion when agreed business, authorization or recovery conditions fail. Retain logs and timestamps and follow the approved rollback. Acceptance thresholds must match actual applications and clients.
Related guidance
Wireless upgrade design and gateway references support configuration planning.
Apply the guidance to your project
Share the model, quantity, destination and existing network so we can discuss the complete configuration.
Discuss configuration & quotation ↗