- Release Notes and Announcements
- [January 15, 2024]Announcement on the Official Launch of CCN Routing Reception and Routing Propagation Policies
- [July 3, 2023] Start Charging on CCN Connected Network Instances and Inbound Traffic
- Jul. 26, 2022 - CCN Tagging Upgrade
- Feb 10, 2022 - CCN API Authentication Upgrade
- Jun. 25, 2021 - Free Hangzhou-Shanghai and Hangzhou-Nanjing Lines
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Practical Tutorial
- API Documentation
- FAQs
- Troubleshooting
- Service Agreement
- Contact Us
- Release Notes and Announcements
- [January 15, 2024]Announcement on the Official Launch of CCN Routing Reception and Routing Propagation Policies
- [July 3, 2023] Start Charging on CCN Connected Network Instances and Inbound Traffic
- Jul. 26, 2022 - CCN Tagging Upgrade
- Feb 10, 2022 - CCN API Authentication Upgrade
- Jun. 25, 2021 - Free Hangzhou-Shanghai and Hangzhou-Nanjing Lines
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Practical Tutorial
- API Documentation
- FAQs
- Troubleshooting
- Service Agreement
- Contact Us
After a CCN is created, the system will automatically create a default route table and control route entries to manage traffic on CCN. You cannot add or delete routes, but you can enable or disable them. You can also manually create custom route tables and flexibly manage the interconnectivity of network instances in the CCN. This document introduces the concepts related to the custom route table.
Use Limits
The CCN binding with the SD-WAN access service and Edge devices does not support the multi-route table feature.
Comparison of Default Route Table and Custom Route Table
Comparison Item | Default Route Table | Custom Route Table |
Creation method | It is created by the system after a CCN instance is created. | It is manually created. |
Number of route tables | Only 1 | |
Route receiving policy | The initial policy is to receive all routes and it cannot be modified. | The initial policy is not to receive any routes. You need to configure the route receiving policy before use; otherwise the route information cannot be learned. For the details of configuring the route receiving policy in the custom route table, see Configuration of Route Receiving Policy. |
Is deletion supported | Deletion is not supported | Deletion is supported; however, it cannot be deleted when bound by network instances. |
Relationship Between Route Table and Network Instances
The route table and the network instance have a paired binding relationship. For example, binding route table A to network instance B and binding route table B to network instance A will produce the same result, that is, a network instance is bound to a route table. For the data messages sent by the network instance after binding, the bound route table will be used for finding and forwarding.
The relationship between the route table and the network instance has the following characteristics:
A network instance added to the CCN can be bound to only one route table. If no specific route table is designated, it will be automatically bound to the default route table.
A network instance will be automatically unbound from the route table when it is removed from the CCN.
After a network instance is bound to a route table under CCN, it can be switched to any other route table under the same CCN instance. Once the new route table is bound successfully, it will be automatically unbound from the original route table.
Creating Custom Route Tables
1. Log in to the CCN console.
2. In the CCN list, click the CCN ID for which you need to create a custom route table to enter the Route Table tab on the details page.
3. Click New Routing Table.
4. In the New Routing Table dialog box, configure the information of the custom route table and then click OK.
Note:
The upper limit for the number of custom route tables is 10. For more custom route tables, please consult Online Support. Custom route tables can be deleted, but they cannot be deleted if they are associated with network instances or referenced by the route table selection policy.
Viewing Route Tables
Viewing Custom Route Tables
1. Log in to the CCN console.
2. In the CCN list, click the CCN ID you want to view to enter the details page.
3. In the Route Table tab, click the Route Table ID to view related information:
In the Route Entries tab, view the information of route entries for the route table.
In the Bind Instance tab, view the network instances bound to the route table.
4. In the Route Reception Policy tab, view the routes of the network instances received by the route table.
Note:
There are two statuses for route table entries: If there is no IP range conflict, the status defaults to Valid. If it conflicts with other existing routes, the status is Invalid. For conflict rules and limitations, see Route Limitation. If you need to use invalid routes, see Disable Route and Enable Route.
Viewing Network Instance Route Tables
1. Log in to the CCN console.
2. In the CCN list, click the CCN ID you want to view to enter the Associated Instances tab on the details page.
3. Click Network Instance ID, and click the Route Table on the basic information page of VPC.
4. Click Route Table ID. On the route table details page, you can view the entry information of the next CCN route in the related route policy.
Deleting Custom Route Tables
Note:
Before deleting a custom route table, please ensure the following conditions are met:
The current custom route table is not associated with any network instance.
1. Log in to the CCN console.
2. In the CCN list, click the CCN ID for which you need to delete the custom route table to enter the Route Table tab on the details page.
3. In the left area of the tab, click Delete next to the custom route table ID.
4. In the Delete Route Table dialog box, click OK.
Directions
After the custom route table is created:
To enable a route in the route table, see Enabling a Route.
To disable a route in the route table, see Disabling a Route.
Yes
No
Was this page helpful?