Tencent Cloud Connect Network (CCN) supports the route aggregation feature, including Virtual Private Cloud (VPC) Classless Inter-Domain Routing (CIDR)-based aggregation and custom aggregation. With this feature, you can aggregate the routes propagated by CCN to Direct Connect (DC) gateways and Virtual Private Network (VPN) gateways, thereby reducing the size of route tables in network instances and simplifying route management.
Note:
The route aggregation policy feature is currently in grayscale release. If you need to use it, submit a ticket for application.
Before enabling this feature, ensure that CCN-associated DC gateways and VPN gateways receive the VPC CIDR-aggregated routes by default.
The routing policy feature is enabled at the CCN instance level.
Before creating a route aggregation policy, ensure that the route aggregation feature has been enabled.
After the feature is enabled, the VPC CIDR-aggregated routes (with the lowest priority that can be deleted in the console) to DC gateways and VPN gateways will be added to each route table of CCN by default.
If no aggregation policy is configured, DC gateways and VPN gateways will receive routes to VPC subnets.
Editing a route aggregation policy may cause changes to the routes received by each network element.
Feature Strengths
Reducing the Route Table Size
Route aggregation can combine multiple routes into a single aggregated route, thereby significantly reducing the size of route tables for network instances. This is particularly important for complex networks with a large number of routes.
Simplifying Route Management
By using aggregated routes, users can manage the routing configuration of network instances more easily, avoiding management difficulties caused by excessive routes.
Improving Network Performance
After the size of route tables for network instances is reduced, routers consume fewer resources with higher processing efficiency, resulting in higher network performance.
Flexible Custom Aggregation
In addition to VPC CIDR-based aggregation, users can customize aggregation policies according to their needs to meet the requirements for route management in different scenarios.
Use Limits
The route aggregation policies can be delivered only to DC gateways and VPN gateways.
VPC CIDR-based aggregation applies only to routes targeting VPC instances, while custom aggregation applies to routes targeting VPC, DC gateway, and VPN gateway instances.
VPC CIDR-based aggregation is not performed for Tencent Kubernetes Engine (TKE) routes (a type of VPC routes) and custom routes.
Aggregation of custom aggregated routes is not supported.
Aggregated routes do not inherit the AsPath property of specific BGP routes. For custom route aggregation, the AsPath of aggregated routes can be specified, with a maximum length of 32 characters.
2. Click the CCN ID to be configured in the CCN list, and select the Route Table tab on the details page.
3. Click the route table ID to be configured, select the Route Aggregation Policy tab, and go to the page for route aggregation policy configuration.
4. Click Insert on the right of an existing route aggregation policy to insert a policy above/below the existing policy. Configure the following information for the route aggregation policy in the Add Policy dialog box, and click OK.
Configuration Item
Description
Aggregation criterion
The routes that meet the matching criteria are aggregated. Routes are filtered by instance ID and instance type (DC gateway, VPC, or VPN gateway).
Target scope
Aggregated routes will be propagated to network instances that meet the matching criteria. Instances are filtered by instance ID and instance type (DC gateway or VPN gateway).
Aggregation mode
The routes that meet the matching criteria can be aggregated in two modes, including VPC CIDR-based aggregation and custom aggregation.
VPC CIDR-based aggregation
This mode of aggregation does not apply to TKE routes and custom routes of the VPC type.
The aggregation criterion can only be VPC type or VPC instance ID.
Custom aggregation
The routes to be aggregated are specified. If specific routes fall within the IP ranges of the aggregated routes, the aggregated routes are distributed, but specific routes are not. The aggregation IP range and AsPath can be configured.
2. Click the CCN ID to be configured in the CCN list, and select the Route Table tab on the details page.
3. Click the route table ID to be configured, select the Route Aggregation Policy tab, and go to the page for route aggregation policy configuration.
4. On the route aggregation policy page, you can view:
Created route aggregation policies.
Aggregation criteria, the target scope, aggregation mode, aggregation IP range, and remarks of route aggregation policies.
Sorting information of created route aggregation policies.
Editing a Route Aggregation Policy
A created route aggregation policy can be edited.
1. Log in to the CCN console, click the CCN ID to be configured in the CCN list, and select the Route Table tab on the details page.
2. Click the route table ID to be configured, select the Route Aggregation Policy tab, and go to the page for route aggregation policy configuration.
3. Click Edit on the right of the existing route aggregation policy to modify the policy information. After the modification is completed, click OK.
Sorting
All route aggregation policies can be freely sorted. After network instances are associated with CCN, route aggregation policies are matched sequentially from top to bottom. If a policy is successfully matched, routes are propagated based on the configured aggregation action. Otherwise, the matching continues downward until the default policy is matched.
1. Log in to the CCN console, click the CCN ID to be configured in the CCN list, and select the Route Table tab on the details page.
2. Click the route table ID to be configured, select the Route Aggregation Policy tab, and go to the page for route aggregation policy configuration.
3. Click Sort to enable the sorting feature.
4. Press, hold, and drag the
icon on the left of an aggregation policy for sorting.
2. Click the CCN ID to be configured in the CCN list, and select the Route Table tab on the details page.
3. Click the route table ID to be configured, select the Route Aggregation Policy tab, and go to the page for route aggregation policy configuration.
4. Check the batch selection boxes on the left of the route aggregation policies to be deleted.
5. Click Delete.
6. In the pop-up window, click OK.
Note:
Creating, editing, sorting, or deleting a route aggregation policy may cause changes to the routes received by network elements, potentially triggering service changes. Proceed with caution.
