When a Transit Gateway (TGW) is configured on a CloudHub 1.0 VPC, some users may be concerned that the following issues could arise after migrating to a CloudHub 2.0 Private Space using the VPC Upgrade Tool:
・The CIDR blocks of the CloudHub 1.0 VPC and the destination CloudHub 2.0 Private Space overlap.
・The TGW route table cannot distinguish between the two destinations.
・Routing conflicts occur.
However, based on the actual behavior of the VPC Upgrade Tool, these concerns do not apply.
When migrating from a CloudHub 1.0 VPC to a CloudHub 2.0 Private Space using the VPC Upgrade Tool, CIDR overlap does not occur.
The VPC Upgrade Tool performs the migration by reusing the same VPC and CIDR block provided by the infrastructure vendor.
As a result The CIDR block of the CloudHub 1.0 VPC is carried over directly to the CloudHub 2.0 Private Space.
Therefore, even when reviewing the TGW route table after migration, no CIDR overlap occurs and no routing conflicts arise.
Related Documentation
https://docs.mulesoft.com/cloudhub/vpc-upgrade
005389674

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.