Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex BareMetal
    • All guides
    • Overview
    • Integrating with other Yandex Cloud services
      • Overview
      • Stock server configurations
      • Custom server configuration
      • On-request server configuration
      • Overview
      • Public network
      • Private network
      • DHCP
      • MC-LAG
      • Restrictions in BareMetal networks
      • Overview
      • Images
      • Access management
      • Additional server settings
      • Management console
      • Monitoring metrics
    • Quotas and limits
  • Pricing policy
  • FAQ
  1. Concepts
  2. Network
  3. MC-LAG

Reserving a BareMetal network connection using MC-LAG

Written by
Yandex Cloud
Updated at July 13, 2026
View in Markdown

For critical tasks that require high fault tolerance of physical network infrastructure, Yandex BareMetal provides a solution for reserving a network connection using MC-LAG.

MC-LAG (multi-chassis link aggregation group) is a type of link aggregation groups that reserve a connection to network switches. The MC-LAG technology is supported by BareMetal server configurations with two network interfaces hooked up to each of the networks (public and private).

In each network, the MC-LAG servers use two independent network ports of two different network adapters to connect to two different switches forming an MC-LAG pair at the same time. If one of the network adapters or switches fails, the second active connection ensures network connectivity of the server and provides fault tolerance.

Configuring aggregation groups and network interfacesConfiguring aggregation groups and network interfaces

Servers with MC-LAG support are simultaneously connected to each of the networks using two network adapters. Each adapter, in turn, is connected to a separate network switch over LACP 802.3ad. Network interface pairs connected to the networks form aggregation groups on the server side.

When you install the server OS with MC-LAG support from a public Marketplace image, aggregation groups are configured automatically during the OS installation, no manual setup required.

When you install the OS from a custom image, server network interfaces will not form aggregation groups, and only one of the two interfaces connected to each of the networks (public and private) will be active. You will need to configure aggregation groups manually. When configuring aggregation groups, you must disable DHCP for the network interfaces and enable it for the aggregation groups.

To learn more about configuring MC-LAG on the server side, see Configuring the MC-LAG aggregation group.

Useful linksUseful links

  • Network
  • Public network
  • Private network
  • DHCP in a Yandex BareMetal network
  • Restrictions in BareMetal networks
  • OS images
  • Configuring the MC-LAG aggregation group

Was the article helpful?

Previous
DHCP
Next
Restrictions in BareMetal networks
© 2026 Direct Cursus Technology L.L.C.