Docs

Direct Connect

DC Gateway

Adding a BGP Peer

Scenarios

If a Virtual Interface associated with a Direct Connect (DC) Gateway uses BGP routes without configuring BGP parameters at the creation of the interface, see this topic. You can add a BGP Peer at your on-premises data center (IDC) for the DC Gateway to interconnect networks between the IDC and the gateway.

Prerequisites

You have created a DC Gateway with basic features and a Virtual Interface using BGP.

Limits

DC Gateways with the status of Suspended do not support adding BGP Peers.

Procedure

In the top menu bar, select your target Region.

Click the name of the target DC Gateway to enter the DC Gateway details page.

Select the BGP Peer tab, click Add BGP Peer, and then configure the BGP Peer based on the table below.

Parameter	Description	Sample value
Network type	Select the network type of the BGP Peer. IPv4 is supported by default. If you enable IPv6 for DC Gateway, you can add BGP Peers of both IPv4 and IPv6 types separately.	IPv4
DC Virtual Interface	Select the Virtual Interface to add the BGP Peer. Only Virtual Interfaces with "BGP" are selectable.	VIF-ad3hu
Peer ASN	Type the ASN of the BGP Peer. In the BGP protocol, each independent AS has a globally unique Autonomous System Number (ASN). The valid range for the Peer ASN is 1 to 4294960000. The ASN of the BGP Peer can neither be the same as that of the DC Gateway, nor be the VolcanoEngine ASN (137718). tip If the DC Gateway uses the VolcanoEngine ASN (137718), confirm the Peer ASN is different from 137718. If the DC Gateway ASN is custom, the Peer ASN must be different from both the custom ASN of DC Gateway and 137718.	46000
BGP key	Type the BGP key accurately.	123456

warning

Once a BGP peer is added, the BGP information (Peer ASN and BGP key) cannot be modified.

Click Add to complete adding the BGP Peer.

Results

After you add a BGP Peer, a neighbor relationship is established between the Autonomous Systems (ASes). The DC Gateway then automatically learns the on-premises data center routes from this peer and propagates them into its routing table.