- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Cloud Access Management
- API Documentation
- Introduction
- History
- API Category
- Making API Requests
- Direct Connect APIs
- ApplyInternetAddress
- Applies for a connection
- DescribeInternetAddress
- Deletes a connection
- DescribeInternetAddressQuota
- AcceptDirectConnectTunnel
- DescribeInternetAddressStatistics
- CreateDirectConnectTunnel
- DescribeAccessPoints
- DisableInternetAddress
- DeleteDirectConnectTunnel
- EnableInternetAddress
- DescribeDirectConnectTunnels
- DescribeDirectConnects
- ModifyDirectConnectAttribute
- ModifyDirectConnectTunnelAttribute
- RejectDirectConnectTunnel
- ReleaseInternetAddress
- Data Types
- Error Codes
- FAQ
- Troubleshooting
- Agreements
- Notice
- Glossary
- Product Introduction
- Purchase Guide
- Quick Start
- Operation Guide
- Cloud Access Management
- API Documentation
- Introduction
- History
- API Category
- Making API Requests
- Direct Connect APIs
- ApplyInternetAddress
- Applies for a connection
- DescribeInternetAddress
- Deletes a connection
- DescribeInternetAddressQuota
- AcceptDirectConnectTunnel
- DescribeInternetAddressStatistics
- CreateDirectConnectTunnel
- DescribeAccessPoints
- DisableInternetAddress
- DeleteDirectConnectTunnel
- EnableInternetAddress
- DescribeDirectConnectTunnels
- DescribeDirectConnects
- ModifyDirectConnectAttribute
- ModifyDirectConnectTunnelAttribute
- RejectDirectConnectTunnel
- ReleaseInternetAddress
- Data Types
- Error Codes
- FAQ
- Troubleshooting
- Agreements
- Notice
- Glossary
This document describes how to create a direct connect gateway and provides information on the inbound route.
Prerequisites
- You have applied for a connection as instructed in Applying for Connection.
- You have built a VPC as instructed in Building Up an IPv4 VPC.
Directions
- Log in to the Direct Connect Gateway console.
- Select a region and VPC at the top of the Direct Connect Gateway page, and click +New.
- Complete the configurations in the pop-up window and click OK.
| Field | Description |
|---|---|
| Name | The name of the direct connect gateway |
| Associate Network | Select either CCN or VPC. |
| CCN instance | A CCN instance is needed if CCN is selected for the Associate Network. This field can also be left empty. |
| Network | A VPC instance is needed if VPC is selected for the Associate Network. |
| Gateway Type | A gateway is needed if VPC is selected for the Associate Network.
|
Inbound Routes
As shown in the Direct Connect network architecture, both the creation time of the direct connect gateway and dedicated tunnel mode will affect the destination of the inbound route (from your IDC to a Tencent Cloud VPC). For more information, please see Direct Connect Gateway Overview.
| Gateway Type | Creation Time | Dedicated Tunnel Mode | IDC Routes to Tencent Cloud |
| VPC-based direct connect gateway | No limit | Static | The inbound routing policy is configured in the local router. |
| BGP | The IDC automatically obtains the VPC CIDR block based on the BGP protocol. | ||
| CCN-based direct connect gateway | Before 00:00:00 on September 15, 2020 | Static | The inbound routing policy is configured in the local router. |
| BGP | The IDC automatically obtains the subnet CIDR block based on the BGP protocol. | ||
| After 00:00:00 on September 15, 2020 | Static | The inbound routing policy is configured in the local router. | |
| BGP | The IDC automatically obtains the VPC CIDR block based on the BGP protocol. |
Subsequent Operations
- After you create a CCN-based direct connect gateway, you should also add IDC IP ranges to the direct connect gateway to implement network communication. For more information, see Adding IDC IP Ranges to the Direct Connect Gateway.
- After you create a VPC-based direct connect gateway, you should also configure the VPC’s route table to implement network communication. For more information, see Configuring the Route Table.
Was this page helpful?