Customer Impact When a VMware SD-WAN Gateway is Migrated
search cancel

Customer Impact When a VMware SD-WAN Gateway is Migrated


Article ID: 312336


Updated On:




VMware SD-WAN Gateway migration occurs when there is a need to move the customers to an improved Gateway to optimize the performance and resource usage. With the migration, the customers VMware SD-WAN Edges are moved from their current Gateway to a new Gateway.

A customer should expect to receive a Maintenance Incident Notification (MIN) prior to the Gateway migration.


Generally, migration occurs with the following conditions and impacts:
- Normally the migration of a VMware SD-WAN Gateway is for the Super Gateway or Non SD-WAN Destinations (NSD) via Gateway sites.
- When reassigning a Super Gateway we do not expect any traffic impact.
- Migration for a NSD via Gateway must be done in one of two ways depending on the Orchestrator Release:
- On an Orchestrator using 4.3.x or earlier, the NSD via Gateway migration is done with the customer's approval and the assistance of the Support Team during a maintenance window .
- On an Orchestrator using 4.5.x or later, the NSD via Gateway may be migrated by the partner or customer using the new self-service feature.
- If a Gateway used as either a Primary or Secondary Gateway needs to be migrated to a different Gateway instance, the tunnels to the old Gateway will be torn down along with the routes and any flows associated with these tunnels. Any existing TCP connections with the Primary Gateway tunnel need to be established with the new Gateway, which means that connection-oriented communications like SSH and FTP would be reconnected. Voice calls would be similarly impacted.
- If any of SAAS infrastructure needs the IP address of the incoming requests then new Gateway IP address needs to be added.
- If the customer includes the Gateway IP address for any internal "Allow Lists" for firewalls or similar applications, they would need to add the migrated Gateway IP address to that Allow List.