Tencent Cloud Connect Network (CCN) supports adding tags to cross-region business traffic of different types based on traffic matching rules, while flexibly setting inter-region bandwidth upper limits for different business tags based on traffic scheduling rules. You can flexibly control business bandwidth based on traffic matching and scheduling rules.
Note:
The traffic scheduling rule feature is currently in grayscale release. If needed, submit a ticket for application. Once cross-region traffic management is enabled, the speed-limited bandwidth of the default rule (QoS 0) will no longer be automatically adjusted.
The default rule (QoS 0) cannot be deleted.
The total speed-limited bandwidth of unidirectional traffic scheduling rules cannot exceed the bandwidth upper limit.
You may need to adjust the scheduling rules for traffic in both directions.
Scenarios
When CCN is used for cross-region communication, different types of businesses share the same cross-region bandwidth. In certain scenarios, bandwidth contention between businesses can result in issues such as decreased stability, latency jitter, and packet loss. Traffic matching and scheduling rules enable targeted bandwidth allocation across regions, ensuring business isolation and enhancing the stability of network communications.
Note:
After the cross-region traffic management feature is enabled, if you need to increase the bandwidth upper limit, it is necessary to increase the speed-limited bandwidth upper limit of the corresponding rules simultaneously. Since the speed-limited bandwidth of the default rule is no longer automatically adjusted, merely increasing the bandwidth upper limit will not take effect.
After enabling the cross-region traffic management feature, if you need to reduce the bandwidth upper limit, you must first decrease the speed-limited bandwidth upper limit of the corresponding rules. Since the speed-limited bandwidth of the default rule is no longer automatically adjusted, merely decreasing the bandwidth upper limit will not take effect.
Use Limits
Only cross-region bandwidth supports the traffic scheduling feature.
Postpaid CCN instances support the traffic scheduling feature only in inter-region speed limiting mode.
The quota limit for matching and scheduling rules is as follows:
|
Traffic matching rules | 255 entries per region | Not supported |
Traffic scheduling rules | 63 entries per region | Not supported |
How It Works
Traffic Matching Rules
Traffic matching rules are used to capture cross-region traffic and add tags. You can configure custom five-tuples and apply different QoS IDs to traffic that meets the conditions. You can configure corresponding traffic matching rules for each region, and the matching rules do not affect each other across different regions.
Note:
The supported range for QoS ID is 1 to 63.
Traffic Scheduling Rules
Traffic scheduling rules are used to allocate inter-region bandwidth for different businesses. Traffic matching rules add QoS tags to businesses, and then traffic scheduling rules allocate cross-region bandwidth based on these QoS tags. Traffic scheduling rules are configured based on the bandwidth and region, and the traffic scheduling rules for each region control the upper limit of outbound bandwidth.
For example, if you purchase a prepaid bandwidth between Beijing and Shanghai with a speed limit of 1 Gbps, and allocate a maximum bandwidth of 500 Mbps to Business A in the Beijing region, then Business A can use a maximum bandwidth of 500 Mbps for traffic from Beijing to Shanghai, while the bandwidth for traffic from Shanghai to Beijing will not be affected. The total bandwidth allocated by unidirectional traffic scheduling rules between two regions cannot exceed the inter-region bandwidth upper limit. For example, if you purchase a 1 Gbps bandwidth link between Beijing and Shanghai, the total bandwidth limits configured by the scheduling rules in a single region cannot exceed 1 Gbps.
Note:
Each cross-region bandwidth has a default scheduling rule. Traffic without any QoS ID tag will share the remaining inter-region bandwidth by default. For example, if you purchase a 1 Gbps bandwidth link between Beijing and Shanghai, and allocate 500 Mbps of bandwidth to Business A and 300 Mbps to Business B in the Beijing region through traffic scheduling rules, other businesses without configured scheduling rules will share the remaining 200 Mbps of bandwidth for the Beijing-to-Shanghai direction.
Enabling Cross-Region Traffic Management
2. In the CCN list, click the CCN ID that you want to configure, and click the Basic Information tab on the details page.
3. Enable the Cross-Region Traffic Management switch, and then click OK.
Creating a Traffic Matching Rule
2. In the CCN list, click the CCN ID you want to configure, and click the Traffic Matching Rules tab on the details page.
3. Select the region where you need to configure matching rules, click Add Rule, and go to the traffic matching rule configuration page.
4. Configure the corresponding information for matching rules in the configuration box, and then click OK.
|
Priority | Traffic matching rules have priorities from 1 to 255, where lower numbers indicate higher priority. CCN applies the highest-priority rules first during traffic matching. |
Protocol type | The protocol type for capturing traffic messages. Currently, TCP, UDP, and ICMP protocol types are supported. |
Source IP range | Source IP range of data messages, supporting fuzzy matching. For example: 10.0.0.0/16 matches 10.0.1.10/32. Leaving this field blank indicates matching any. |
Destination IP range | Destination IP range of data messages, supporting fuzzy matching. For example: 10.0.0.0/16 matches 10.0.1.10/32. Leaving this field blank indicates matching any. |
Source port | Source port of data messages. Value range: 1–65535. |
Destination port | Destination port of data messages. Value range: 1–65535. |
QoS ID | Set QoS ID tags for matched traffic, with a valid range from 1 to 63. Subsequent traffic scheduling rules will allocate cross-region bandwidth based on these QoS IDs. |
Description | Description of traffic matching rules. |
Viewing Traffic Matching Rules
2. In the CCN list, click the CCN ID you want to configure, and click the Traffic Matching Rules tab on the details page.
3. After selecting the corresponding region, you can view the information about the configured matching rules for that region.
Deleting Traffic Matching Rules
2. In the CCN list, click the CCN ID you want to configure, and click the Traffic Matching Rules tab on the details page.
3. Batch select the checkboxes on the left side of the rules, then click Delete to perform batch deletion. Alternatively, click Delete on the right side of a rule to delete a single rule.
Creating a Traffic Scheduling Rule
2. In the CCN list, click the CCN ID you want to configure, and click the Bandwidth Management tab on the details page.
3. Click Configure Traffic Scheduling Rules on the right side of the bandwidth.
4. In Configure Traffic Scheduling Rules, select the Target Direction tab, click Add Rule, and configure the rules according to the following information.
|
Name | Name of the traffic scheduling rule. |
Description | Description of the traffic scheduling rule. |
Match QoS ID | QoS ID value of traffic messages. This indicates that scheduling rules allocate bandwidth based on the configured QoS IDs. |
Bandwidth | Cross-region bandwidth value allocated to business traffic with the configured QoS ID. The total bandwidth allocated by all scheduling rules under one cross-region bandwidth cannot exceed the inter-region bandwidth limit. |
Editing a Traffic Scheduling Rule
2. In the CCN list, click the CCN ID you want to configure, and click the Bandwidth Management tab on the details page.
3. Click Configure Traffic Scheduling Rules on the right side of the bandwidth.
4. In Configure Traffic Scheduling Rules, select the Target Direction tab, and click Edit on the right side of the existing scheduling rule to edit the rule.
Deleting a Traffic Scheduling Rule
2. In the CCN list, click the CCN ID you want to configure, and click the Bandwidth Management tab on the details page.
3. Click Configure Traffic Scheduling Rules on the right side of the bandwidth.
4. In Configure Traffic Scheduling Rules, select the Target Direction tab, click Delete on the right side of the existing scheduling rule, and click Confirm in the pop-up window.