- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
-
Routing Control
-
Route Policies
- Route Policy Overview
- Creating a Route Policy
- Associating a Route Policy with an Enterprise Router
- Changing the Route Policy Associated with an Enterprise Router
- Disassociating a Route Policy from an Enterprise Router
- Modifying a Route Policy
- Viewing a Route Policy
- Deleting a Route Policy
- Adding a Policy Node to a Route Policy
- Modifying a Policy Node in a Route Policy
- Exporting Policy Nodes in a Route Policy
- Viewing a Policy Node in a Route Policy
- Deleting a Policy Node from a Route Policy
-
IP Prefix Lists
- IP Prefix List Overview
- Creating an IP Prefix List
- Modifying the Name of an IP Prefix List
- Viewing an IP Prefix List
- Deleting an IP Prefix List
- Adding a Prefix Rule to an IP Address Prefix List
- Modifying an IP Prefix Rule in an IP Prefix List
- Exporting Prefix Rules in an IP Prefix List
- Viewing a Prefix Rule in an IP Prefix List
- Deleting a Prefix Rule from an IP Prefix List
-
AS_Path Lists
- AS_Path List Overview
- Creating an AS_Path List
- Modifying the Name of an AS_Path List
- Viewing an AS_Path List
- Deleting an AS_Path List
- Adding an AS_Path Filter to an AS_Path List
- Exporting AS_Path Filters in an AS_Path List
- Viewing an AS_Path Filter in an AS_Path List
- Deleting an AS_Path Filter from an AS_Path List
-
Route Policies
- Sharing
- Flow Logs
- Monitoring and Auditing
- Tags
- Quotas
-
Best Practices
- Summary on Enterprise Router Best Practices
- Connecting VPCs Across Regions Using Enterprise Router and Central Network
- Using Enterprise Router to Isolate VPCs in the Same Region
- Using a Third-Party Firewall to Protect VPCs Connected by Enterprise Routers
- Enabling an On-Premises Data Center to Access Service VPCs Using an Enterprise Router and Transit VPC
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect Global DC Gateway
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Virtual Gateway)
- Allowing VPCs to Share an EIP to Access the Internet Using Enterprise Router and NAT Gateway
- Using Enterprise Router to Migrate the Network Set Up Through VPC Peering
- Using Enterprise Router to Migrate the Network Set Up Through Direct Connect (Global DC Gateway)
- Using Enterprise Router and Central Network to Migrate the Network Set Up Through a Cloud Connection
- API Reference
- FAQs
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Interconnecting with CTS
- Permissions Management
- Tags
- Quotas
- FAQ
- Change History
-
User Guide (Ankara Region)
- Service Overview
- Getting Started
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Quotas
- FAQ
- Change History
- API Reference (Ankara Region)
-
User Guide (ME-Abu Dhabi Region)
- General Reference
- Scenario 1: Multiple VPCs communicating or not communicating with each other on the cloud, but communicating with the on-premises data center through a Direct Connect connection
- Scenario 2: Dynamic switchover between Direct Connect connections
- Scenario 3: Active/Standby Direct Connect and VPN connections
- Scenario 4: Cross-cloud, cross-region highly reliable backbone network
- Scenario 5: Building a border firewall between VPCs
Show all
Copied.
When to Use Enterprise Routers
- Scenario 1: Multiple VPCs communicating or not communicating with each other on the cloud, but communicating with the on-premises data center through a Direct Connect connection
- Scenario 2: Dynamic switchover between Direct Connect connections
- Scenario 3: Active/Standby Direct Connect and VPN connections
- Scenario 4: Cross-cloud, cross-region highly reliable backbone network
- Scenario 5: Building a border firewall between VPCs
Scenario 1: Multiple VPCs communicating or not communicating with each other on the cloud, but communicating with the on-premises data center through a Direct Connect connection

Customer Requirements |
Multiple service networks communicate or do not communicate with each other on the cloud but communicate with the on-premises data center. Suppose you require three VPCs for running the workloads on the public cloud, and the three VPCs (services A, B, and C) need to access public services in VPC 4 and your on-premises data center. |
---|---|
Pain Points |
|
Benefits of Using Enterprise Routers |
|
Best Practice |
Customer Requirements |
Some services run on the public cloud and some in the on-premises data center. Two independent high-bandwidth Direct Connect connections are deployed between the public cloud and the data center to enable communication between them. |
---|---|
Pain Points |
Two Direct Connect connections are independent of each other and cannot work in load-sharing or active/standby mode. |
Benefits of Using Enterprise Routers |
Direct Connect connections are connected to the enterprise router.
|
Best Practice |
Scenario 3: Active/Standby Direct Connect and VPN connections

Customer Requirements |
You are running workloads in your on-premises data center and on the public cloud. A single Direct Connect connection connects your on-premises data center to the cloud, which cannot ensure reliability. |
---|---|
Pain Points |
You cannot afford another Direct Connect connection. |
Benefits of Using Enterprise Routers |
In this example, there are two connections, one Direct Connect connection and a VPN connection. Enterprise Router, Direct Connect, and VPC are used to build a hybrid cloud. When the Direct Connect connection becomes faulty, the VPN connection takes over to ensure that connectivity is not interrupted. |
Best Practice |
Scenario 4: Cross-cloud, cross-region highly reliable backbone network
Change the enterprise router on the other cloud shown in Figure 4 to its actual service name of the other cloud.
Customer Requirements |
To improve service DR capabilities, enterprises often run workloads on multiple public clouds. Each public cloud spans across multiple regions for nearest access. They do not have their own backbone networks and use the backbone networks of the public clouds for multi-cloud, multi-region interconnection. Suppose you are running workloads in regions of both Huawei Cloud and another cloud service provider. The two public clouds communicate with each other through private lines of different carriers. Different regions of the same public cloud communicate with each other through the backbone networks (central networks provided by Cloud Connect). |
---|---|
Pain Points |
|
Benefits of Using Enterprise Routers |
The public clouds are connected through private lines, and different regions in the same public cloud are connected through the central network.
|
Best Practices |
Connecting VPCs Across Regions Using Enterprise Router and Central Network Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect (Virtual Gateway) |
Scenario 5: Building a border firewall between VPCs

Customer Requirements |
You have two VPCs with each VPC used to run a separate service (service A in VPC 1 and service B in VPC 2). For security purposes, the traffic between service A and service B needs to be filtered by the firewall. |
---|---|
Pain Points |
You want to quickly set up a cloud network that meets security requirements. |
Benefits of Using Enterprise Routers |
A cloud firewall is deployed on the network, and the VPC and cloud firewall are associated with different route tables of the enterprise router to control the mutual access traffic between VPC 1 and VPC 2 to pass through the firewall. |
Best Practice |
Using Enterprise Router and CFW to Protect Traffic Between VPCs |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot