Provides answers to frequently asked questions about SD-WAN migration, clarifying common concerns, troubleshooting issues, and offering solutions to support users throughout the migration process.
The Cisco SD-WAN Cloud fabric migration moves your existing Cisco SD-WAN Cloud-Pro environment to the Cisco SD-WAN Cloud environment, providing enhanced scalability, access to the latest features, and simplified management and analytics.
Operational benefits
-
Cisco SD-WAN Cloud simplifies operations: network administrators manage edge devices, while we handle operational responsibilities for SD-WAN Control Components.
-
The solution offers flexible cloud consumption, operational simplicity, and comprehensive analytics.
Migration preparation steps
-
Ask your Cisco representative about the required software version for your Cisco SD-WAN Cloud-Pro Control Components and upgrade them as specified.
-
Ask your Cisco representative about the required software version for your edge devices and upgrade them. Check device compatibility using the Cisco SD-WAN Control Components Compatibility Matrix.
-
Remove unreachable or unused edge device serial numbers from your current SD-WAN Manager.
-
Ensure all edge devices are configured with working NTP and DNS servers.
-
Do not configure static hostname-to-IP mapping for the SD-WAN Validator. Use the SD-WAN Validator fully-qualified domain name (FQDN) value in System Configuration.
-
Ensure you have out-of-band (OOB) direct access to edge devices, especially software-based devices, to address any connectivity issues during migration.
Frequently asked questions
Is an all-at-once migration required, or can it be performed in phases?
The migration is performed in a single maintenance window, which includes migration, post-migration checks, and recovery if needed.
How long does the migration process take?
Plan for at least 8 hours, but the exact time depends on the fabric size.
What are the communication channels during migration?
The primary channel is through a Technical Assistance Center (TAC) support case for coordination and support.
Who is responsible for upgrading Cloud-Pro Control Components and edge devices?
You are responsible for upgrades as part of preparation. Contact CloudOps for assistance if needed. After migration, we will handle future software upgrades for SD-WAN Control Components.
What information must I provide for the migration request?
-
Sales or Web Order details for the SD-WAN subscriptions
-
Name of the SD-WAN Control Component fabric and target region
-
Contact email address
-
SD-WAN Manager admin credentials for the existing environment
What precautions should be taken during migration?
Maintain OOB access to edge devices for troubleshooting. Update edge site firewall rules as needed to allow edge devices to communicate with the new public IP addresses of the Control Components.
What steps are required if I am using Enterprise certificates?
-
Renew certificates and migrate to PKI-based certificates for SD-WAN Control Components.
-
Install the root CA bundle on all edge devices.
How is configuration data transferred to the Cloud fabric?
Migration scripts extract all configuration data (policies, templates, and edge device serials) from your current SD-WAN Manager and restore it to the new environment.
Will edge devices automatically connect to the Cloud fabric after migration?
After the configuration is pushed, edge devices will authenticate and connect using previously configured policies.
Is SD-WAN Analytics onboarded during migration?
Analytics is automatically enabled during migration.
Will the controller profile from the Plug and Play (PnP) portal be created in the Cloud environment?
Organization names are used to create controller profiles and link your Smart Account and Virtual Account (SA and VA) using PnP external management features.
Will the data plane be affected during the change window?
Plan for downtime during the change window. Usually, the data plane remains unaffected, but unforeseen events may cause disruption.
Where do I log in after migration?
Continue using the Cisco Catalyst SD-WAN Portal and SD-WAN Manager dashboard via single sign-on (SSO).
How do I verify migration success?
You will receive notification from support. Log in to the Cisco Catalyst SD-WAN Portal, open Cisco SD-WAN Manager, and review your devices and configurations.
What should I do if edge device issues occur after migration?
Provide out-of-band (OOB) access to devices so Support can assist in re-establishing control connections.
How can I ensure user permissions and roles are correctly set up after migration?
Review role assignments in the Cisco Catalyst SD-WAN portal by navigating to as needed. Support can assist.
What preparation do I need to make in case of a rollback?
Maintain OOB access to edge devices to update the SD-WAN Validator DNS and organization (sp-org-name) values for fallback to the source Cisco SD-WAN Manager.
What risks are involved with this migration?
Risks include temporary loss of connectivity, device control issues, or incomplete migration. Strict procedures minimize these risks.
What features are enabled by default in a new Cloud fabric?
SD-WAN Analytics and Cloud OnRamp for SaaS are enabled by default, even if previously disabled. Software-Defined Application Visibility and Control (SD-AVC), SSO, and the Remote Software Upgrade Image Repository are also enabled.
Will my existing SD-WAN Analytics and reporting continue post-migration?
SD-WAN Analytics and reporting capabilities will remain intact.
What happens to my Cloud-Pro Control Components after migration?
After migration, the system deletes the Cisco SD-WAN Cloud-Pro Control Components.
Will CLI access to Control Components be available after migration?
CLI access is not available after migration.
What do I do when public IP addresses of Control Components change?
If public IP addresses of the SD-WAN Control Components change, update your firewall rules. You can request the public IP addresses of the SD-WAN Control Components from the SD-WAN Cloud Infra team via a TAC support case.