- Release Notes and Announcements
- Release Notes
- [Oct. 2022] Discontinuing the Free Tier of Outbound Traffic and Introducing a New Pricing Plan
- Direct Connect Resource Lifecycle Standardization
- Dec. 31, 2022 - Migration of Direct Connect Cross-Region Tunnel Service to CCN
- Redundant Direct Connect Gateway Clearance
- Jun. 1, 2022 - Starts Commercialization of Shared Tunnel Service
- [Dec 1, 2020] Free Trial Period Extension and Billing Rule Change for Direct Connect Outbound Traffic
- Aug. 1, 2020 - Service Change Notice
- Dec. 31, 2021 - Direct Connect 2.0 Released
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Cloud Access Management
- Best Practices
- Connecting a Local IDC to CVM by Using a VPC NAT Gateway and Direct Connect
- Hybrid Cloud Primary/Secondary Communication (DC and VPN)
- Best Practices on Direct Connect High Availability and Hybrid Cloud Network
- Migrating Cross-Region Dedicated Tunnel to CCN
- Migrating IDC to the Cloud Through CCN
- Accelerating Routing Convergence Through BGP+BFD (Layer 3)
- IDC Local Configuration
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Direct Connect APIs
- RejectDirectConnectTunnel
- ModifyDirectConnectTunnelAttribute
- DescribeDirectConnectTunnels
- DeleteDirectConnectTunnel
- CreateDirectConnectTunnel
- AcceptDirectConnectTunnel
- ModifyDirectConnectAttribute
- DescribeDirectConnects
- DescribeAccessPoints
- DeleteDirectConnect
- CreateDirectConnect
- ReleaseInternetAddress
- EnableInternetAddress
- DisableInternetAddress
- DescribeInternetAddressStatistics
- DescribeInternetAddressQuota
- DescribeInternetAddress
- ApplyInternetAddress
- Data Types
- Error Codes
- FAQ
- Troubleshooting
- Agreements
- Contact Us
- Glossary
- Release Notes and Announcements
- Release Notes
- [Oct. 2022] Discontinuing the Free Tier of Outbound Traffic and Introducing a New Pricing Plan
- Direct Connect Resource Lifecycle Standardization
- Dec. 31, 2022 - Migration of Direct Connect Cross-Region Tunnel Service to CCN
- Redundant Direct Connect Gateway Clearance
- Jun. 1, 2022 - Starts Commercialization of Shared Tunnel Service
- [Dec 1, 2020] Free Trial Period Extension and Billing Rule Change for Direct Connect Outbound Traffic
- Aug. 1, 2020 - Service Change Notice
- Dec. 31, 2021 - Direct Connect 2.0 Released
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Cloud Access Management
- Best Practices
- Connecting a Local IDC to CVM by Using a VPC NAT Gateway and Direct Connect
- Hybrid Cloud Primary/Secondary Communication (DC and VPN)
- Best Practices on Direct Connect High Availability and Hybrid Cloud Network
- Migrating Cross-Region Dedicated Tunnel to CCN
- Migrating IDC to the Cloud Through CCN
- Accelerating Routing Convergence Through BGP+BFD (Layer 3)
- IDC Local Configuration
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Direct Connect APIs
- RejectDirectConnectTunnel
- ModifyDirectConnectTunnelAttribute
- DescribeDirectConnectTunnels
- DeleteDirectConnectTunnel
- CreateDirectConnectTunnel
- AcceptDirectConnectTunnel
- ModifyDirectConnectAttribute
- DescribeDirectConnects
- DescribeAccessPoints
- DeleteDirectConnect
- CreateDirectConnect
- ReleaseInternetAddress
- EnableInternetAddress
- DisableInternetAddress
- DescribeInternetAddressStatistics
- DescribeInternetAddressQuota
- DescribeInternetAddress
- ApplyInternetAddress
- Data Types
- Error Codes
- FAQ
- Troubleshooting
- Agreements
- Contact Us
- Glossary
Direct Connect connects Tencent Cloud with the user IDC with a dedicated physical line. After configuring the Direct Connect gateway and dedicated tunnel on the Tencent Cloud side, users need to configure routes on the local IDC. Using the layer-3 sub-interfaces to connect to Tencent Cloud is recommended.
Note:
This document only introduces the local routing configurations associated with Tencent Cloud Direct Connect. For other information, please see the local router documentation or consult your router provider.
Routing Configuration
Note:
It's recommended that you use the default configurations of
Keepalive and holdtime for the BGP connection between the two peers. The holdtime is three times the interval at which keepalive messages are sent. The recommended holdtime value is 180s.# Configure portsinterfaces <interface_number>description <interface_desc>undo portswitchundo shutdownspeed <interface_speed>duplex fullundo negotiation autocommit# Configure virtual tunnels (layer 3 sub-interfaces)interface <interface_number>.subinterface-numberdescription <subinterface_desc>dot1q termination vid <vlanid>ip address <subinterface_ipaddress> <subinterface_netmask># Set eBGPbgp <as_number>#router-id <route_id>peer <bgp_peer_address> as-number <bgp_peer_as_number>peer <bgp_peer_address> password cipher <bgp_auth_key>peer <bgp_peer_address> description <bgp_desc>ipv4-family unicastpeer <bgp_peer_address> enablecommit# Configure BFD for eBGPbgp <as_number>router-id <route_id>peer <bgp_peer_address> bfd min-tx-interval <time value> min-rx-interval <time value> detect-multiplier <value>
Yes
No
Was this page helpful?