Source inputs
The Cisco switch configuration, source hardware/software details and intended Aruba CX model/version. Include port and uplink mapping.
Switch migration / Scope first
Cisco IOS-XE
to Aruba CX
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
Aruba CX configuration output for the supported scope, with manual steps and findings for review.
Path-specific boundaries
Switch families and software versions differ. Physical stacking, chassis features, hardware limits and port security require target-specific review; no universal one-to-one hardware conversion is promised.
Scope the review
Check the behavior,
not just the syntax.
VLANs, tagged/untagged ports and trunks
Confirm the intended behavior, supported scope and target-platform requirements.
Link aggregation and uplink mapping
Confirm the intended behavior, supported scope and target-platform requirements.
Spanning tree and port protections
Confirm the intended behavior, supported scope and target-platform requirements.
Access policies, management access and hardware-specific features
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.