Help Center/ Enterprise Router/ Best Practices/ Using Enterprise Router to Migrate the Network Set Up Through Direct Connect/ Process of Using Enterprise Router to Migrate the Network Set Up Through Direct Connect
Updated on 2024-06-27 GMT+08:00
View PDF
Share

Process of Using Enterprise Router to Migrate the Network Set Up Through Direct Connect

Table 1 describes the process of migrating a hybrid cloud network by replacing Direct Connect with Enterprise Router.

Table 1 Process of migrating a network from Direct Connect to Enterprise Router

Step

Description

Step 1: Create an Enterprise Router and a VPC Attachment
  1. Create an enterprise router ER-X in the same region as the service VPC.
  2. Create a VPC attachment er-attach-VPC-X to attach the service VPC to the enterprise router.
  3. Verify that routes are automatically added to the enterprise router route table.
  4. In the VPC route table, add a route destined for the large CIDR block through the enterprise router.

Step 2: Create a Virtual Gateway Attachment
  1. Create a virtual gateway VGW-B and attach it to the enterprise router.

    VGW-B is used to replace VGW-A after the migration.

  2. Delete virtual interface VIF-A02 associated with virtual gateway VGW-A.

    Before deleting virtual interface VIF-A02, complete configuration on the on-premises network device to ensure that traffic does not pass through this virtual interface.

  3. Create virtual interface VIF-B02 for virtual gateway VGW-B. VIF-B02 is used to replace VIF-A02 after the migration.
  4. Complete configuration on the on-premises network device to ensure that traffic can pass through virtual interface VIF-B02.

Step 3: Verify Communications Between the VPC and On-Premises Data Center Through the Enterprise Router
  1. In the VPC route table, add a route destined for any on-premises server to verify communications between the VPC and on-premises data center.
  2. Create an ECS in the VPC subnet that needs to communicate with the on-premises data center, log in to the ECS, and run the ping command.
  3. Delete the route and ECS used for verifying communications.

Step 4: Complete Migration
  1. Delete virtual interface VIF-A01 associated with virtual gateway VGW-A.

    Before deleting virtual interface VIF-A01, complete configuration on the on-premises network device to ensure that traffic does not pass through this virtual interface.

  2. Create virtual interface VIF-B01 for virtual gateway VGW-B. VIF-B01 is used to replace VIF-A01 after the migration.
  3. Complete configuration on the on-premises network device to ensure that traffic can pass through virtual interface VIF-B01.

Step 5: Delete the Original Virtual Gateway

When the on-premises data center can access VPC-X using the enterprise router, delete virtual gateway VGW-A.