Sign in Request access

Home · Migrations · Aruba CX to Juniper JunOS

Switch migration / Scope first

Aruba CX
to Juniper JunOS

Translate an Aruba CX switch configuration toward Junos. Aruba CX is a switch platform. There is no router path to or from Aruba CX, and no direct Cisco IOS-XE switch to Junos switch path.

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

Which switch vendors connect to Junos?

The supported-vendors page lists Cisco IOS-XE, Aruba CX and Junos as the switch triangle, with one gap: no direct IOS-XE switch to Junos switch path. Aruba CX and Junos do translate both ways for the supported scope. ArubaOS can be a source into Junos, not a target. Every hosted switch result stays in NEEDS REVIEW.

Define the handoff

What goes in.
What you review.

Source inputs

An Aruba CX switch configuration and software version.

Target output

A Junos switch candidate for VLANs, trunking, aggregated Ethernet and Layer 3 interfaces in the supported scope.

Path-specific boundaries

BGP on Aruba CX is partial when CX is the target. This page targets Junos. Juniper SRX is not supported. Do not treat the candidate as complete vendor coverage.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

VLANs and access ports

Confirm VLAN IDs and access ports in the Junos candidate.

REVIEW 02

Trunks and aggregated Ethernet

Review LAG and trunk membership. A rename is a finding to accept, not a silent success.

REVIEW 03

Layer 3

Review routed VLAN interfaces that the findings mark as translated.

REVIEW 04

Held status

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

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

Can I convert this Aruba CX config to a Junos router?

No. Aruba CX has no router path. IOS-XE to Junos router is a separate guide.

Does the reverse path exist?

Yes. Junos to Aruba CX is a separate switch guide, also held in NEEDS REVIEW.

Is BGP fully translated onto Junos from CX?

Do not assume that. The published limit is that BGP on an Aruba CX target is partial. This page's target is Junos. Unstated features stay out of the claim.

Plan the next step

Bring the details
that make your migration different.

Bring the AOS-CX version and the Junos switch version. Say if the device is an SRX. SRX is not supported.

Discuss your scope →Junos to Aruba CX →