Sign in Request access

Home · Migrations · Cisco IOS-XE to Junos

Router migration / Scope first

Cisco IOS-XE
to Juniper JunOS

Prepare the source, review the translated configuration and validate the behavior that matters to your network. Start with the device, software version and features in scope.

Discuss this migration →Open the platform →

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

Define the handoff

What goes in.
What you review.

Source inputs

An IOS-XE router configuration, software version and the target JunOS platform. Include interface and routing-instance requirements.

Target output

JunOS router configuration output for the supported scope, with findings for review.

Path-specific boundaries

This page concerns router migration. Complex routing and VRF forwarding need target-environment testing; it is not a blanket statement about JunOS switching or SRX firewall support. Every hosted router and switch result is held in NEEDS REVIEW for engineer review, even after the emitted configuration text is checked. Engineer review of NEEDS REVIEW and BLOCKED findings is required before deployment.

Scope the review

Check the behavior,
not just the syntax.

REVIEW 01

Interfaces and addressing

Confirm the intended behavior, supported scope and target-platform requirements.

REVIEW 02

Routing-instance and VRF placement

Confirm the intended behavior, supported scope and target-platform requirements.

REVIEW 03

Routing protocols and policy references

Confirm the intended behavior, supported scope and target-platform requirements.

REVIEW 04

Route selection, filtering and operational dependencies

Confirm the intended behavior, supported scope and target-platform requirements.

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.

See the current product

Explore the workflow.

View dated product captures and a clearly labeled synthetic verification example. A screenshot of an interface does not establish acceptance of this migration path.

See the product tour →

Understand your result

Read the findings and their limits alongside the output. Address blockers, validate device acceptance and test affected traffic before seeking deployment approval.

Read the result guide →

Questions

Common questions

Is this a router path or a switch path?

Router. Cisco IOS-XE and Juniper Junos routers. There is no direct IOS-XE switch to Junos switch path.

What routing is out of scope?

EIGRP is not translated to Junos. An EIGRP-to-OSPF proposal is opt-in only. Coverage of other features is whatever the findings report.

What status should you expect?

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.

Source and target models, software versions, critical features and the change window help establish a realistic scope.

Discuss your scope →Compare migration paths →