Trunk
Trunks are mainly used for:
- Providing a physical link between external hardware and the Yandex Cloud equipment at a point of presence.
- Enabling traffic multiplexing for both private and public connections using Ethernet 802.1Q.
Warning
Customers can have one or more trunks set up at a single point of presence. However, you cannot set up multiple private connections to a single cloud network through different trunks at the same point of presence.
Physical port settings on the Yandex Cloud equipment
All physical ports on the Yandex Cloud equipment have the following default settings:
- Physical port speed autonegotiation is not supported. Make sure to manually configure the speed and disable autonegotiation on your equipment.
- Yandex Cloud physical ports are always configured as 802.1Q tagged trunks. Access port (untagged) connections are not supported.
- The default MTU size supports jumbo frame transmission.
Physical port aggregation on the Yandex Cloud equipment
If you need to, you can group multiple physical ports into a single bundle using LACP in Active mode. When setting up a bundle, all its physical ports must use transceivers of the same type. You cannot combine transceivers of different types within a single bundle.
Yandex Cloud equipment does not support MC-LAG for aggregated links.
Physical connection topologies
Yandex Cloud equipment supports the following physical link options:
- Direct client connection: Connection of your own equipment at the point of presence directly to the Yandex Cloud equipment.
- Connection via a telecom provider: You have no equipment of your own at the point of presence and use the services of a telecom provider to set up a connection to the Yandex Cloud equipment.
Direct client connection
This is a connection of your own equipment at the point of presence directly to the Yandex Cloud equipment.
In this configuration, the trunk will comprise the following components:
- Physical port on your equipment.
- Optical transceiver connected to the physical port on your equipment.
- Physical port reserved on the Yandex Cloud equipment.
- Optical transceiver connected to the physical port on the Yandex Cloud equipment.
- Cross-connect linking the optical transceiver on your equipment's port and to the optical transceiver on the Yandex Cloud equipment.
The following chart illustrates this connection option:
The customer equipment is located at a point of presence and connected to the Yandex Cloud equipment directly through an optical cross-connect within the point of presence.
The transceiver transmitting side (Tx) on the Yandex Cloud equipment is connected to the transceiver receiving side (Rx) on the customer equipment using optical fiber. The transceiver transmitting side (Tx) on the customer equipment is connected to the transceiver receiving side (Rx) on the Yandex Cloud equipment with optical fiber. This optical fiber pair forms an optical cross-connect.
Connection via a telecom provider
If the customer does not have their own equipment at the appropriate point of presence, they can engage a telecom provider that has equipment at that point of presence to connect to the Yandex Cloud equipment.
The following chart illustrates this connection option:
In this configuration, the trunk will comprise the following components:
- Physical port on the telecom provider equipment.
- Optical transceiver connected to the physical port on the telecom provider equipment.
- Physical port reserved on the Yandex Cloud equipment.
- Optical transceiver connected to the physical port on the Yandex Cloud equipment.
- Cross-connect linking the optical transceiver on the telecom provider equipment port and to the optical transceiver on the Yandex Cloud equipment.
Note
The telecom provider is responsible for setting up a connection between the customer equipment and its own equipment at the appropriate point of presence and ensuring traffic between the customer equipment and the Yandex Cloud equipment.
Partner trunk
Using a partner trunk makes connecting to Yandex Cloud easier thanks to:
- Shorter CIC setup times.
- Lower operational cost for cross-connects.
You can use such trunks to set up both private and public connections.
Tutorials
- To set up a private connection over a partner trunk, use this tutorial.
- To set up a public connection over a partner trunk, use this tutorial.
There is a limitation on the packet transfer rate per second (packets per second) for a trunk connection via a partner, which is calculated using the following formula:
PpsRate (Pps) = Capacity (Mbps) × 101.166667
Where:
PpsRate: Maximum packet transfer rate per second (Pps).Capacity: Throughput of the trunk connection in megabits per second (Mbps).
Connection multiplexing (802.1Q)
VLAN-ID
Ethernet 802.1Q enables transmitting various traffic types concurrently, i.e., traffic multiplexing. Each private or public connection in a trunk is assigned its own unique VLAN-ID.
Warning
When setting up a private or public connection, you can only use the VLAN ID values ranging from 2 to 4000, inclusive.
Connection multiplexing options
A single trunk can accommodate a mix of different connection types:
- One private connection.
- One public connection.
- Multiple private connections and/or public connections.
You can leverage the following multiplexing options:
- Direct connection at a point of presence.
- Connection via a telecom provider (L2 transit).
- Connection via a telecom provider (L3VPN).
- Connection via a partner.
Direct connection at a point of presence
This option assumes setting up an 802.1Q trunk through a direct physical connection between the customer equipment at the point of presence and the Yandex Cloud equipment.
Connection via a telecom provider (L2 transit)
This option is used when the customer does not have their own equipment at the point of presence. In this case, the following applies:
- An 802.1Q trunk is set up at the point of presence via a telecom provider enabling L2 transit.
- An 802.1Q trunk is set up between the customer equipment and the Yandex Cloud equipment.
- When connecting the customer equipment, the provider uses its own communication circuits. If the customer needs to change connection VLAN IDs (enable VLAN ID translation) on their equipment, the telecom provider needs to agree with the customer on the translation scenario to ensure seamless operation between the customer and telecom provider equipment.
Connection via a telecom provider (L3VPN)
This option is used when the customer does not have their own equipment at the point of presence. In this case, the following applies:
- An 802.1Q trunk is set up at the point of presence via a telecom provider.
- An 802.1Q trunk is set up between the telecom provider equipment at the point of presence and the Yandex Cloud equipment.
- Telecom provider enables L3VPN for the customer to establish connectivity between the telecom provider equipment at the point of presence and the customer equipment. This option is generally used when the customer lacks technical resources to ensure BGP peering to the Yandex Cloud equipment on their own and delegates this to a telecom provider that enables such peering through L3VPN.
Connection via a partner
A partner trunk is established using the 802.1ad (QinQ) technology, which relies on a stack of two VLAN tags:
- Upper VLAN tag (
C-VLAN): Client ID within the partner trunk. Determined by the VLAN-ID value from the pool specified by the partner when creating the trunk. TheC-VLANtag allows the Yandex Cloud network equipment to separate one client's traffic from another's within an individual partner trunk. This tag is assigned to the partner trunk the moment the trunk is created. - Lower VLAN tag (
PRC-VLAN): Determined by the VLAN-ID value of the private connection in the trunk. This tag is set when creating the private connection.
The C-VLAN and PRC-VLAN tags in the stack may have the same value. The partner and the client agree on the communication scheme directly, without involving Yandex Cloud.
The partner's network equipment must do the following:
- Remove the
C-VLANtag when receiving QinQ Ethernet frames from the Yandex Cloud equipment and send a regular 802.1q trunk towards the client's network equipment. - Add the appropriate
C-VLANtag when receiving an 802.1q Ethernet frame from the client, after which QinQ Ethernet frames can be transmitted towards the Yandex Cloud equipment.
Whether is it a direct client connection or a partner trunk, the client must always get a clean 802.1q trunk (without the C-VLAN tag) with a set of VLAN IDs matching the set of private connections configured by the client.
Connection capacity
At the trunk level, Yandex Cloud equipment uses reception and transmission speed limits for data from/to external equipment in bits per second and packets per second according to the connection capacity selected by the customer.
Yandex Cloud equipment utilizes RateLimit (Policing) to limit data reception and transmission speeds. When transmission speeds exceed the specified bits per second or packets per second, the equipment may drop the data. This can result in evenly transmitted traffic being processed at a higher speed than traffic transmitted in sudden bursts.