Sign in Request access

Home · Migrations · ArubaOS to Aruba CX

Switch migration / Scope first

ArubaOS
to Aruba CX

Translate an ArubaOS switch configuration toward Aruba CX for the supported scope. ArubaOS is source-only. Aruba CX is a switch platform, not a router. Every hosted switch result stays in NEEDS REVIEW.

Discuss this migration →Compare migration paths →

Account approval and feature support apply. A listed migration path does not certify every model, version or configuration.

The short answer

Is ArubaOS to Aruba CX supported?

Yes, as a switch path for approved accounts. The supported-vendors page lists ArubaOS to Aruba CX, IOS-XE or JunOS, with ArubaOS source-only. The supported scope includes VLANs, trunking and Layer 3 features. BGP on an Aruba CX target is partial. There is no router path to or from Aruba CX.

Define the handoff

What goes in.
What you review.

Source inputs

An ArubaOS switch configuration. ArubaOS is never a translation target.

Target output

An Aruba CX switch configuration for the supported scope, held in NEEDS REVIEW even after the emitted text is checked.

Path-specific boundaries

A listed switch path is not complete vendor coverage. BGP on Aruba CX is partial. Engineers still test the device.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

VLANs and trunks

Confirm VLAN IDs, access and trunk ports, and native VLAN behavior on the CX candidate.

REVIEW 02

Aggregation

Review link-aggregation and trunk membership. Names and IDs may not carry over unchanged.

REVIEW 03

Layer 3

Review SVIs and routed interfaces that are in the supported scope. Missing L3 context stays a finding.

REVIEW 04

Partial BGP

If the CX target has BGP, treat it as partial. Do not read a switch result as a finished routing design.

Each result's status comes from deterministic checkpoints (CP0–CP4) and, on firewall paths, behavior checks (BC1–BC4); AI can explain findings but never sets status. These are review areas, not a guarantee that every construct in them is automated. Unsupported features, missing captures and conditional behavior remain part of the engineering review.

Every hosted router and switch result is held in NEEDS REVIEW for engineer review, even after the emitted configuration text is checked.

Questions

Common questions

Does every ArubaOS switch feature convert?

No. The page states the supported scope: VLANs, trunking and Layer 3 features. Anything outside that stays for engineer review.

Can Aruba CX be translated back to ArubaOS?

No. ArubaOS is source-only. Aruba CX can be a source and a target for other supported switch paths.

Why is the result NEEDS REVIEW?

Every hosted router and switch result is held in NEEDS REVIEW for engineer review, even after the emitted configuration text is checked.

Plan the next step

Bring the details
that make your migration different.

Bring the ArubaOS and AOS-CX versions, and say whether BGP or only L2 and SVIs are in scope.

Discuss your scope →ArubaOS to Cisco →