Network Resilience Improvement for LACP aggregation on OVHcloud Bare Metal Servers

Hello,

Starting from November 25, 2025, we are changing the way link aggregation (LACP) functions within OVHcloud infrastructures.

What's changing

Until now, link aggregation for network interfaces was performed using ports belonging to the same network card (NIC). While this already provided redundancy in case of a ToR (Top-of-Rack) switch failure, it did not cover the risk of a NIC failure. The following diagram shows a comparison between the old and new aggregation rules:

What's not changing

• Existing aggregations will not be modified automatically.
• If you are not using LACP link aggregation on your server, no action is required and no change will be visible.

After this update

• Switching to OLA mode and then back to the default mode will trigger a reconfiguration and thus the application of the new aggregation rule.
• Reconfiguration will logically redistribute aggregations across two distinct NICs (no physical cabling changes).
• Once the new rule is applied, it will not be possible to revert to the old mode.
• For servers delivered after November 25, 2025, only the new rule will apply.

The OVHcloud control panel shows the aggregation layout to configure on your server. The same information is also available through the OVHcloud API (/dedicated/server/{serviceName}/virtualNetworkInterface and /dedicated/server/{serviceName}/virtualNetworkInterface/{uuid} routes).

For more information, see the documentation related to this change.