This topic describes how to migrate a VPC from a peering connection in Express Connect to a Cloud Enterprise Network (CEN) instance. CEN allows you to enable communication between VPCs and between VPCs and on-premises data centers by using internal network connections. CEN automatically learns and distributes routes, and quickly adapts to network changes. This improves the quality of cross-network communication.
If you want to migrate a VPC to an existing CEN instance, make sure that the overlapping routing function is enabled.
To migrate a VPC from a peering connection to a CEN instance, perform the following steps:
- Log on to the CEN console.
- On the Instances page, find the required CEN instance and click its ID.
- On the Networks tab, click Attach Network and attach the VPC that you want to migrate. For more information, see Attach networks.
- If you want to communicate across regions, purchase a bandwidth plan and configure
the bandwidth for the communication.
For more information, see Set a cross-region bandwidth.
- If you have added routes that point to high-availability virtual IP addresses (HAVIPs) or IP addresses of ECS instances and VPN gateways, go to the VPC console and advertise these routes to the CEN instance based on your connection requirements.
- Log on to the CEN console and click the ID of the required CEN instance. Then, click the Routes tab to view the route information. After you attach the VPC to the CEN instance,
make sure that the routes do not conflict.
The static routes that are configured in the peering connection have higher priorities than the dynamic routes of the CEN instance. Specifically, if a static route is configured in the peering connection, CEN does not learn routes that are more specific than the static route and have the same destination as the static route. We recommend that you split static routes of the peering connection and delete them after CEN learns the routes. This ensures smooth migration.In the following figure, the route to 172.16.1.0/24 in the CEN instance is more specific than the route to 172.16.0.0/16 in the peering connection. Therefore, the two routes are in conflict.
- If you can tolerate a transient network interruption during the migration, delete
the route to 172.16.0.0/16 in the VPC console. Then, the route in the CEN instance
automatically takes effect.
The duration of the network interruption increases as the number of CEN routes increases. For important business scenarios, we recommend that you use the following method to smoothly migrate the VPC.
- If you want to smoothly migrate the VPC, split the route in the peering connection
into routes more specific than the route to 172.16.1.0/24 in the CEN instance. For
example, split the route to 172.16.0.0/16 in the peering connection into two routes,
one to 172.16.1.0/25 and the other to 172.16.1.128/25.
- Log on to the VPC console and find the route table to which the route you want to split belongs.
- Click Add Route Entry to add two routes in which the destination CIDR blocks are 172.16.1.0/25 and 172.16.1.128/25 and the next hops are the router interface of the peering connection.
- Find the route to 172.16.0.0/16 and click Delete in the Actions column.
- Click Refresh to check whether the routes in the CEN instance take effect.
- After the routes in the CEN instance take effect, delete the routes to 172.16.1.0/25 and 172.16.1.128/25. The smooth migration is complete.
- If you can tolerate a transient network interruption during the migration, delete the route to 172.16.0.0/16 in the VPC console. Then, the route in the CEN instance automatically takes effect.