Operators send notification emails about Gateway migration to Administrators with Super User privileges. Plan your migration based on the notification email that you receive from your Operator.
To avoid any service disruption, ensure that you migrate to the new Gateway within the Migration Deadline mentioned in the notification email.
To migrate from a quiesced Gateway to a new Gateway, perform the following steps:
Prerequisites
Before you migrate the Edges and NSDs (if configured) from the quiesced Gateway to the new Gateway, ensure that you schedule a maintenance window as traffic may be disrupted during migration.
Procedure
In the SD-WAN service of the Enterprise portal, go to Service Settings > Gateway Migration. The list of quiesced Gateways appears.
Click Start for the quiesced Gateway from which you want to migrate to the new Gateway.
Note: Step 3 and 4 are only applicable if you have the NSDs configured from the quiesced Gateway. If there are no NSDs configured, go to
Step 5 to rebalance cloud Gateways and Edges that are connected to the quiesced Gateway.
Make the required configuration to all the NSDs that are configured through the quiesced Gateway.
Click the View IKE IPSec link to view a sample configuration for the NSD. Copy the template and customize it to suit your deployment.
Add the IP address of the SD-WAN Gateway (new Gateway IP) to each NSD configured for the quiesced Gateway.
For example, if you have configured an NSD for AWS, you must add the IP address of the new Gateway in the NSD configuration in the AWS instance.
After making the configuration changes to all the NSDs, select the The listed NSD site(s) have been configured check box, and then click Next.
Note: The Configure NSD Site(s) option is not available for NSDs configured automatically as well as for Gateways with Data Plane role that are not attached to any NSDs.
Select each NSD and click Switch Gateway to switch the traffic from the quiesced Gateway to the new Gateway.
In the Switch Gateway pop-up window, select the The NSD site has been configured check box to confirm that you have made the required changes to the remote-end NSD configuration.
Note: This confirmation is not applicable for NSDs configured automatically.
Click Switch Gateway.
It may take few minutes to verify the tunnel status. The IP address of the quiesced Gateway is replaced with the IP address of the new Gateway so that the traffic switches to the new Gateway. The
Migration Status changes to "NSD Tunnels are up and running" as shown in the following screenshot. If the Switch Gateway action fails, see
What to do When Switch Gateway Action Fails.
Click Next.
Note: The Switch Gateway option is not available for Gateways with Data Plane role that are not attached to any NSDs.
Rebalance Cloud Gateways (Primary or Secondary or Super Gateways) of all Edges or the required Edges that are connected to the quiesced Gateway so that the Edges get reassigned to the new Gateway. You can rebalance Gateways from the Configure > Edges page as well.
When rebalancing Super Gateways, all the Edges connected to the quiesced Gateway will be rebalanced. Rebalancing of selected Edges is not allowed.
Select the Edges that are connected to the quiesced Gateway and click
Rebalance Gateways to reassign Edges to the new Gateway.
Click Rebalance Gateway to complete the Gateway migration. The Edges connected to the quiesced Gateway are migrated to the new Gateway.
Click Finish.
Results
Go to the
Gateway Migration page and click
Review to review the migration steps, if required.
The Gateways that have been migrated remain in this page until the Migration Deadline assigned for the quiesced Gateway. After the Migration Deadline, you can view the history of migration events in the Monitor > Events page.
We’re sorry, but we can’t post your question to Communities right now. Try again later, or go directly to VMware Communities and post a question without us. We’ll understand.
Your question is posted to Communities. Wait patiently for an answer, or take a look now!
Product-specific community spaces are hosted in English. If you want to ask a question in another language, visit your global community instead.
Usernames can’t contain spaces or special characters. Try a username with numbers and letters instead.
Enter Username
Username Availablex Username Not Available
Delete
Translation Error
"
"?
Cookies
Broadcom and third-party partners use technology, including cookies to, among other things, analyze site usage, improve your experience and help us advertise. By using our site, you agree to our use of cookies as described in our Cookie Notice
Privacy Preference Center
Your Privacy
Strictly Necessary Cookies
Functional Cookies
Performance Cookies
Targeting Cookies
Your Privacy
When you interact with Broadcom as set forth in the Privacy Policy through visiting any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience.
Cookie PolicyPrivacy Policy
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in Broadcom’s systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Performance Cookies
These cookies allow Broadcom to count visits and traffic sources so Broadcom can measure and improve the performance of its site. They help Broadcom to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies Broadcom will not know when you have visited our site and will not be able to monitor its performance.
Targeting Cookies
These cookies may be set through Broadcom’s site by its advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.