2. On the left sidebar, click Dedicated tunnels > Exclusive virtual interface, click + New, complete basic configurations such as name, connection type, access network, gateway region and associated direct connect gateway, and click Next.
Field
Description
Name
Enter a name for your dedicated tunnel.
Tunnel Type
Set to 1.0 or 2.0 depending on the associated connection you select.
Connections
Select a connection you have applied for.
Access Network
For a 1.0 tunnel, select from CCN and VPC.
For a 2.0 tunnel, select either CCN、Virtual Private Cloud and NAT network.
Region
If CCN is selected as the access network, the region is where the CCN-based direct connect gateway resides by default.
If VPC is selected as the access network, you can only select the region where the connection resides for a 2.0 tunnel and select any region for a 1.0 tunnel.
VPC
Select the VPC instance to be connected to by the dedicated tunnel.
Direct Connect Gateway
Associate an existing direct connect gateway with the dedicated tunnel. A 2.0 tunnel does not support a NAT-type direct connect gateway.
3. Configure the following parameters on the Advanced Configuration page.
Field
Description
VLAN ID
One VLAN corresponds to one tunnel. Valid range: [0，3000).
If the value is 0, only 1 tunnel can be created. Use physical layer 3 interfaces for the connection.
If the value is between 1 and 2999, multiple tunnels can be created. Use layer 3 sub-interfaces for the connection. When only the layer 2 connection is supported, please disable the STP protocol under the interface at the IDC side. In the case of multiple dedicated tunnels, when the MSTP connection passes through multiple VLANs, the carrier line needs to enable the Trunk mode.
Bandwidth
Specify the bandwidth cap of the dedicated tunnel, which cannot exceed the maximum bandwidth of the associated connection. If the billing mode is pay-as-you-go by monthly 95th percentile, this parameter does not mean the billable bandwidth.
Interconnection Method
By default, Manual allocation is selected for 2.0 tunnels.
Both Manual allocation and Automatic Assignment are supported for 1.0 tunnels. If Automatic Assignment is selected, there is no need to configure Tencent Cloud Primary Edge IP and CPE Peer IP.
Tencent Cloud Primary IP
Enter the connection IP address on the Tencent Cloud side. Do not use the following IP ranges or IP addresses: 169.254.0.0/16, 127.0.0.0/8, 255.255.255.255, 224.0.0.0 - 239.255.255.255, 240.0.0.0 - 255.255.255.254.
Tencent Cloud Primary IP
Enter the secondary IP address of the connection on the Tencent Cloud side. The secondary IP will be automatically used to ensure the normal operation of your business when the Tencent Cloud primary IP fails and becomes unavailable. This field is not supported when the mask of the secondary IP address is 30 or 31.
CPE Peer IP
Configure the connection IP address on the user (or carrier) side.
Routing Mode
Select:
BGP Routing: Applicable to the exchange of routing information and network accessibility across autonomous systems (AS).
Static Routing: Applicable to a simper network environment.
Switch the route after the configured consecutive failed health checks.
BGP ASN
Enter the BGP neighbor ASN on the CPE side. Note that the Tencent Cloud ASN is 45090. If this field is left empty, a random ASN will be assigned.
BGP Key
Enter the MD5 value of the BGP neighbor, which defaults to "tencent". If it is left empty, no BGP key is required. It cannot contain 6 special characters including ?, &, space, ", \\, and +.
Note:
If Static is selected as the routing mode, do not directly publish the following routes: 9.0.0.0/8, 10.0.0.0/8, 11.0.0.0/8, 30.0.0.0/8, 100.64.0.0/10, 131.87.0.0/16, 172.16.0.0/12 and 192.168.0.0/16` when configuring IDC IP ranges. Instead, you need to first split them as follows.
9.0.0.0/8 is split into 9.0.0.0/9 + 9.128.0.0/9.
10.0.0.0/8 is split into 10.0.0.0/9 + 10.128.0.0/9.
11.0.0.0/8 is split into 11.0.0.0/9 + 11.128.0.0/9.
30.0.0.0/8 is split into 30.0.0.0/9 + 30.128.0.0/9.
100.64.0.0/10 is split into 100.64.0.0/11 + 100.96.0.0/11.
131.87.0.0/16 is split into 131.87.0.0/17 + 131.87.128.0/17.
172.16.0.0/12 is split into 172.16.0.0/13 + 172.24.0.0/13.
192.168.0.0/16 is split into 192.168.0.0/17 + 192.168.128.0/17.
4. Configure IDC devices. You can click Download configuration guide to download related files and complete the configurations as instructed in the guide.
Parameter
Configuration
Remarks
CPE IP Range
Enter the customer IP range if Static is selected as the routing mode. This parameter cannot conflict with the VPC IP range in a non-NAT mode.
You can update the IP range later via "Change Tunnel" in the console.
5. Click Submit.
Step 2: Set the alarm recipient
After a dedicated tunnel is created, Tencent Cloud automatically configures four event alarms such as DirectConnectTunnelDown, DirectConnectTunnelBFDDown, DirectConnectTunnelBGPSessionDown, and DirectConnectTunnelRouteTableOverload, helping you monitor and manage your dedicated tunnels. For more information on the event alarms, see Alarm Overview.
The automatically created default alarm policy is not configured with recipient information, and only supports console alarms. You can configure alarm recipients by yourself. For details, see [**Configuring Alarm Policies**](https://www.tencentcloud.com/ document/product/216/38402).
Connection Status
After the dedicated tunnel is created, it will be displayed on the Dedicated Tunnels page in the Applying status.
The possible connection statuses of a dedicated channel include:
Applying
The system has received your application for a new dedicated tunnel and is ready to start the creation.
Configuring
The system is delivering the parameter configuration. If this status lasts for a long time, a failure may occur. In this case, contact your architect or submit a ticket for assistance.
Configured
The system has completed the configuration based on the specified parameters but is unable to ping to the IP address of your IDC. A dedicated tunnel in this status can be deleted.
Connected
The system pings to your IDC device successfully. However, this does not mean that your business is connected. You have to configure the route table of the VPC or CCN instance to implement the connection.
Deleting
If you delete your dedicated tunnel on the console, the connection status of the dedicated tunnel becomes Deleting. If this status lasts for a long time, a failure may occur. In this case, contact your architect or submit a ticket for assistance.
Yes
No
Was this page helpful?