Skip to navigationSkip to main contentSkip to footerScaleway Docs HomepageAsk our AI
Ask our AI

Understanding dual attachment on Elastic Metal

Dual attachment, or dual-homing, is a network setup where a server has 2 physical network ports, each wired to a different network switch.

On a compatible Elastic Metal server, each port handles both public and private network traffic. This architecture provides hardware-level network redundancy (removing the network single point of failure) and doubles the maximum bandwidth (up to 2 x 100 Gbps on Private Networks).

How it works

Top-of-rack redundancy
The server physically connects to 2 distinct top-of-rack (leaf) switches.
Active-Active hardware
Both physical links are active simultaneously on the infrastructure side, combining maximum network capacity with native fault tolerance.
Enabled by default
Compatible Elastic Metal server offers come with dual-attachment pre-configured if you follow the standard OS install process from the console. Note that if you do a custom install, you must configure the network for LACP yourself (e.g. for Proxmox, refer to their network configuration guide (External link)).
Seamless failover
If a cable, a port, or an entire leaf switch fails, network traffic automatically reroutes to the remaining interface with no TCP session interruption.
Bandwidth quotas
For the compatible offers that can have a bandwidth higher than 2 x 25 Gbps, you must request a quota increase from Scaleway Support.

Network requirements and configuration rules

To ensure dual attachment functions properly, follow the configuration rules:

LACP active mode
Configure bonding with Link Aggregation Control Protocol (LACP) in active mode on the server side (passive mode is not supported).
No LACP fallback
If you do not use LACP, only the primary port functions, and network redundancy is unavailable (without LACP, the server does not support primary/backup configurations).
MAC address alignment
Configure the MAC address of the bond interface to match exactly the physical MAC address of the primary network interface. Note that Ubuntu generates a random MAC address for bonds by default.
Reversion power cycle
After you establish an LACP bond between the server and the pair of leaf switches, reverting to a standard non-bonded configuration requires a full server power cycle.
iPXE boot limitations
The secondary network interface does not support iPXE boot. If the primary switch becomes unavailable, the server cannot reboot into rescue mode via the secondary interface.
OS compatibility
Dual attachment is supported on Linux operating systems. It is currently not supported on Windows.

VPC and Private Networks behavior

VLAN capacity sharing
If multiple Elastic Metal servers reside in the same VLAN or are connected to the same leaf switch pair, those servers share the overall network bandwidth.
Private Networks bandwidth
Total server bandwidth is split equally among all attached Private Networks. Example: A server configured with 2 x 30 Gbps attached to 3 Private Networks allocates 2 x 10 Gbps per Private Network (rather than 2 x 30 Gbps on each).

Compatible offers

This feature is introduced with the Lithium EM-L530E and EM-L630E Elastic Metal offers.

For the full list of offers and their up-to-date compatibility, see the Elastic Metal Datasheet.

Still need help?

Create a support ticket
No Results