Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Enterprise Router/ Best Practices/ Using Enterprise Router to Migrate the Network Set Up Through Direct Connect (Global DC Gateway)/ Procedure for Using Enterprise Router to Migrate the Network Set Up Through Direct Connect

Procedure for Using Enterprise Router to Migrate the Network Set Up Through Direct Connect

Updated on 2024-11-21 GMT+08:00

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.

    When creating the enterprise router, enable Default Route Table Association and Default Route Table Propagation. For details, see Table 4.

    For details, see Creating an Enterprise Router.

  2. Create a VPC attachment er-attach-VPC-X to attach the service VPC to the enterprise router.

    Do not enable Auto Add Routes and manually add routes with destinations set to the large CIDR block in the VPC route table.

    For details, see Creating VPC Attachments for the Enterprise Router.

  3. In the enterprise router route table, check the route points to the VPC attachment.

    In this example, Default Route Table Association and Default Route Table Propagation are enabled for the enterprise router, and routes with destinations set to VPC CIDR blocks are automatically added when you attach the VPCs to the enterprise router.

    NOTICE:

    If Default Route Table Propagation is not enabled when creating the enterprise router, you need to manually add routes with destinations set to the VPC CIDR blocks to the enterprise router route table. For details, see Creating a Static Route.

    For enterprise router route details, see Table 1 and Table 3.

    To view enterprise routes, see Viewing Routes.

  4. In the VPC route table, add a route destined for the large CIDR block with the enterprise router as the next hop.

    For VPC route details, see Table 1 and Table 2.

    In this example, the large CIDR block is 172.16.0.0/15, and the next hop is the enterprise router.

    For details, see Adding Routes to VPC Route Tables.

Step 2: Attach Global DC Gateway DGW-B01 to the Enterprise Router

  1. Create a global DC gateway DGW-B01.

    For details, see Creating a Global DC Gateway.

  2. Delete virtual interface VIF-A01 from virtual gateway VGW-A on the on-premises network device and the Direct Connect console in sequence:

    1. Log in to the on-premises network device and delete the configuration of VIF-A01.

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

    2. Delete virtual interface VIF-A01 on the Direct Connect console.

      For details, see Deleting a Virtual Interface.

      After the virtual interface is deleted, the system route pointing to VGW-A and destined for the local and remote gateways of VIF-A01 will be deleted from the VPC route table. For VPC route details, see Table 2.

      In this example, the route whose destination is 10.0.0.0/30 and next hop is the virtual gateway will be automatically deleted.

  3. Create a global DC gateway attachment for the enterprise router.

    1. On the Direct Connect console, perform the following operations:
      1. Create virtual interface VIF-B01.
      2. Attach the global DC gateway to the enterprise router.

      For details, see Creating a Global DC Gateway.

    2. On the Enterprise Router console, view the global DC gateway attachment created for the enterprise router.

      For details, see Viewing Details About an Attachment.

      If the status of the global DC gateway attachment is Normal, the attachment has been created.

      Default Route Table Association and Default Route Table Propagation are enabled when you create the enterprise router. After the global DC gateway is attached to the enterprise router, Enterprise Router will automatically:
      • Associate the global DC gateway attachment with the default route table of the enterprise router.
      • Propagate the global DC gateway attachment to the default route table of the enterprise router. The routes to the on-premises data center are propagated to the route table.

        You can view routes to the on-premises data center in the route table of the enterprise router only after taking the following steps.

  4. (Optional) Configure the on-premises network device to enable the on-premises data center to access cloud resources through the new virtual interface VIF-B01 or a specified virtual interface.

    • If virtual interface VIF-B01 uses BGP routing, the on-premises data center can access cloud resources through VIF-B01 after 3 is complete. In this case, skip this step.
    • If virtual interface VIF-B01 uses static routing, the on-premises data center can access cloud resources through VIF-B01 only after the current step is complete.
    • If you do not want the traffic from the on-premises data center to pass through virtual interface VIF-B01, take this step to configure a specified virtual interface.

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.

    For VPC route details, see Table 2.

    In this example, the route destination is 172.16.0.12/32 and next hop is the enterprise router.

    For details, see Adding Routes to VPC Route Tables.

  2. Create an ECS in the VPC subnet that needs to communicate with the on-premises data center.

    For more resource details, see Table 4.

    For details, see Purchasing a Custom ECS.

  3. Verify communications between the VPC and on-premises data center.

    Multiple methods are available for logging in to an ECS. For details, see Logging In to an ECS.

    ping <IP-address-of-an-on-premises-server>

    Add the IP address of an on-premises server to the VPC route table and run the following command:

    ping 172.16.0.12

    If information similar to the following is displayed, VPC-X can communicate with the on-premises data center through the enterprise router:
    [root@ecs-X ~]# ping 172.16.0.12
    PING 172.16.0.12 (172.16.0.12) 56(84) bytes of data.
    64 bytes from 172.16.0.12: icmp_seq=1 ttl=64 time=0.849 ms
    64 bytes from 172.16.0.12: icmp_seq=2 ttl=64 time=0.455 ms
    64 bytes from 172.16.0.12: icmp_seq=3 ttl=64 time=0.385 ms
    64 bytes from 172.16.0.12: icmp_seq=4 ttl=64 time=0.372 ms
    ...
    --- 172.16.0.12 ping statistics ---

  4. Delete the route and ECS used for verifying communications.

    1. Delete the route from the VPC route table.

      To delete a route, refer to Deleting a Route.

    2. Delete the ECS.

      To delete an ECS, refer to How Can I Delete or Restart an ECS?

Step 4: Attach Global DC Gateway DGW-B02 to the Enterprise Router

  1. Create a global DC gateway DGW-B02.

    For details, see Creating a Global DC Gateway.

  2. Delete virtual interface VIF-A02 from virtual gateway VGW-A on the on-premises network device and the Direct Connect console in sequence:

    1. Log in to the on-premises network device and delete the configuration of VIF-A02.

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

    2. Delete virtual interface VIF-A02 on the Direct Connect console.

      For details, see Deleting a Virtual Interface.

      After the virtual interface is deleted, the two routes pointing to virtual gateway VGW-A are deleted from the VPC route table. For VPC route details, see Table 2.
      • The system route whose destination is the local and remote gateways of virtual interface VIF-A02.

        In this example, the route whose destination is 10.1.0.0/30 and next hop is the virtual gateway will be automatically deleted.

      • The system route destined for the on-premises data center.

        In this example, the route whose destination is 172.16.0.0/16 and next hop is the virtual gateway will be automatically deleted.

  3. Create a global DC gateway attachment for the enterprise router.

    1. On the Direct Connect console, perform the following operations:
      1. Create virtual interface VIF-B02.
      2. Attach the global DC gateway to the enterprise router.

      For details, see Creating a Global DC Gateway.

    2. On the Enterprise Router console, view the global DC gateway attachment created for the enterprise router.

      For details, see Viewing Details About an Attachment.

      If the status of the global DC gateway attachment is Normal, the attachment has been created.

      Default Route Table Association and Default Route Table Propagation are enabled when you create the enterprise router. After the global DC gateway is attached to the enterprise router, Enterprise Router will automatically:
      • Associate the global DC gateway attachment with the default route table of the enterprise router.
      • Propagate the global DC gateway attachment to the default route table of the enterprise router. The routes to the on-premises data center are propagated to the route table.

        You can view routes to the on-premises data center in the route table of the enterprise router only after taking the following steps.

  4. (Optional) Configure the on-premises network device to enable the on-premises data center to access cloud resources through the new virtual interface VIF-B02 or a specified virtual interface.

    • If virtual interface VIF-B02 uses BGP routing, the on-premises data center can access cloud resources through VIF-B02 after 3 is complete. In this case, skip this step.
    • If virtual interface VIF-B02 uses static routing, the on-premises data center can access cloud resources through VIF-B02 only after the current step is complete.
    • If you do not want the traffic from the on-premises data center to pass through virtual interface VIF-B02, take this step to configure a specified virtual interface.

Step 5: Configure the Working Mode of the Connections

  1. Configure a route policy to make the two connections to work in load balancing or active/standby mode based on site requirements.

Step 6: Delete the Virtual Gateway

NOTICE:

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

  1. Delete virtual gateway VGW-A.

    For details, see Deleting a Virtual Gateway.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback