Sign in Request access

Home · Migrations · Juniper JunOS to Aruba CX

Switch migration / Scope first

Juniper JunOS
to Aruba CX

Translate a Junos switch configuration, in configuration mode or display set, toward Aruba CX. This is not the Junos router to IOS-XE path. BGP on an Aruba CX target is partial. The 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

What Junos switch scope moves to Aruba CX?

The supported-vendors page lists VLANs, trunking, aggregated Ethernet and Layer 3 interfaces, to and from Aruba CX, and from ArubaOS. There is no direct Cisco IOS-XE switch to Junos switch path. If you need IOS-XE, go CX to IOS-XE or IOS-XE to CX, not through a claimed direct Junos switch hop.

Define the handoff

What goes in.
What you review.

Source inputs

A Junos switch configuration in configuration mode or display set. A Junos router config belongs on the router guides.

Target output

An Aruba CX switch candidate. BGP on that target is partial. The job is held in NEEDS REVIEW after the text is checked.

Path-specific boundaries

Aruba CX is not a router. SRX is not supported.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

VLANs and trunks

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

REVIEW 02

Aggregated Ethernet to LAG

Review AE membership against CX link aggregation. Expect explicit renames in the findings when IDs collide.

REVIEW 03

Layer 3

Review VLAN interfaces and addresses that are in the supported scope.

REVIEW 04

Partial BGP

Treat BGP on the Aruba CX target as partial. Do not describe the result as complete.

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

Is this the Junos to Cisco router migration?

No. Junos to Cisco IOS-XE for routers has its own guide. This page is a switch path to Aruba CX.

Why might LAG names change?

Aggregated interfaces sometimes have to be renamed so they fit the target. The findings should show the rename. Accept it in review rather than assuming the original name survived.

What is the result status?

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 Junos version, whether the file is a switch, and whether BGP on CX is in scope.

Discuss your scope →Aruba CX to Junos →