tencent cloud

Direct Connect

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Application Scenarios
Use Limits
Connection Access Point
Relevant Products
Network Planning
Purchase Guide
Billing Overview
Purchasing in the Console
Renewing Connections
Getting Started
Operation Guide
Connections
Direct Connect Gateways
Dedicated Tunnels
Monitoring and Alarming
MACsec Encryption
Cloud Exchange
Cloud Access Management
Overview
Access Policy Types
Access Policy Syntax
Practical Tutorial
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
Establishing Direct Connect Between Tencent Cloud and Various Cloud Vendors Through Equinix
API Documentation
History
Introduction
API Category
Making API Requests
Direct Connect APIs
Data Types
Error Codes
FAQ
Basic FAQs
Billing Issues
Function Issues
Troubleshooting
General Troubleshooting Solutions
Access Failure and Packet Loss
Agreements
Tencent Cloud Direct Connect Service Level Agreement
Tencent Cloud Direct Connect Service Agreement
Tencent Cloud Direct Connect Review Standards
Contact Us
Glossary
DocumentaçãoDirect ConnectPractical TutorialIDC Local ConfigurationBGP Routing Configuration GuideHuawei NE Series Routers

Huawei NE Series Routers

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2024-11-05 09:46:38
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.
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 ports
interfaces <interface_number>
description <interface_desc>
undo shutdown
speed <interface_speed>
duplex full
undo negotiation auto
commit

# Set virtual tunnels
interfaces <interface_number>.<subinterface_number>
description <subinterface_desc>
vlan-type dot1q <subinterface_vlanid>
ip address <subinterface_ipaddress> <subinterface_netmask>
commit

# Set eBGP
bgp <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 unicast
peer <bgp_peer_address> enable
commit

# Configure BFD for eBGP
bgp <as_number>
router-id <route_id>
peer <bgp_peer_address> bfd min-tx-interval <time value> min-rx-interval <time value> detect-multiplier <value>
Anterior: Accelerating Routing Convergence Through BGP+BFD (Layer 3)Próximo: Huawei CE Series Switches

Ajuda e Suporte

Esta página foi útil?

comentários