Dedicated tunnels are network link segmentation of a connection. You can create dedicated tunnels that connect to different Direct Connect gateways to enable communication between your on-premises IDC and multiple VPCs. This document describes how to apply for a dedicated tunnel.
The shared connection feature of new dedicated tunnels has stopped accepting new applications at 00:00, August 1, 2020. If you are using a shared connection, it will not be affected by this change, but if you delete it, you will not be able to apply for new dedicated tunnels with shared connection after 00:00, August 1, 2020.
To ensure the fine-grained scheduling capability of your network, do not publish the following routes:
220.127.116.11/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 100.64.0.0/10, 18.104.22.168/16, 172.16.0.0/12, 192.168.0.0/16.
If a large IP range route is published, the direct connect gateway will directly reject it.
You can split the above routes as follows for distribution:
|Dedicated tunnel name||Enter your dedicated tunnel name.||-|
|Access network||VPC, BM VPC, and CCN are supported.||CCN: it enables connection to multiple VPCs through one tunnel.|
|VPC/BM VPC||Select the ID of the network instance to be connected to by the dedicated tunnel.||BM VPC currently supports only Standard Direct Connect gateways.|
|Gateway region||If **CCN** is selected as the access network, this parameter means the CCN-based Direct Connect gateway region, which is the same as the public cloud region where the connection access point is located.||For the shared connection mode, you need to get the connection access point region information from the connection owner.|
|Direct Connect gateway||The VPC-based Direct Connect gateway region is the same as the VPC region, while the CCN-based Direct Connect gateway region is the same as the public cloud region where the connection access point is located.||CCN-based Direct Connect gateways currently don't support the NAT feature.|
|VLAN ID||If VLAN ID is 0, it means that this connection does not enable subinterfaces; therefore, only one tunnel can be created.||MSTP connection passthrough to multiple VLANs requires the ISP's line to enable the Trunk mode.|
|Bandwidth||Bandwidth is the maximum rate, which can be changed later in "Tunnel Change". With postpaid monthly 95th percentile billing mode, the "bandwidth" parameter does not represent the billable bandwidth.||-|
|IP||This IP can be customized by you or provided randomly by Tencent Cloud. You can get the randomly assigned IP address in tunnel details after your application is submitted.
||If you choose to publish the IP to the Direct Connect gateway, please plan IP segmentation well to avoid IP conflicts.|
|Routing method||BGP routing and static routing are supported.||Tencent Cloud ASN: 45090.|
|BGP ASN||For **BGP routing**, this parameter is optional. Enter the BGP neighbor AS number at the CPE side. If it is left empty, the number will be assigned by the system randomly.||-|
|BGP key||For **BGP routing**, this parameter is optional. Enter the MD5 value of the BGP neighbor, which is "tencent" by default. If it is left empty, it means that no BGP key is required. It cannot contain ?, &, space, ", \, and +.||-|
|User IDC IP range||For **static routing**, enter your CPE IP range, which should not conflict with the VPC IP range if not in NAT mode.||Change is supported: you can update the IP range in "Tunnel Change" in the console subsequently.|
The possible statuses of a dedicated tunnel include the following: