> For the complete documentation index, see [llms.txt](https://docs.console.zenlayer.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.console.zenlayer.com/welcome/cloud-networking/get-started/validate-connection-in-public-cloud/volcengine-configuration.md).

# Volcengine Direct Connect Configuration

The Volcengine side of the setup: accept the shared connection, create the DC gateway and virtual interface, attach it to a CEN, and bring up BGP.

## Background Information

Volcengine Direct Connect (DC) builds a fast, low-latency, stable, and secure private channel between your on-premises data center and your VPCs. Compared with a VPN or public IP addresses, it offers more bandwidth, lower latency, and privacy, and lets one site reach several VPCs over the private network.

A direct connection has four components: the **access point**, the **physical connection**, the **DC gateway**, and the **virtual interface**. The physical connection links your data center to the access point, the DC gateway is the entry point in the cloud, the virtual interface ties the two together, and a Cloud Enterprise Network (CEN) carries traffic to the VPC.

<figure><img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-77264cd1333746e51153e53c331e7ee80ffd19a7%2Fvolcengine-dc-overview.png?alt=media" alt=""><figcaption><p>An on-premises IDC reaching a Volcengine VPC over the Zenlayer backbone</p></figcaption></figure>

### The shared connection model

Volcengine offers dedicated and shared connections. Going through Zenlayer uses the **shared** model: Zenlayer has already reached the Volcengine access point as an operator and created the shared physical connection, so you do not arrange a circuit from your site to the access point yourself — you only need to reach the Zenlayer access point. Provisioning is therefore faster and cheaper.

{% hint style="info" %} <mark style="color:blue;">**Note**</mark>

<mark style="color:blue;">In the shared model, Zenlayer handles the physical connection request and the LOA work. On the Volcengine console you only configure the DC gateway, the virtual interface, and the network instance attachment.</mark>
{% endhint %}

## Terminology

| Term                               | Description                                                                                                |
| ---------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Access point**                   | The location where a physical connection reaches Volcengine                                                |
| **Physical connection**            | The circuit between your facility and the Volcengine access point                                          |
| **DC gateway**                     | The access router for the connection — the entry point from your site into the cloud                       |
| **Virtual interface (VIF)**        | The logical interface that ties the physical connection to the DC gateway; supports static and BGP routing |
| **CEN** (Cloud Enterprise Network) | The service that interconnects VPCs across regions and links cloud and on-premises networks                |
| **VPC**                            | The isolated virtual network you configure for your cloud resources                                        |
| **ASN**                            | The DC gateway's ASN defaults to `137718`; the BGP peer ASN must differ from it                            |
| **VLAN ID**                        | The VLAN of the virtual interface, from 0 to 2999; it must be unique per switch                            |

The definitions follow the [**Volcengine Direct Connect documentation**](https://www.volcengine.com/docs/6408/68176).

## Procedures

The Volcengine-side setup runs as follows:

<figure><img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-65289737ec58e59b344478c7dbd834ccd94f6c04%2Fvolcengine-direct-connect-flow.svg?alt=media" alt=""><figcaption><p>Volcengine-side setup flow</p></figcaption></figure>

<figure><img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-c7a71f0ca6d22e72d79335dd91f1ef3bf3219f6c%2Fvolcengine-dc-flow.png?alt=media" alt=""><figcaption><p>The Volcengine Direct Connect configuration flow</p></figcaption></figure>

{% stepper %}
{% step %}
**Before you start**

* Make sure your Volcengine account has completed real-name verification and that the balance plus vouchers is not below zero.
* Create the VPC and subnets you want to reach. Their CIDR blocks must not overlap or conflict with your on-premises network.
* Create a CEN instance and attach that VPC to it as a network instance.
* Agree the access point, port speed, bandwidth, and high-availability design with your Zenlayer solutions engineer, including the VLAN ID and the interconnect IP plan.

<img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-5961bea9ac389c1aa2f03164b5622f10a99895e1%2FIcon.svg?alt=media&amp;token=b85eac46-fd05-4800-aa2b-8db408b8af26" alt="" data-size="line"><mark style="color:blue;">**Note**</mark>\ <mark style="color:blue;">Pick the access point closest to your data center — the shorter the distance, the lower the latency. Access points differ in which carriers and port speeds they support, so confirm with Zenlayer before planning.</mark>
{% endstep %}

{% step %}
**Get the shared physical connection**

1. Send Zenlayer your Volcengine **account ID** and the **region** you want to reach.
2. Once Zenlayer creates the shared physical connection, it appears in the **Physical Connections** list on the Volcengine console awaiting your confirmation (named something like `DAS201_port01_conn`).
3. Confirm and accept it, and note its name and project — you select it when creating the virtual interface.

<img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-5961bea9ac389c1aa2f03164b5622f10a99895e1%2FIcon.svg?alt=media&amp;token=b85eac46-fd05-4800-aa2b-8db408b8af26" alt="" data-size="line"><mark style="color:blue;">**Note**</mark>\ <mark style="color:blue;">When you terminate the service, delete this shared physical connection as well, or port charges continue.</mark>
{% endstep %}

{% step %}
**Create the DC gateway**

Open the DC gateway console, select the same region as the physical connection, and click **Create DC Gateway**:

| Setting | Description                                                                  | Example                 |
| ------- | ---------------------------------------------------------------------------- | ----------------------- |
| Region  | Must match the physical connection                                           | North China 2 (Beijing) |
| Name    | The gateway's name                                                           | dcgw-01                 |
| ASN     | The gateway's autonomous system number; the Volcengine ASN can be used as is | 137718                  |
| IPv6    | Whether to enable IPv6                                                       | Disabled                |
| Project | The project the gateway belongs to                                           | Project-test            |

<img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-5961bea9ac389c1aa2f03164b5622f10a99895e1%2FIcon.svg?alt=media&amp;token=b85eac46-fd05-4800-aa2b-8db408b8af26" alt="" data-size="line"><mark style="color:blue;">**Note**</mark>\ <mark style="color:blue;">A virtual interface can use IPv6 only if IPv6 is enabled on its DC gateway, and that cannot be switched off again. Leave it disabled unless you need it.</mark>
{% endstep %}

{% step %}
**Create the virtual interface**

Open the virtual interface console, select the same region as the connection and the gateway, and click **Create Virtual Interface**:

| Setting               | Description                                                                                           | Example                               |
| --------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------- |
| Region                | Must match the connection and the gateway                                                             | North China 2 (Beijing)               |
| Name                  | The interface's name                                                                                  | VIF-01                                |
| Physical connection   | Filter by project to find the connection                                                              | Project-test｜DAS201\_port01\_conn     |
| DC gateway            | Filter by project to find the gateway                                                                 | Project-test｜dcgw-01                  |
| Bandwidth limit       | Whether to cap the bandwidth                                                                          | Off                                   |
| IPv4 interconnect IPs | The local (cloud gateway) and remote (on-premises gateway) addresses, in the same subnet and distinct | Local 10.0.0.1/30, remote 10.0.0.2/30 |
| VLAN ID               | The VLAN towards your site, from 0 to 2999                                                            | 10                                    |
| Routing type          | BGP (recommended) or static                                                                           | BGP                                   |
| BGP peer ASN          | From 1 to 4294960000, and different from the gateway ASN                                              | Provided by Zenlayer                  |
| BGP key               | 6 to 80 characters; cannot be changed afterwards                                                      | Provided by Zenlayer                  |
| Health detection      | BGP routing supports BFD                                                                              | BFD                                   |

<img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-5961bea9ac389c1aa2f03164b5622f10a99895e1%2FIcon.svg?alt=media&amp;token=b85eac46-fd05-4800-aa2b-8db408b8af26" alt="" data-size="line"><mark style="color:blue;">**Note**</mark>

* <mark style="color:blue;">VLAN ID 0 means the switch port runs as a Layer 3 routed interface, so the connection carries exactly one untagged virtual interface; 1–2999 means Layer 3 subinterfaces, and one connection can carry several virtual interfaces.</mark>
* <mark style="color:blue;">The BGP key is sensitive and cannot be changed after creation — store it safely.</mark>
* <mark style="color:blue;">If the physical connection needs a QoS policy, do not enable the bandwidth limit on the virtual interface.</mark>
  {% endstep %}

{% step %}
**Attach the gateway to the CEN**

Once the virtual interface exists, attach the DC gateway to the Cloud Enterprise Network so that it can reach the VPC over the private network.

1. Open the CEN console, select the target instance, and go to the **Network Instances** tab.
2. Click **Attach Network Instance**, choose **DC gateway** as the type, and select the gateway you created.
3. Confirm the gateway becomes available and that the VPC is attached to the same CEN.
4. For cross-region traffic, configure a bandwidth package and the cross-region bandwidth in the CEN.
   {% endstep %}

{% step %}
**Route on your side and verify**

With static routing, add a route towards your on-premises network on the DC gateway's **Routes** tab. With BGP routing configured on the virtual interface, routes are learned automatically.

1. On your switch or router, configure routes towards the VPC CIDR as planned.
2. On the Volcengine console, check that the virtual interface and the BGP peer show as established.
3. From a server in your data center, ping the private IP of an ECS instance in the VPC.
4. For a redundant pair, enable BFD and confirm the failover time meets your expectation.

<img src="https://3201622183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9X3FDdkCL2HzhbPpPMFt%2Fuploads%2Fgit-blob-5961bea9ac389c1aa2f03164b5622f10a99895e1%2FIcon.svg?alt=media&amp;token=b85eac46-fd05-4800-aa2b-8db408b8af26" alt="" data-size="line"><mark style="color:blue;">**Note**</mark>\ <mark style="color:blue;">End-to-end testing is done together with Zenlayer. If connectivity fails, check the VLAN ID, the interconnect subnets, the BGP ASN and key, and the CEN routing in that order.</mark>
{% endstep %}
{% endstepper %}

## References

* [**Volcengine Direct Connect documentation**](https://www.volcengine.com/docs/6408/68176)
