Trunk

Trunks are mainly used for:

• Providing a physical connection from external equipment to the Yandex Cloud equipment at a point of presence.
• Enabling traffic multiplexing for private and public connections using Ethernet 802.1Q.

Physical port settings on the Yandex Cloud equipmentPhysical port settings on the Yandex Cloud equipment

All physical ports on the Yandex Cloud equipment have the following default settings:

• No auto negotiation of the transmission rate is supported on physical ports. Make sure to explicitly set the transmission rate and disable auto negotiation on your equipment.
• On the Yandex Cloud equipment, a physical port always works in trunk mode with 802.1Q tagging. No connection in access port mode (without tagging) is supported.
• The default MTU size supports transfer of jumbo frames.

Physical connection topologiesPhysical connection topologies

The following physical connection setup options are supported on the Yandex Cloud equipment:

• Direct client connection: Connection of your own equipment at a point of presence directly to the Yandex Cloud equipment.
• Connection using telecom provider services: You do not have your own equipment at a point of presence and use services of a telecom provider that sets up a connection from your equipment to the Yandex Cloud equipment.

Direct client connectionDirect client connection

This is a connection of your own equipment at a point of presence directly to the Yandex Cloud equipment.

A trunk in this setup option has 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 connection that is used to connect to the optical transceiver on your equipment's port and to the optical transceiver on the Yandex Cloud equipment.

One may outline this connection as follows:

The client equipment is located at a point of presence and connected to the Yandex Cloud equipment directly through an optical cross-connection routed 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 client equipment using optical fiber. The transceiver transmitting side (Tx) on the client equipment is connected to the transceiver receiving side (Rx) on the Yandex Cloud equipment with optical fiber. A pair of these optical fibers makes up an optical cross-connect.

Connecting using telecom provider servicesConnecting using telecom provider services

If a client does not have their own equipment at the appropriate point of presence, they can use a telecom provider that has equipment at the appropriate point of presence to connect to the Yandex Cloud equipment.

One may outline this connection as follows:

A trunk in this setup option has the following components:

• Physical port on the telecom provider's equipment.
• Optical transceiver connected to the physical port on the telecom provider's equipment.
• Physical port reserved on the Yandex Cloud equipment.
• Optical transceiver connected to the physical port on the Yandex Cloud equipment.
• Cross connection that is used to connect to the optical transceiver on the telecom provider's equipment and to the optical transceiver on the Yandex Cloud equipment.

Connection multiplexing (802.1Q)Connection multiplexing (802.1Q)

VLAN-IDVLAN-ID

Ethernet 802.1Q allows you to transmit different types of traffic, i.e., enables traffic multiplexing. Each private or public connection in a trunk is assigned its own unique VLAN-ID.

Connection multiplexing optionsConnection multiplexing options

You can combine different types of connections in a trunk:

• 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 using telecom provider services (L2 transit).
• Connection using telecom provider services (L3VPN).

Direct connection at a point of presenceDirect connection at a point of presence

This option assumes setting up a 802.1Q trunk over a direct physical connection between the client equipment at the point of presence and the Yandex Cloud equipment.

Connection using telecom provider services (L2 transit)Connection using telecom provider services (L2 transit)

This option is used when the client does not have their own equipment at the point of presence. It assumes that:

• The 802.1Q trunk is set up at the point of presence through a telecom provider that provides L2 transit.
• The 802.1Q trunk is set up between the client equipment and the Yandex Cloud equipment.
• When connecting the client equipment, the provider uses its own communication circuits. If the client needs to change connection VLAN IDs (enable VLAN ID translation) on their equipment, the telecom provider needs to agree upon the translation scenario with the client for consistent operation of the client and telecom provider equipment.

Connection using telecom provider services (L2 transit)Connection using telecom provider services (L2 transit)

This option is used when the client does not have their own equipment at the point of presence. It assumes that:

• The 802.1Q trunk is set up at the point of presence through a telecom provider.
• The 802.1Q trunk is set up between the telecom provider's equipment at the point of presence and the Yandex Cloud equipment.
• Connectivity between the telecom provider's equipment at the point of presence and the client equipment is ensured by providing the L3VPN service to the client. This setup option is usually used when the client cannot technically ensure BGP connectivity to the Yandex Cloud equipment on their own and delegates this to a telecom provider that ensures connectivity by providing an L3VPN service to the client.

Connection capacityConnection capacity

At the trunk level, Yandex Cloud equipment limits data receive/send rates from/to external equipment in bits per second and packets per second according to the connection capacity selected by the client.

To limit the rate of receiving and sending data on the Yandex Cloud equipment, one uses the RateLimit (Policing) tool. When the data transfer speed in bits per second or packets per second is exceeded, the data may be rejected. As a result, uniform traffic may be transmitted at a faster speed than the traffic transmitted in sudden bursts.