Migrating an Aviatrix Global Transit Network to Next Gen Transit for AWS¶
This document assumes that you have deployed an Aviatrix Global Transit Network solution with Aviatrix Transit Gateway and VGW.
The following steps provide instructions to migrate a live Aviatrix Global Transit deployment to AWS Transit Gateway using Aviatrix TGW Orchestrator.
The objectives here are:
- No change to any on-prem network.
- No change to the connectivity between AWS VGW and on-prem. (either over DX or over Internet or both)
- Re-use AWS VGW deployed in Aviatrix Global Transit solution if possible.
- No change to existing VPC infrastructure.
- Minimum operation downtime.
- Create AWS Transit Gateway Follow Step 1 in TGW Orchestrator > Plan page.
- Create Security Domains If you have plans for custom security domains, follow Step 2 to create them. If you do not intend to build custom security domains, skip this step.
- Add/modify connection policies Follow Step 3 to build connection policies.
- Prepare Aviatrix Transit GW for TGW Attachment Follow Step 5.
- Attach Aviatrix Transit Gateway to TGW Follow Step 6. to complete the hybrid connection between your existing VGW and the TGW. At this point, VGW starts to advertise to Aviatrix Transit GW. Make sure you specify a different “AS” number for the BGP session of Aviatrix Transit GW connection to VGW. Also note that if Transit GW and VGW are in the same account and same VPC, VGW must be detached from the VPC.
- Detach Spoke GW Follow Step 7 to detach a Spoke GW from the existing Aviatrix Global Transit Network.
- Delete Spoke GW Go to Gateway on the main navigation tab, select the Spoke gateway and click Delete. If you have HA gateway, you will need to delete it first before the primary Spoke gateway.
- Attach Spoke VPC to Transit Gateway Follow Step 1 to attach a VPC to the corresponding security domain.
- Repeat the above step 6-8 for the remaining Spoke gateways.
The effective operation downtime for each Spoke VPC is the time between step 6-8 above.