Help & DocumentationCloud Connect NetworkBest PracticesMigrate a Peering Connection-enabled VPC to CCN

Migrate a Peering Connection-enabled VPC to CCN

Last updated: 2020-02-24 12:13:10

PDF

If your VPC already uses peering connection, you can use the following steps to migrate to cloud networking:

  1. Create a cloud networking instance.
  2. Connect the VPC that has already used the peering connection to the cloud, Associate.
  3. Check cloud networking Route table.
  4. In Route table, the subnet of VPC, disable peering connection routing and enable cloud networking routing.

Operation Examples

Your VPC1 and VPC2 have been interconnected through peering connection, and now you need to migrate to cloud networking to interconnect with other VPC's entire network.

  • VPC1 (Guangzhou): 192.168.0.0Unix 16, subnet 192.168.0.0Unix 24, subnet BREX 192.168.1.0 Unix 24.
  • VPC2 (Shanghai): 10.0.0.0Compact 16, subnet CRV 10.0.0.0Unix 24, subnet DRO 10.0.1.0 Unix 24.

You need to complete the following steps:

  1. Create, an example of cloud networking (if you already have it, you don't need it). For more information, please see New CCN instance .
  2. Connect VPC1 and VPC2 to the corresponding cloud networking instance Associate. For more information, please see Associate network example .
  3. After Associate, in the Route table of the cloud networking instance, you can see Routing policy of each subnet whose destination end is VPC1 and VPC2 (in this case, there are 4 Routing policy pointing to subnets A, B, C, D, respectively).
  4. Enter Route table in each subnet of VPC1 and VPC 2, check the routing status (cloud-connected routes default deliver to the subnet routing table, but not necessarily take effect), and complete the migration by disabling and enabling routes.

Information note

  • Case 1: if there is no conflict between deliver's route and the existing peering connection, the cloud networking route takes effect. You only need to disable the original peering connection route.
  • Case 2: cloud networking automatic deliver routing conflicts with existing peering connections, then cloud networking routing is invalid by default and cannot be directly enabled. You need to [disable] Routing policy whose next hop is peering connection, and then [enable] Routing policy who is connected to the cloud in the next hop.

Notes:
The deactivation operation will cause a brief interruption to your business. Resume's time depends on the time when you enable cloud network routing.

  • Case 3: if there is an inclusion conflict between deliver's route and the existing peering connection, the cloud network route is invalid by default, but you can [enable] the next hop of the cloud network Routing policy. When enabled, it will be based on the longest Mask matching principle, repost. If the original peering connection is no longer used after migration, it is recommended that you [disable] Routing policy whose original next hop is peering connection.