Source inputs
A JunOS router export, source and target software versions and the intended interface/VRF mapping.
Router migration / Scope first
Juniper JunOS
to Cisco IOS-XE
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.
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.
Target output
Cisco IOS-XE router output for supported scope, with findings for review.
Path-specific boundaries
Configuration checks do not establish end-to-end routing or VRF forwarding behavior. Confirm feature support on the exact target and test the affected paths before cutover.
Scope the review
Check the behavior,
not just the syntax.
Interfaces, addressing and routing instances
Confirm the intended behavior, supported scope and target-platform requirements.
VRF placement and route import/export intent
Confirm the intended behavior, supported scope and target-platform requirements.
Routing policy and object references
Confirm the intended behavior, supported scope and target-platform requirements.
Protocol behavior and operational dependencies
Confirm the intended behavior, supported scope and target-platform requirements.
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 →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.