Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- 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
Show all
Function Overview
-
Enterprise Router
-
What's an Enterprise Router?
An enterprise router connects virtual private clouds (VPCs) and on-premises networks to build a central hub network. It has high specifications, provides high bandwidth, and delivers high performance. Enterprise routers use the Border Gateway Protocol (BGP) to learn, dynamically select, or switch between routes, thereby ensuring the service continuity and significantly improving network scalability and O&M efficiency.
An enterprise router connects virtual private clouds (VPCs) and on-premises networks to build a central hub network. It has high specifications, provides high bandwidth, and delivers high performance. Enterprise routers use the Border Gateway Protocol (BGP) to learn, dynamically select, or switch between routes, thereby ensuring the service continuity and significantly improving network scalability and O&M efficiency.
Availability: CN North-Beijing4, CN North-Ulanqab1, CN East-Shanghai1, CN East-Qingdao, CN East2, CN South-Guangzhou, CN Southwest-Guiyang1, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, ME-Riyadh, AF-Cairo, AF-Johannesburg, TR-Istanbul, LA-Mexico City2, LA-Sao Paulo1, and LA-Santiago
-
-
Attachment
-
A variety of network instances can be attached to an enterprise router as its attachments.
Availability: CN North-Beijing4, CN North-Ulanqab1, CN East-Shanghai1, CN East-Qingdao, CN East2, CN South-Guangzhou, CN Southwest-Guiyang1, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, ME-Riyadh, AF-Cairo, AF-Johannesburg, TR-Istanbul, LA-Mexico City2, LA-Sao Paulo1, and LA-Santiago
-
-
Route Table
-
Route tables are used by enterprise routers to forward packets. Route tables contain associations, propagations, and routes.
An enterprise router can have multiple route tables. You can associate attachments with different route tables to enable communication or isolation between network instances.
Availability: CN North-Beijing4, CN North-Ulanqab1, CN East-Shanghai1, CN East-Qingdao, CN East2, CN South-Guangzhou, CN Southwest-Guiyang1, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, ME-Riyadh, AF-Cairo, AF-Johannesburg, TR-Istanbul, LA-Mexico City2, LA-Sao Paulo1, and LA-Santiago
-
-
Association
-
Each attachment can be associated with one route table for:
Packet forwarding: Packets from the attachment are forwarded through the routes specified in the associated route table.
Route propagation: The routes in the associated route tables are automatically propagated to the route table of the attachment.
You can create an association in the following ways:
Manually: Select a route table and create an association for an attachment in the route table.
Automatically: You just need to enable Default Route Table Association and specify the default route table. The system automatically creates an association for an attachment in the default route table.
Availability: CN North-Beijing4, CN North-Ulanqab1, CN East-Shanghai1, CN East-Qingdao, CN East2, CN South-Guangzhou, CN Southwest-Guiyang1, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, ME-Riyadh, AF-Cairo, AF-Johannesburg, TR-Istanbul, LA-Mexico City2, LA-Sao Paulo1, and LA-Santiago
-
-
Propagation
-
You can create a propagation for each attachment to propagate routes to one or more route tables on an enterprise router.
If you do not need a propagation, you can manually add static routes for attachments to the route tables.
You can create a propagation in the following ways:
Manually: Select a route table and create a propagation for an attachment in the route table.
Automatically: You just need to enable Default Route Table Propagation and specify the default route table. A propagation is automatically created for an attachment in the default propagation route table.
Availability: CN North-Beijing4, CN North-Ulanqab1, CN East-Shanghai1, CN East-Qingdao, CN East2, CN South-Guangzhou, CN Southwest-Guiyang1, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, ME-Riyadh, AF-Cairo, AF-Johannesburg, TR-Istanbul, LA-Mexico City2, LA-Sao Paulo1, and LA-Santiago
-
-
Route
-
Routes are used to forward packets. A route contains information such as the destination, next hop, and route type.
You can create a propagation for attachments to automatically propagate routes to route tables or manually add static routes to route tables.
Availability: CN North-Beijing4, CN North-Ulanqab1, CN East-Shanghai1, CN East-Qingdao, CN East2, CN South-Guangzhou, CN Southwest-Guiyang1, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, ME-Riyadh, AF-Cairo, AF-Johannesburg, TR-Istanbul, LA-Mexico City2, LA-Sao Paulo1, and LA-Santiago
-
-
Sharing
-
Integration with Resource Access Manager (RAM) allows you to share enterprise routers in your accounts with other accounts so that these other users can attach their network instances to your enterprise router for network connectivity.
After you share your enterprise router with other accounts, these principals can attach their network instances to your enterprise router, so that their network instances can access your enterprise router.
Availability: CN North-Beijing4, CN North-Ulanqab1, CN East-Shanghai1, CN East-Qingdao, CN East2, CN South-Guangzhou, CN Southwest-Guiyang1, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, ME-Riyadh, AF-Cairo, AF-Johannesburg, TR-Istanbul, LA-Mexico City2, LA-Sao Paulo1, and LA-Santiago
-
-
Flow Log
-
Enterprise Router can work with Log Tank Service (LTS) to capture traffic of attachments on enterprise routers in real time. Flow logs allow you to monitor the network traffic of attachments and analyze network attacks, improving your O&M efficiency.
Flow logs can capture traffic of the following types of attachments:
VPC attachment
Virtual gateway attachment
VPN gateway attachment
Peering connection attachment
Global DC gateway
Availability: CN North-Beijing4, CN North-Ulanqab1, CN East-Shanghai1, CN East-Qingdao, CN East2, CN South-Guangzhou, CN Southwest-Guiyang1, CN-Hong Kong, AP-Bangkok, AP-Singapore, AP-Jakarta, ME-Riyadh, AF-Cairo, AF-Johannesburg, TR-Istanbul, LA-Mexico City2, LA-Sao Paulo1, and LA-Santiago
-
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