AOS-8 → AOS-10 Campus AP Migration Toolkit

A Python-driven Windows 11 desktop application (native desktop GUI + Netmiko / Aruba Central REST core) that curates a convert list of AOS-8 MM/MD–managed campus APs and migrates them to Aruba Central on AOS-10 — using either batch-by-model or dynamic per-AP loop processing.

GUI layer (desktop)Core engine (GUI-agnostic)External systemsSafety gate

Launch Live Demo

Explore the diagrams

Campus TopologyNetwork hierarchy & device layersView Function CatalogEvery function, by moduleView Process & FlowOperator flow, strategies, state machineView MM CommandsEvery controller CLI command, explainedView Migration ActionsCommands by phase & user actionView Pre-Validate RequirementsInfrastructure & connectivity checklistView AP Image SelectionHow controllers choose which AOS-10 build for each modelView Migration Toolkit DemoInteractive in-browser simulationView Deployment Tool DemoTwo-phase net-new AP deployment simulationView

What makes it safe

Two processing strategies

Batch-by-model for large identical fleets, or a dynamic per-AP loop for mixed-model sites — both converge on one state machine.

Safety gates everywhere

Non-AOS-10-capable and down APs are skipped, never sent a convert command. An AP is only DONE once Central confirms a 10.x build.

GUI-agnostic core

A thin desktop GUI over a reusable, testable engine that can also be driven from a CLI or test suite.

Image filenames and AOS-10 version targets shown in the toolkit are placeholders — always confirm the recommended build for your Central instance on the HPE Support Center before a production run.

Migration Flowchart

Five-Phase Migration Process

Complete AOS-8 to AOS-10 migration workflow with safety checkpoints, automatic activation, and Central verification at every stage.

Phase 1

Inventory & Curation

Discovery & List Building

Connect to Mobility Master, list all campus APs, identify AOS-10-capable devices, build convert list

Key actions

Connect to MM/MD via SSH
Query AP database
Filter by device capability
Create convert list

Phase 2

Pre-flight Checks

Validation & Verification

Validate credentials with Aruba Central, confirm AP eligibility, flag incompatible devices

Key actions

Verify Central API credentials
Validate each AP eligibility
Check device connectivity
Flag non-compliant APs

Phase 3

Convert & Activate

Image Staging & Activation

Stage AOS-10 image on controller, activate conversion per AP or batch by model

Key actions

Download AOS-10 image
Stage image on controller
Trigger ap convert active
Batch by model or per-AP

Phase 4

Upgrade & Reboot

Automatic Reboot Cycle

AP automatically reboots with new AOS-10 image (controller-initiated, no manual commands)

Key actions

Monitor AP reboots
Track boot status
Wait for reconnection
Verify image loaded

Phase 5

Verify & Complete

Central Confirmation

Confirm AP joined Central with AOS-10 build, mark migration complete, rollback available

Key actions

Query Central inventory
Verify AOS-10 version
Confirm join status
Complete migration

Migration timeline

Each phase is gated by validation. Phases 1–3 require operator interaction; Phase 4 runs automatically via controller. Phase 5 confirms completion via Aruba Central. Rollback is always available until final verification.

Upcoming: REST API library operations

In the next release, add or update library objects, groups, and sites directly from a tooltip in Aruba Central via REST API — streamline bulk site/group mapping without manual Central UI navigation.