Updated on 2023-12-01 GMT+08:00


An enterprise router provides the functions listed in Table 1, allowing you to:
  • Manage attachments, custom route tables, associations, propagations, and routes.
  • Manage permissions, tags, and quota to improve service security.
Table 1 Functions of an enterprise router




Enterprise routers

An enterprise router is a high-performance centralized router that supports route learning. When creating an enterprise router, you can set parameters such as its region, AZ, and name.

After an enterprise router is created, you can still change its parameters based on service requirements.

Creating an Enterprise Router


You can add attachments to attach network instances to the enterprise router.

Different network instances are attached through different consoles.
  • VPCs are attached through the Enterprise Router console.
  • Virtual gateways are attached through the Direct Connect console.
  • VPN gateways are attached through the VPN console.
  • Enterprise routers of other regions are added to a central network on the Cloud Connect console.
  • VPC border firewalls are created on the CFW console.

Attachment Overview

Route tables

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.

Route Table Overview


Associations are created manually or automatically to associate attachments with enterprise router route tables.
  • 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.

Association Overview


A propagation is created manually or automatically to enable an enterprise router to learn the routes to an associated attachment.
  • 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.

Propagation Overview


A route consists of information such as the destination address, next hop, and route type. There are two types of routes:
  • Propagated routes
  • Static routes

Route Overview


You are the owner of the enterprise router, and other accounts are the users of your enterprise router.

After you share your enterprise router with other accounts, these other users can attach their network instances to your enterprise router, so that their network instances can access your enterprise router.

This allows VPCs in the same region but different accounts to be attached to the same enterprise router.

Sharing Overview

Flow logs

The flow log function records traffic logs of attachments on enterprise routers in real time. The logs allow you to monitor the network traffic of attachments and analyze network attacks, helping you achieve efficient O&M.

Flow logs can capture traffic of the following types of attachments:
  • VPC
  • Virtual gateway
  • VPN gateway
  • Peering connection

Flow Log Overview


You can use Cloud Eye to monitor the network status of enterprise routers and their attachments.

Supported Metrics


You can use Cloud Trace Service (CTS) to record operations associated with your enterprise routers for future query, audit, and backtracking.

Key Operations Recorded by CTS


You can use Identity and Access Management (IAM) to set different permissions for employees in your enterprise to control their access to enterprise routers.

Creating a User and Granting Permissions


Tags are used to identify cloud resources. You can add tags to enterprise routers and route tables.

Tag Overview


Quotas can limit the number or amount of resources available to users, for example, how many enterprise routers can be created, how many attachments can be created for each enterprise router, and how many routes can be added to each route table.