Direct Connect
Direct Connect
Document
- Documentation
Direct ConnectFAQDirect Connect Connection FAQs
Copy page
Download PDFFAQ
Direct Connect Connection FAQs
Copy pageDownload PDFDirect Connect Connection FAQs
How to select a line operator when creating a DC Connection?
- First, confirm which line operators are supported at the access point. You can consult your VolcanoEngine account manager to understand the supported line operators. For more information, see Direct Connect access points.
- Among the line operators supported at the access point, comprehensively consider factors like pricing and network conditions of different line operator types to select the most suitable Direct Connect (DC) line operator.
What are the network requirements for Direct Connect access?
- The cloud DC gateway IP and the on-premises data center's gateway IP must be in the same subnet and must not be duplicate addresses.
- The interconnection subnet should use a private IP range and must not conflict with either the cloud or on-premises IP ranges.
Who pays for a Shared Line?
The tenant pays for a Shared Line.
When using a Shared Line, fees charged by VolcanoEngine mainly include port occupancy fees and traffic fees:
- Port occupancy fee: The tenant applies to the operator (also known as a VolcanoEngine partner) to use a Shared Line. The operator creates a Shared Line under the tenant's account based on confirmed information (no charge at this step). After creation, the tenant can see the Shared Line in their own "DC Connection" console. The tenant must accept the Shared Line and pay the port occupancy fee before using the line.
- Traffic fee: The tenant creates a DC Gateway under their own account. The tenant pays traffic fees for using this gateway. Whether using a Shared Line or Dedicated Line, traffic fees generated by the DC Gateway are always paid by the user.
Is dynamic routing protocol supported?
Yes. BGP dynamic routing is supported.
Are the upstream and downstream bandwidths of a DC Connection the same?
Yes. If you purchase a 200M DC Connection, both its upstream and downstream bandwidths are 200M.
What is the mapping between DC Connections and Virtual Interfaces?
The mapping is 1 : n. One DC Connection can be associated with multiple Virtual Interfaces.
What are the switch restrictions for redundant DC Connections?
Currently, DC Gateways do not support cross-switch access. When connecting multiple DC Connections to switches, the following restrictions apply (using 2 DC Connections as an example):
- If connecting the two DC Connections to the same switch, you can associate them with a DC Gateway.
- (Recommended) If connecting the two different DC Connections to separate switches, you must create two separate DC Gateways to associate with respective DC Connections.
Why can't I use the QoS policy?
Confirm whether you have enabled the QoS policy feature.
The QoS policy feature is in the beta stage and can only be used after activation. If it is not activated, it will not be visible or usable in the console. To request a trial, please contact your account manager.
How to associate a QoS Policy with a Shared Line?
Shared Lines do not support associating QoS policies. Currently, only Dedicated Lines support QoS policy association. Shared lines, DC Gateways, and Virtual Interfaces do not support QoS policies. For more QoS policy usage limits, see QoS Policy.
Why are DSCP values on some DC Connections without QoS policies also being re-marked?
This may happen because the re-marked DC Connection without QoS policy (DCC-01) shares the same DC Gateway (DCGW-01) with another DC Connection (DCC-02) that has a QoS policy (QoS_policy) with DSCP re-marking enabled.
When a QoS policy is associated with a DC Connection, the platform suggests associating other DC Connections using the same DC Gateway simultaneously. In the example below, DCC-01 and DCC-02 both use DCGW-01. Only DCC-01 is associated with QoS_policy having DSCP re-marking enabled, while DCC-02 is not. Traffic passing through DCGW-01 enters both DC Connections.
- Traffic entering DCC-01 is scheduled by QoS_policy.
- Traffic entering DCC-02 is scheduled by the system-default QoS policy. However, its DSCP values are re-marked according to DCC-01's policy.
Why is the QoS policy on a DC Connection not taking effect?
After a QoS policy is associated with a DC Connection, possible reasons for it not taking effect include:
- The bandwidth of the DC Connection is less than the port specification of the DC Connection.
- If the bandwidth of the DC Connection is less than the Port Spec, the queue scheduling of QoS policy does not take effect. Only remarking DSCP is supported.
- The Virtual Interface associated with this DC Connection has bandwidth limit enabled.
- All Virtual Interfaces created using the QoS policy-associated DC Connection cannot enable bandwidth limit. If any Virtual Interfaces with bandwidth limit enabled exist, the QoS policy of the DC Connection becomes invalid.
How is MACsec different from IPsec and TLS encryption?
The differences of Media Access Control Security (MACsec), Internet Protocol Security (IPsec), and TLS Transport Layer Security (TLS) are shown in the table below. To switch encryption mode for a DC Connection, see Managing encryption mode.
Last updated: 2026.08.24 11:30:48
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
