VMWare SASE Gateway Migration to GCP
Article ID: 369471
Updated On:
Products
Issue/Introduction
VMware SASE plans to migrate the Velocloud Gateways from select SASE PoPs to GCP PoPs in the same region. This article includes some Frequently Asked Questions (FAQs) and answers related to this migration process.
Resolution
- Which are the PoP locations that are being migrated?
The below are the list of PoPs which will be migrated:
|
SASE PoP to be migrated |
GCP PoPs |
|
Paris (cdg3) |
Paris (lfpg1) |
|
London - 2(lhr5) |
London(egll1) |
|
Sydney(syd2) |
Sydney(yssy1) |
|
Toronto(yyz1) |
Toronto(cyyz1) |
|
Milan(mxp1) |
Milan(limc1) |
|
Tel Aviv(tlv1) |
Tel Aviv(llbg1) |
|
Warsaw(waw1) |
Warsaw(epwa1) |
|
Amsterdam(ams3) |
Amsterdam(ehgg1) |
|
Hong Kong(hkg4) |
Hong Kong(vhhh1) |
|
Jakarta(jkt1) |
Jakarta(wiii1) |
|
Melbourne(mel3) |
Melbourne(ymml1) |
|
Mumbai(bom2) |
Mumbai(vabb1) |
|
Osaka(itm2) |
Osaka(rjbb1) |
|
São Paulo(sao2) |
São Paulo(sbgr1) |
|
Zurich(zrh1) |
Zurich(lszh1) |
|
Seoul(icn1) |
Seoul(rksi1) |
|
Johannesburg(jnb3) |
Johannesburg(faor1) |
- Will the Gateways with NSDs and without NSDs be migrated at the same time?
Initially, the Gateway migrations will involve the Gateways without NSDs. Once this is complete, migration of Gateways with NSDs will start.
- Are there any recommendations specific to NSD via Gateway?
It is recommended that Enterprises already have a Redundant NSD Gateway configured. If the Redundant NSD Gateway is not configured, enable this prior to the NSD Migration.
Feedback
