diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.de-de.md
index a835b4d0bc9..4f9e92a3acb 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.de-de.md
@@ -1,7 +1,7 @@
---
title: "So konfigurieren Sie Link-Aggregation mit LACP in Debian 12 oder Ubuntu 24.04 (EN)"
-excerpt: "Enable Link Aggregation in your Debian 12 or Ubuntu 24.04 server (Netplan) to increase your server’s availability and boost the efficiency of your network connections"
-updated: 2026-04-14
+excerpt: "Enable Link Aggregation in your Debian 12 or Ubuntu 24.04 server (Netplan) to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
## Ziel
-Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die Verfügbarkeit Ihres Servers zu erhöhen und die Effizienz Ihrer Netzwerkverbindungen zu steigern. Mit nur wenigen Klicks können Sie Ihre Netzwerkkarten aggregieren und Ihre Netzwerkverbindungen redundant machen. Wenn also eine Verbindung ausfällt, wird der Datenverkehr automatisch auf eine andere verfügbare Verbindung umgeleitet.
+Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die Verfügbarkeit Ihres Servers zu erhöhen und die Effizienz Ihrer Netzwerkverbindungen zu steigern. Mit nur wenigen Klicks können Sie Ihre Netzwerkkarten aggregieren und Ihre Netzwerkverbindungen redundant machen. Wenn also eine Verbindung ausfällt, wird der Datenverkehr automatisch auf eine andere verfügbare Verbindung umgeleitet. Die verfügbare Bandbreite wird durch Aggregation ebenfalls verdoppelt.
+Die Aggregation basiert auf dem Standard IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Diese Anleitung erklärt, wie Sie Ihre Schnittstellen für die Verwendung mit OLA in Debian 9 bis 11 zusammenfassen können (ifupdown-Konfiguration).**
-**Erfahren Sie, wie Sie Ihre NIC (Network Interface Controller) für die Verwendung mit dem OLA-Dienst unter Debian (Versionen 9 bis 11) zusammenfassen können.**
+> [!warning]
+> Diese Anleitung enthält Anweisungen zum Konfigurieren der Netzwerk-Schnittstellenaggregation speziell mit `ifupdown`, dessen Konfigurationsdatei sich unter `/etc/network/interfaces` befindet. Sie gilt auch für den Rescue-Modus.
+>
+> Wenn die Netzwerkkonfiguration Ihres Systems stattdessen `Netplan` verwendet (Debian 12 oder neuer, Ubuntu 24.04), lesen Sie bitte [diese Anleitung](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Voraussetzungen
-- [Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation im OVHcloud Kundencenter](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [OVHcloud Link Aggregation im OVHcloud Kundencenter konfigurieren](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -25,89 +46,241 @@ Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die V
---
+## In der praktischen Anwendung
+
+> [!primary]
+> Die in den Konfigurationen und Beispielen unten angezeigten Werte (MAC-Adressen, IP-Adressen usw.) dienen nur als Beispiele. Sie müssen diese Werte natürlich durch Ihre eigenen ersetzen.
+>
+
> [!warning]
>
-> Sie müssen das Paket "ifenslave" auf den Server herunterladen, bevor Sie OLA im OVHcloud Kundencenter oder in der API aktivieren können. Verwenden Sie dazu den folgenden Befehl:
+> Sie müssen das Paket ifenslave auf dem Server installieren, bevor Sie OLA im OVHcloud Kundencenter oder in der API aktivieren können. Verwenden Sie dazu den folgenden Befehl:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Ermittlung der MAC-Adressen
+
+Melden Sie sich im [OVHcloud Kundencenter](/links/manager) an, wechseln Sie zum Bereich `Bare Metal Cloud`{.action} und wählen Sie Ihren Server unter **Dedicated Server** aus.
+
+Wechseln Sie zum Tab `Netzwerkinterfaces`{.action} und notieren Sie die MAC-Adressen für jede Schnittstelle (öffentlich/privat), die am unteren Ende des Menüs angezeigt werden.
+
+{.thumbnail}
+
> [!primary]
+> Bitte beachten Sie, dass die MAC-Adresse der **öffentlichen Hauptschnittstelle** diejenige ist, die DHCP-Angebote empfängt, sowohl im Betriebssystem des Servers als auch im Rescue-Modus. Diese Schnittstelle verwaltet die öffentliche Konnektivität in der Standardkonfiguration.
>
-> Diese Anleitung enthält Anweisungen zum Konfigurieren der Netzwerk-Schnittstellenaggregation speziell mit `ifupdown`, dessen Konfigurationsdatei `/etc/network/interfaces` ist. Sie gilt auch für den Rescue-Modus.
+> Außerdem ist die MAC-Adresse der **privaten Hauptschnittstelle** diejenige mit dem niedrigsten Wert. Im obigen Beispielbild ist dies die Adresse `a1:b2:c3:d4:e5:d6`.
>
-> Wenn die Netzwerkkonfiguration Ihres Systems stattdessen `Netplan` verwendet, lesen Sie [diese Anleitung](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-
-
-## In der praktischen Anwendung
Da wir für unsere NICs in OLA eine privat-private Konfiguration haben, können wir keine SSH-Verbindung zum Server herstellen. Daher müssen wir das IPMI-Tool nutzen, um auf den Server zuzugreifen.
-
Loggen Sie sich hierzu in Ihrem [OVHcloud Kundencenter](/links/manager) ein. Klicken Sie im Bereich `Bare Metal Cloud`{.action} Ihren Server aus `Dedicated Server`{.action}, aus und klicken Sie dann auf den Tab `IPMI`{.action} (1).
+
Klicken Sie auf den Tab `IPMI`{.action} (1).
Klicken Sie anschließend auf die Schaltfläche `Mit einem Java-Applet (KVM)`{.action} (2).
-{.thumbnail}
-
-Ein JNLP-Applet wird heruntergeladen. Öffnen Sie es, um IPMI aufzurufen. Melden Sie sich mit gültigen Anmeldeinformationen für den Server an.
-
-Bei Verwendung eines OVHcloud Templates werden die NICs standardmäßig mit *ethX* oder *enoX* gekennzeichnet. Wenn Sie kein OVHcloud Template verwenden, können Sie die Namen Ihrer Schnittstellen mit dem folgenden Befehl ermitteln:
-
-```bash
-ip a
-```
+### Ermittlung der Interface-Namen
> [!primary]
>
-> Mit diesem Befehl werden mehrere "interfaces" verknüpft. Wenn Sie Probleme haben, die physischen NICs zu bestimmen, wird die öffentliche IP-Adresse des Servers weiterhin standardmäßig der ersten Schnittstelle zugeordnet.
+> Wenn Sie die Netzwerkverbindung zu Ihrem Server verlieren, folgen Sie den Schritten unter "**KVM öffnen**" in [dieser Anleitung](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Sobald wir die Namen unserer beiden Netzwerkkarten ermittelt haben, konfigurieren wir die Netzwerkkartenbindung im Betriebssystem. Erstellen Sie die Schnittstellendatei mit dem folgenden Befehl in einem Texteditor Ihrer Wahl:
+Führen Sie den folgenden Befehl aus, um die Interface-Namen abzurufen:
```bash
-vi /etc/network/interfaces
-```
-
-Zum Konfigurieren der Bond-Schnittstelle fügen Sie Folgendes am Ende der Datei ein:
-
-```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> Für den Parameter `hwaddress` empfehlen wir, die kleinere der beiden MAC-Adressen Ihrer Netzwerkkarten zu verwenden, da diese zur LACP-Fallback-Schnittstelle gehört.
+> Dieser Befehl zeigt mehrere Interfaces an. Wenn Sie Schwierigkeiten haben, Ihre physischen Interfaces zu identifizieren, ist an der ersten Schnittstelle standardmäßig die öffentliche IP-Adresse des Servers angehängt.
>
-> [!primary]
->
-> Sie müssen die letzte Zeile nur dann zur Datei hinzufügen, wenn Sie das private Netzwerk über IPv6 konfigurieren möchten.
->
+Hier ein Beispiel der Ausgabe:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Abschließend starten wir den Netzwerk-Daemon mit dem folgenden Befehl neu:
+Sobald Sie die Namen Ihrer Interfaces ermittelt haben, können Sie die Interface-Aggregation im Betriebssystem konfigurieren.
+
+### Konfiguration der Interface-Aggregation
+
+Wählen Sie den unten stehenden Tab entsprechend Ihrer Server-Konfiguration:
+
+- **Zwei Interfaces**: Advance-Server mit zwei physischen NICs.
+- **Vier Interfaces - Double LAG**: Scale- und High-Grade-Server mit OLA im Modus **Active - Double LAG** (öffentliche + private Aggregate). Dies erfordert die [Aktivierung von OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) im OVHcloud Kundencenter.
+- **Vier Interfaces - Fully Private**: Scale- und High-Grade-Server mit OLA im Modus **Active - Fully Private** (einzelnes privates Aggregat für vRack). Dies erfordert die [Aktivierung von OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) im OVHcloud Kundencenter.
+
+> [!tabs]
+> Zwei Interfaces
+>> Ersetzen Sie den Inhalt von `/etc/network/interfaces` durch Folgendes:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC-Adresse der öffentlichen Hauptschnittstelle des Servers
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC-Adresse der öffentlichen Hauptschnittstelle des Servers
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Vier Interfaces - Double LAG
+>> Diese Konfiguration aggregiert öffentliche Interfaces in `bond0` (mit öffentlicher IP) und private Interfaces in `bond1` (für vRack).
+>>
+>> Ersetzen Sie den Inhalt von `/etc/network/interfaces` durch Folgendes:
+>>
+>> **Statische IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC-Adresse der öffentlichen Hauptschnittstelle des Servers
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: Konfiguration des privaten Aggregats
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC-Adresse der privaten Hauptschnittstelle des Servers
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC-Adresse der öffentlichen Hauptschnittstelle des Servers
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: Konfiguration des privaten Aggregats
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC-Adresse der privaten Hauptschnittstelle des Servers
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Vier Interfaces - Fully Private
+>> Diese Konfiguration aggregiert alle physischen Interfaces in einem einzigen Aggregat ausschließlich für den vRack-Einsatz. Es gibt keine öffentliche IP-Konnektivität.
+>>
+>> > [!warning]
+>> >
+>> > Nach der Implementierung von OLA im Fully-Private-Modus ist die öffentliche IP nicht mehr erreichbar. Stellen Sie sicher, dass Sie über einen alternativen Zugangsweg verfügen (z. B. über einen anderen Server im vRack oder via KVM/IPMI), bevor Sie diese Konfiguration anwenden.
+>> >
+>>
+>> Ersetzen Sie den Inhalt von `/etc/network/interfaces` durch Folgendes:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # MAC-Adresse der privaten Hauptschnittstelle des Servers
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > Im Fully-Private-Modus verwendet das Aggregat die MAC-Adresse der **privaten Hauptschnittstelle**. Das Feld `address` sollte auf Ihre private vRack-IP gesetzt werden.
+>> >
+
+### Anwenden der Konfiguration
+
+Wenden Sie die Konfiguration an, indem Sie den Netzwerk-Daemon neu starten:
```bash
systemctl restart networking
```
-Dieser Neustart kann einige Sekunden dauern, da die Bond-Schnittstelle erstellt wird. Um zu testen, ob unsere Verbindung funktioniert, senden Sie einen Ping-Befehl an einen anderen Server im selben vRack. Wenn es funktioniert, sind Sie bereit. Ist dies nicht der Fall, überprüfen Sie Ihre Einstellungen oder starten Sie den Server neu.
+Dieser Neustart kann einige Sekunden dauern, da die Bond-Schnittstelle erstellt wird. Um zu testen, ob das Aggregat funktioniert, senden Sie einen Ping an einen anderen Server im selben vRack. Wenn es funktioniert, sind Sie fertig. Wenn nicht, überprüfen Sie Ihre Konfigurationen oder versuchen Sie, den Server neu zu starten.
## Weiterführende Informationen
-[Konfigurieren der OVHcloud Link Aggregation im OVHcloud Kundencenter](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[OVHcloud Link Aggregation im OVHcloud Kundencenter konfigurieren](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 12 oder Ubuntu 24.04 mit Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
[Konfigurieren der OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Treten Sie unserer [User Community](/links/community) bei.
\ No newline at end of file
+Treten Sie unserer [User Community](/links/community) bei.
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-asia.md
index 1b7861ab560..64d9c953478 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-asia.md
@@ -1,14 +1,35 @@
---
-title: How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11
-excerpt: "Enable OVHcloud Link Aggregation in your Debian server (from Debian 9 to Debian 11)"
-updated: 2026-01-09
+title: "How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11"
+excerpt: "Enable Link Aggregation in your Debian server (from Debian 9 to Debian 11, using ifupdown) to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in Debian (versions 9 to 11)**
+**This guide explains how to bond your interfaces to use them for OLA in Debian 9 to 11 (ifupdown configuration).**
+
+> [!warning]
+> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
+>
+> If your system's network configuration uses `Netplan` instead (Debian 12 or newer, Ubuntu 24.04), please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requirements
@@ -25,89 +46,241 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
---
+## Instructions
+
+> [!primary]
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
+>
+
> [!warning]
>
-> You will need to download the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
+> You will need to install the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Retrieving MAC addresses
+
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
+
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
+
+{.thumbnail}
+
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
->
-> If your system's network configuration uses `Netplan` instead, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-## Instructions
-
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
-
To do so, first log in to your [OVHcloud Control Panel](/links/manager). In the `Bare Metal Cloud`{.action} section, select your server from `Dedicated Servers`{.action} and click the `IPMI`{.action} tab (1).
+
Click the `IPMI`{.action} tab (1).
Next, click the `From a Java applet (KVM)`{.action} button (2).
-{.thumbnail}
-
- A JNLP program will download. Open the program to enter the IPMI. Log in using valid credentials for the server.
-
-By default, using an OVHcloud template, the NICs will be named either *ethX* or *enoX*. If you are not using an OVHcloud template, you can find the names of your interfaces using the following command:
-
-```bash
-ip a
-```
+### Retrieving interfaces names
> [!primary]
>
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Once we have determined the names of our two NICs, we will configure NIC bonding in the OS. Create the interfaces file in a text editor of your choice using the following command:
-
-```bash
-vi /etc/network/interfaces
-```
-
-This will open an empty text file. To configure the bond interface, insert the following at the bottom of the text file:
+To retrieve the names of the interfaces, execute the following command:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> For the `hwaddress` parameter, we recommend using the smaller of the two MAC addresses of your NICs, as it belongs to the LACP fallback interface.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-> [!primary]
->
-> You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
->
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Finally, we will restart the networking daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interfaces bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `address` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by restarting the networking daemon:
```bash
systemctl restart networking
```
-This restart may take several seconds since it is building the bond interface. To test that our bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double check your configurations or try rebooting the server.
+This restart may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-au.md
index 1b7861ab560..64d9c953478 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-au.md
@@ -1,14 +1,35 @@
---
-title: How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11
-excerpt: "Enable OVHcloud Link Aggregation in your Debian server (from Debian 9 to Debian 11)"
-updated: 2026-01-09
+title: "How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11"
+excerpt: "Enable Link Aggregation in your Debian server (from Debian 9 to Debian 11, using ifupdown) to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in Debian (versions 9 to 11)**
+**This guide explains how to bond your interfaces to use them for OLA in Debian 9 to 11 (ifupdown configuration).**
+
+> [!warning]
+> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
+>
+> If your system's network configuration uses `Netplan` instead (Debian 12 or newer, Ubuntu 24.04), please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requirements
@@ -25,89 +46,241 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
---
+## Instructions
+
+> [!primary]
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
+>
+
> [!warning]
>
-> You will need to download the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
+> You will need to install the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Retrieving MAC addresses
+
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
+
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
+
+{.thumbnail}
+
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
->
-> If your system's network configuration uses `Netplan` instead, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-## Instructions
-
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
-
To do so, first log in to your [OVHcloud Control Panel](/links/manager). In the `Bare Metal Cloud`{.action} section, select your server from `Dedicated Servers`{.action} and click the `IPMI`{.action} tab (1).
+
Click the `IPMI`{.action} tab (1).
Next, click the `From a Java applet (KVM)`{.action} button (2).
-{.thumbnail}
-
- A JNLP program will download. Open the program to enter the IPMI. Log in using valid credentials for the server.
-
-By default, using an OVHcloud template, the NICs will be named either *ethX* or *enoX*. If you are not using an OVHcloud template, you can find the names of your interfaces using the following command:
-
-```bash
-ip a
-```
+### Retrieving interfaces names
> [!primary]
>
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Once we have determined the names of our two NICs, we will configure NIC bonding in the OS. Create the interfaces file in a text editor of your choice using the following command:
-
-```bash
-vi /etc/network/interfaces
-```
-
-This will open an empty text file. To configure the bond interface, insert the following at the bottom of the text file:
+To retrieve the names of the interfaces, execute the following command:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> For the `hwaddress` parameter, we recommend using the smaller of the two MAC addresses of your NICs, as it belongs to the LACP fallback interface.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-> [!primary]
->
-> You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
->
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Finally, we will restart the networking daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interfaces bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `address` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by restarting the networking daemon:
```bash
systemctl restart networking
```
-This restart may take several seconds since it is building the bond interface. To test that our bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double check your configurations or try rebooting the server.
+This restart may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-ca.md
index 1b7861ab560..64d9c953478 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-ca.md
@@ -1,14 +1,35 @@
---
-title: How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11
-excerpt: "Enable OVHcloud Link Aggregation in your Debian server (from Debian 9 to Debian 11)"
-updated: 2026-01-09
+title: "How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11"
+excerpt: "Enable Link Aggregation in your Debian server (from Debian 9 to Debian 11, using ifupdown) to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in Debian (versions 9 to 11)**
+**This guide explains how to bond your interfaces to use them for OLA in Debian 9 to 11 (ifupdown configuration).**
+
+> [!warning]
+> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
+>
+> If your system's network configuration uses `Netplan` instead (Debian 12 or newer, Ubuntu 24.04), please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requirements
@@ -25,89 +46,241 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
---
+## Instructions
+
+> [!primary]
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
+>
+
> [!warning]
>
-> You will need to download the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
+> You will need to install the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Retrieving MAC addresses
+
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
+
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
+
+{.thumbnail}
+
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
->
-> If your system's network configuration uses `Netplan` instead, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-## Instructions
-
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
-
To do so, first log in to your [OVHcloud Control Panel](/links/manager). In the `Bare Metal Cloud`{.action} section, select your server from `Dedicated Servers`{.action} and click the `IPMI`{.action} tab (1).
+
Click the `IPMI`{.action} tab (1).
Next, click the `From a Java applet (KVM)`{.action} button (2).
-{.thumbnail}
-
- A JNLP program will download. Open the program to enter the IPMI. Log in using valid credentials for the server.
-
-By default, using an OVHcloud template, the NICs will be named either *ethX* or *enoX*. If you are not using an OVHcloud template, you can find the names of your interfaces using the following command:
-
-```bash
-ip a
-```
+### Retrieving interfaces names
> [!primary]
>
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Once we have determined the names of our two NICs, we will configure NIC bonding in the OS. Create the interfaces file in a text editor of your choice using the following command:
-
-```bash
-vi /etc/network/interfaces
-```
-
-This will open an empty text file. To configure the bond interface, insert the following at the bottom of the text file:
+To retrieve the names of the interfaces, execute the following command:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> For the `hwaddress` parameter, we recommend using the smaller of the two MAC addresses of your NICs, as it belongs to the LACP fallback interface.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-> [!primary]
->
-> You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
->
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Finally, we will restart the networking daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interfaces bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `address` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by restarting the networking daemon:
```bash
systemctl restart networking
```
-This restart may take several seconds since it is building the bond interface. To test that our bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double check your configurations or try rebooting the server.
+This restart may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-gb.md
index 64352572335..64d9c953478 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-gb.md
@@ -1,14 +1,35 @@
---
-title: How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11
-excerpt: "Enable OVHcloud Link Aggregation in your Debian server (from Debian 9 to Debian 11)"
-updated: 2026-01-09
+title: "How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11"
+excerpt: "Enable Link Aggregation in your Debian server (from Debian 9 to Debian 11, using ifupdown) to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in Debian (versions 9 to 11)**
+**This guide explains how to bond your interfaces to use them for OLA in Debian 9 to 11 (ifupdown configuration).**
+
+> [!warning]
+> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
+>
+> If your system's network configuration uses `Netplan` instead (Debian 12 or newer, Ubuntu 24.04), please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requirements
@@ -25,89 +46,241 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
---
+## Instructions
+
+> [!primary]
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
+>
+
> [!warning]
>
-> You will need to download the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
+> You will need to install the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Retrieving MAC addresses
+
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
+
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
+
+{.thumbnail}
+
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
->
-> If your system's network configuration uses `Netplan` instead, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-## Instructions
-
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
Click the `IPMI`{.action} tab (1).
Next, click the `From a Java applet (KVM)`{.action} button (2).
-{.thumbnail}
-
- A JNLP program will download. Open the program to enter the IPMI. Log in using valid credentials for the server.
-
-By default, using an OVHcloud template, the NICs will be named either *ethX* or *enoX*. If you are not using an OVHcloud template, you can find the names of your interfaces using the following command:
-
-```bash
-ip a
-```
+### Retrieving interfaces names
> [!primary]
>
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Once we have determined the names of our two NICs, we will configure NIC bonding in the OS. Create the interfaces file in a text editor of your choice using the following command:
-
-```bash
-vi /etc/network/interfaces
-```
-
-This will open an empty text file. To configure the bond interface, insert the following at the bottom of the text file:
+To retrieve the names of the interfaces, execute the following command:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> For the `hwaddress` parameter, we recommend using the smaller of the two MAC addresses of your NICs, as it belongs to the LACP fallback interface.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-> [!primary]
->
-> You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
->
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Finally, we will restart the networking daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interfaces bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `address` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by restarting the networking daemon:
```bash
systemctl restart networking
```
-This restart may take several seconds since it is building the bond interface. To test that our bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double check your configurations or try rebooting the server.
+This restart may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-ie.md
index 1b7861ab560..64d9c953478 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-ie.md
@@ -1,14 +1,35 @@
---
-title: How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11
-excerpt: "Enable OVHcloud Link Aggregation in your Debian server (from Debian 9 to Debian 11)"
-updated: 2026-01-09
+title: "How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11"
+excerpt: "Enable Link Aggregation in your Debian server (from Debian 9 to Debian 11, using ifupdown) to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in Debian (versions 9 to 11)**
+**This guide explains how to bond your interfaces to use them for OLA in Debian 9 to 11 (ifupdown configuration).**
+
+> [!warning]
+> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
+>
+> If your system's network configuration uses `Netplan` instead (Debian 12 or newer, Ubuntu 24.04), please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requirements
@@ -25,89 +46,241 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
---
+## Instructions
+
+> [!primary]
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
+>
+
> [!warning]
>
-> You will need to download the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
+> You will need to install the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Retrieving MAC addresses
+
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
+
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
+
+{.thumbnail}
+
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
->
-> If your system's network configuration uses `Netplan` instead, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-## Instructions
-
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
-
To do so, first log in to your [OVHcloud Control Panel](/links/manager). In the `Bare Metal Cloud`{.action} section, select your server from `Dedicated Servers`{.action} and click the `IPMI`{.action} tab (1).
+
Click the `IPMI`{.action} tab (1).
Next, click the `From a Java applet (KVM)`{.action} button (2).
-{.thumbnail}
-
- A JNLP program will download. Open the program to enter the IPMI. Log in using valid credentials for the server.
-
-By default, using an OVHcloud template, the NICs will be named either *ethX* or *enoX*. If you are not using an OVHcloud template, you can find the names of your interfaces using the following command:
-
-```bash
-ip a
-```
+### Retrieving interfaces names
> [!primary]
>
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Once we have determined the names of our two NICs, we will configure NIC bonding in the OS. Create the interfaces file in a text editor of your choice using the following command:
-
-```bash
-vi /etc/network/interfaces
-```
-
-This will open an empty text file. To configure the bond interface, insert the following at the bottom of the text file:
+To retrieve the names of the interfaces, execute the following command:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> For the `hwaddress` parameter, we recommend using the smaller of the two MAC addresses of your NICs, as it belongs to the LACP fallback interface.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-> [!primary]
->
-> You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
->
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Finally, we will restart the networking daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interfaces bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `address` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by restarting the networking daemon:
```bash
systemctl restart networking
```
-This restart may take several seconds since it is building the bond interface. To test that our bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double check your configurations or try rebooting the server.
+This restart may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-sg.md
index 1b7861ab560..64d9c953478 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-sg.md
@@ -1,14 +1,35 @@
---
-title: How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11
-excerpt: "Enable OVHcloud Link Aggregation in your Debian server (from Debian 9 to Debian 11)"
-updated: 2026-01-09
+title: "How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11"
+excerpt: "Enable Link Aggregation in your Debian server (from Debian 9 to Debian 11, using ifupdown) to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in Debian (versions 9 to 11)**
+**This guide explains how to bond your interfaces to use them for OLA in Debian 9 to 11 (ifupdown configuration).**
+
+> [!warning]
+> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
+>
+> If your system's network configuration uses `Netplan` instead (Debian 12 or newer, Ubuntu 24.04), please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requirements
@@ -25,89 +46,241 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
---
+## Instructions
+
+> [!primary]
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
+>
+
> [!warning]
>
-> You will need to download the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
+> You will need to install the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Retrieving MAC addresses
+
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
+
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
+
+{.thumbnail}
+
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
->
-> If your system's network configuration uses `Netplan` instead, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-## Instructions
-
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
-
To do so, first log in to your [OVHcloud Control Panel](/links/manager). In the `Bare Metal Cloud`{.action} section, select your server from `Dedicated Servers`{.action} and click the `IPMI`{.action} tab (1).
+
Click the `IPMI`{.action} tab (1).
Next, click the `From a Java applet (KVM)`{.action} button (2).
-{.thumbnail}
-
- A JNLP program will download. Open the program to enter the IPMI. Log in using valid credentials for the server.
-
-By default, using an OVHcloud template, the NICs will be named either *ethX* or *enoX*. If you are not using an OVHcloud template, you can find the names of your interfaces using the following command:
-
-```bash
-ip a
-```
+### Retrieving interfaces names
> [!primary]
>
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Once we have determined the names of our two NICs, we will configure NIC bonding in the OS. Create the interfaces file in a text editor of your choice using the following command:
-
-```bash
-vi /etc/network/interfaces
-```
-
-This will open an empty text file. To configure the bond interface, insert the following at the bottom of the text file:
+To retrieve the names of the interfaces, execute the following command:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> For the `hwaddress` parameter, we recommend using the smaller of the two MAC addresses of your NICs, as it belongs to the LACP fallback interface.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-> [!primary]
->
-> You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
->
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Finally, we will restart the networking daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interfaces bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `address` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by restarting the networking daemon:
```bash
systemctl restart networking
```
-This restart may take several seconds since it is building the bond interface. To test that our bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double check your configurations or try rebooting the server.
+This restart may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-us.md
index 1b7861ab560..64d9c953478 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.en-us.md
@@ -1,14 +1,35 @@
---
-title: How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11
-excerpt: "Enable OVHcloud Link Aggregation in your Debian server (from Debian 9 to Debian 11)"
-updated: 2026-01-09
+title: "How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11"
+excerpt: "Enable Link Aggregation in your Debian server (from Debian 9 to Debian 11, using ifupdown) to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in Debian (versions 9 to 11)**
+**This guide explains how to bond your interfaces to use them for OLA in Debian 9 to 11 (ifupdown configuration).**
+
+> [!warning]
+> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
+>
+> If your system's network configuration uses `Netplan` instead (Debian 12 or newer, Ubuntu 24.04), please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requirements
@@ -25,89 +46,241 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
---
+## Instructions
+
+> [!primary]
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
+>
+
> [!warning]
>
-> You will need to download the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
+> You will need to install the ifenslave package on the server before enabling OLA in the OVHcloud Control Panel or API. To do so, please use the following command:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Retrieving MAC addresses
+
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
+
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
+
+{.thumbnail}
+
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> This guide provides instructions for configuring network interface bonding specifically using `ifupdown`, whose configuration file is located at `/etc/network/interfaces`. It also applies to the rescue system.
->
-> If your system's network configuration uses `Netplan` instead, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-## Instructions
-
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
-
To do so, first log in to your [OVHcloud Control Panel](/links/manager). In the `Bare Metal Cloud`{.action} section, select your server from `Dedicated Servers`{.action} and click the `IPMI`{.action} tab (1).
+
Click the `IPMI`{.action} tab (1).
Next, click the `From a Java applet (KVM)`{.action} button (2).
-{.thumbnail}
-
- A JNLP program will download. Open the program to enter the IPMI. Log in using valid credentials for the server.
-
-By default, using an OVHcloud template, the NICs will be named either *ethX* or *enoX*. If you are not using an OVHcloud template, you can find the names of your interfaces using the following command:
-
-```bash
-ip a
-```
+### Retrieving interfaces names
> [!primary]
>
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Once we have determined the names of our two NICs, we will configure NIC bonding in the OS. Create the interfaces file in a text editor of your choice using the following command:
-
-```bash
-vi /etc/network/interfaces
-```
-
-This will open an empty text file. To configure the bond interface, insert the following at the bottom of the text file:
+To retrieve the names of the interfaces, execute the following command:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> For the `hwaddress` parameter, we recommend using the smaller of the two MAC addresses of your NICs, as it belongs to the LACP fallback interface.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-> [!primary]
->
-> You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
->
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Finally, we will restart the networking daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interfaces bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # MAC address of the server's main public interface
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optional: private bond configuration
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Replace the content of `/etc/network/interfaces` with the following:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # MAC address of the server's main private interface
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `address` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by restarting the networking daemon:
```bash
systemctl restart networking
```
-This restart may take several seconds since it is building the bond interface. To test that our bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double check your configurations or try rebooting the server.
+This restart may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.es-es.md
index 3ec449b5ea5..1ca2c4700ea 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.es-es.md
@@ -1,18 +1,39 @@
---
-title: 'Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9 a 11'
-excerpt: 'Activar el servicio OVHcloud Link Aggregation en un servidor Debian 9 a 11'
-updated: 2026-01-09
+title: "Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 9 a 11"
+excerpt: "Active la agregación de enlaces en su servidor Debian (de Debian 9 a Debian 11, con ifupdown) para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red"
+updated: 2026-04-20
---
+
+
## Objetivo
-La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible.
+La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible. El ancho de banda disponible también se duplica gracias a la agregación.
+La agregación se basa en la tecnología IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Descubra cómo agrupar sus NIC (controladores de interfaz de red) para utilizarlos con el servicio OLA en Debian (versiones 9 a 11).**
+**Esta guía explica cómo configurar sus interfaces en agregación para utilizarlas con OLA en Debian 9 a 11 (configuración ifupdown).**
+
+> [!warning]
+> Esta guía proporciona instrucciones para configurar la agregación de interfaces de red específicamente con `ifupdown`, cuyo archivo de configuración es `/etc/network/interfaces`. También es aplicable al modo de rescate.
+>
+> Si la configuración de red de su sistema utiliza `Netplan` (Debian 12 o superior, Ubuntu 24.04), consulte [esta guía](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requisitos
-- [Configurar un NIC para el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -25,89 +46,241 @@ La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la
---
+## Procedimiento
+
+> [!primary]
+> Los valores (direcciones MAC, direcciones IP, etc.) que aparecen en las configuraciones y ejemplos a continuación se proporcionan como ejemplos. Por supuesto, debe reemplazarlos por los suyos propios.
+>
+
> [!warning]
>
-> Es necesario descargar el paquete ifenslave en el servidor antes de activar el servicio OLA en el área de cliente de OVHcloud o en la API. Para ello, utilice el siguiente comando:
+> Es necesario instalar el paquete ifenslave en el servidor antes de activar el servicio OLA en el área de cliente de OVHcloud o en la API. Para ello, utilice el siguiente comando:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
-> [!primary]
->
-> Esta guía proporciona instrucciones para configurar la agregación de interfaces de red específicamente con `ifupdown`, cuyo archivo de configuración es `/etc/network/interfaces`. También es aplicable al modo de rescate.
->
-> Si la configuración de red de su sistema utiliza `Netplan`, consulte [esta guía](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
->
+### Obtención de las direcciones MAC
-## Procedimiento
+Conéctese al [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione su servidor en **Servidores dedicados**.
-Nuestros NIC en OLA tienen una configuración privada-privada, por lo que no es posible acceder al servidor por SSH. Así pues, es necesario utilizar la herramienta IPMI para acceder al servidor.
-
Para ello, en primer lugar, conéctese al [área de cliente de OVHcloud](/links/manager). En la pestaña `Bare Metal Cloud`{.action}, haga clic en `Servidores dedicados`{.action} y seleccione el servidor. A continuación, abra la pestaña `IPMI`{.action} (1).
+Vaya a la pestaña `Interfaces de red`{.action} y tome nota de las direcciones MAC de cada interfaz (pública/privada) que se muestran en la parte inferior del menú.
-Haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
+{.thumbnail}
-{.thumbnail}
+> [!primary]
+> Tenga en cuenta que la dirección MAC de la interfaz **pública principal** es la que recibe las ofertas DHCP, tanto en el sistema operativo del servidor como en el modo de rescate. Esta interfaz gestiona la conectividad pública en la configuración predeterminada.
+>
+> Además, la dirección MAC de la interfaz **privada principal** es la de menor valor. En la imagen de ejemplo anterior, esta es la dirección `a1:b2:c3:d4:e5:d6`.
+>
-Se descargará un programa JNLP. Abra el programa para acceder a IPMI e introduzca las claves asociadas al servidor.
+Dado que nuestros NIC en OLA tienen una configuración privada-privada, no es posible acceder al servidor por SSH. Por lo tanto, es necesario utilizar la herramienta IPMI para acceder al servidor.
+
Haga clic en la pestaña `IPMI`{.action} (1).
-Por defecto, al utilizar una plantilla de OVHcloud, el nombre asignado de los NIC será o bien *ethX* o *enoX*. Si no utiliza una plantilla de OVHcloud, puede consultar el nombre de las interfaces utilizando el siguiente comando:
+A continuación, haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
-```bash
-ip a
-```
+### Obtención de los nombres de las interfaces
> [!primary]
>
-> Este comando mostrará diversas interfaces. Si tiene dificultad para determinar qué interfaces corresponden a sus NIC físicos, la primera interfaz todavía tendrá la dirección de la IP pública del servidor asignada por defecto.
+> Si pierde la conexión de red con su servidor, siga los pasos de "**Abrir KVM**" de [esta guía](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Una vez que haya determinado el nombre de los dos NIC, ya puede asociar los NIC en el sistema operativo. Para ello, cree el siguiente archivo de configuración en el editor de texto que desee:
+Para obtener los nombres de las interfaces, ejecute el siguiente comando:
```bash
-vi /etc/network/interfaces
-```
-
-Se abrirá un archivo de texto vacío. Para configurar la interfaz de enlace, introduzca el siguiente texto al final del archivo:
-
-```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> Para el parámetro `hwaddress`, recomendamos utilizar la menor de las dos direcciones MAC de sus NIC, ya que pertenece a la interfaz de respaldo (fallback) LACP.
+> Este comando mostrará diversas interfaces. Si tiene dificultad para determinar cuáles son sus interfaces físicas, la primera interfaz todavía tendrá la dirección IP pública del servidor asignada por defecto.
>
-> [!primary]
->
-> Añada la última línea de comando si piensa configurar una red privada a través de IPv6.
->
+Aquí tiene un ejemplo de salida:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Por último, reinicie el servicio de red utilizando el siguiente comando:
+Una vez que haya determinado los nombres de sus interfaces, puede configurar la agregación de interfaces en el sistema operativo.
+
+### Configuración de la agregación de interfaces
+
+Seleccione la pestaña siguiente que corresponda a la configuración de su servidor:
+
+- **Dos interfaces**: servidores Advance con dos NIC físicas.
+- **Cuatro interfaces - Double LAG**: servidores Scale y High-Grade con OLA en modo **Active - Double LAG** (agregados público + privado). Requiere [activar OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) en el área de cliente de OVHcloud.
+- **Cuatro interfaces - Fully Private**: servidores Scale y High-Grade con OLA en modo **Active - Fully Private** (único agregado privado para vRack). Requiere [activar OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) en el área de cliente de OVHcloud.
+
+> [!tabs]
+> Dos interfaces
+>> Sustituya el contenido de `/etc/network/interfaces` por lo siguiente:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Dirección MAC de la interfaz pública principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Dirección MAC de la interfaz pública principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Cuatro interfaces - Double LAG
+>> Esta configuración agrupa las interfaces públicas en `bond0` (con IP pública) y las interfaces privadas en `bond1` (para vRack).
+>>
+>> Sustituya el contenido de `/etc/network/interfaces` por lo siguiente:
+>>
+>> **IP estática**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Dirección MAC de la interfaz pública principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opcional: configuración del agregado privado
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Dirección MAC de la interfaz privada principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Dirección MAC de la interfaz pública principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opcional: configuración del agregado privado
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Dirección MAC de la interfaz privada principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Cuatro interfaces - Fully Private
+>> Esta configuración agrega todas las interfaces físicas en un único agregado exclusivamente para uso con vRack. No hay conectividad IP pública.
+>>
+>> > [!warning]
+>> >
+>> > Tras la implementación de OLA en modo Fully Private, la IP pública deja de estar accesible. Asegúrese de tener un medio alternativo de acceso (p. ej., a través de otro servidor en el vRack o mediante KVM/IPMI) antes de aplicar esta configuración.
+>> >
+>>
+>> Sustituya el contenido de `/etc/network/interfaces` por lo siguiente:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # Dirección MAC de la interfaz privada principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > En modo Fully Private, el agregado utiliza la dirección MAC de la interfaz **privada principal**. El campo `address` debe configurarse con su IP privada de vRack.
+>> >
+
+### Aplicación de la configuración
+
+Aplique la configuración reiniciando el servicio de red:
```bash
systemctl restart networking
```
-Este reinicio puede tardar unos segundos ya que se está creando la interfaz de enlace. Para comprobar que el enlace funciona correctamente, haga ping en otro servidor en el mismo vRack. Si funciona, ha configurado el enlace correctamente. En caso contrario, compruebe que la configuración es correcta o reinicie el servidor.
+Este reinicio puede tardar unos segundos ya que se está creando la interfaz de agregado. Para comprobar que el agregado funciona correctamente, haga ping a otro servidor en el mismo vRack. Si funciona, está todo listo. En caso contrario, compruebe sus configuraciones o intente reiniciar el servidor.
## Más información
-[Configurar el servicio OVHcloud Link Aggregation desde el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
[Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
[Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
+Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.es-us.md
index 3ec449b5ea5..1ca2c4700ea 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.es-us.md
@@ -1,18 +1,39 @@
---
-title: 'Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9 a 11'
-excerpt: 'Activar el servicio OVHcloud Link Aggregation en un servidor Debian 9 a 11'
-updated: 2026-01-09
+title: "Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 9 a 11"
+excerpt: "Active la agregación de enlaces en su servidor Debian (de Debian 9 a Debian 11, con ifupdown) para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red"
+updated: 2026-04-20
---
+
+
## Objetivo
-La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible.
+La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible. El ancho de banda disponible también se duplica gracias a la agregación.
+La agregación se basa en la tecnología IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Descubra cómo agrupar sus NIC (controladores de interfaz de red) para utilizarlos con el servicio OLA en Debian (versiones 9 a 11).**
+**Esta guía explica cómo configurar sus interfaces en agregación para utilizarlas con OLA en Debian 9 a 11 (configuración ifupdown).**
+
+> [!warning]
+> Esta guía proporciona instrucciones para configurar la agregación de interfaces de red específicamente con `ifupdown`, cuyo archivo de configuración es `/etc/network/interfaces`. También es aplicable al modo de rescate.
+>
+> Si la configuración de red de su sistema utiliza `Netplan` (Debian 12 o superior, Ubuntu 24.04), consulte [esta guía](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requisitos
-- [Configurar un NIC para el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -25,89 +46,241 @@ La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la
---
+## Procedimiento
+
+> [!primary]
+> Los valores (direcciones MAC, direcciones IP, etc.) que aparecen en las configuraciones y ejemplos a continuación se proporcionan como ejemplos. Por supuesto, debe reemplazarlos por los suyos propios.
+>
+
> [!warning]
>
-> Es necesario descargar el paquete ifenslave en el servidor antes de activar el servicio OLA en el área de cliente de OVHcloud o en la API. Para ello, utilice el siguiente comando:
+> Es necesario instalar el paquete ifenslave en el servidor antes de activar el servicio OLA en el área de cliente de OVHcloud o en la API. Para ello, utilice el siguiente comando:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
-> [!primary]
->
-> Esta guía proporciona instrucciones para configurar la agregación de interfaces de red específicamente con `ifupdown`, cuyo archivo de configuración es `/etc/network/interfaces`. También es aplicable al modo de rescate.
->
-> Si la configuración de red de su sistema utiliza `Netplan`, consulte [esta guía](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
->
+### Obtención de las direcciones MAC
-## Procedimiento
+Conéctese al [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione su servidor en **Servidores dedicados**.
-Nuestros NIC en OLA tienen una configuración privada-privada, por lo que no es posible acceder al servidor por SSH. Así pues, es necesario utilizar la herramienta IPMI para acceder al servidor.
-
Para ello, en primer lugar, conéctese al [área de cliente de OVHcloud](/links/manager). En la pestaña `Bare Metal Cloud`{.action}, haga clic en `Servidores dedicados`{.action} y seleccione el servidor. A continuación, abra la pestaña `IPMI`{.action} (1).
+Vaya a la pestaña `Interfaces de red`{.action} y tome nota de las direcciones MAC de cada interfaz (pública/privada) que se muestran en la parte inferior del menú.
-Haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
+{.thumbnail}
-{.thumbnail}
+> [!primary]
+> Tenga en cuenta que la dirección MAC de la interfaz **pública principal** es la que recibe las ofertas DHCP, tanto en el sistema operativo del servidor como en el modo de rescate. Esta interfaz gestiona la conectividad pública en la configuración predeterminada.
+>
+> Además, la dirección MAC de la interfaz **privada principal** es la de menor valor. En la imagen de ejemplo anterior, esta es la dirección `a1:b2:c3:d4:e5:d6`.
+>
-Se descargará un programa JNLP. Abra el programa para acceder a IPMI e introduzca las claves asociadas al servidor.
+Dado que nuestros NIC en OLA tienen una configuración privada-privada, no es posible acceder al servidor por SSH. Por lo tanto, es necesario utilizar la herramienta IPMI para acceder al servidor.
+
Haga clic en la pestaña `IPMI`{.action} (1).
-Por defecto, al utilizar una plantilla de OVHcloud, el nombre asignado de los NIC será o bien *ethX* o *enoX*. Si no utiliza una plantilla de OVHcloud, puede consultar el nombre de las interfaces utilizando el siguiente comando:
+A continuación, haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
-```bash
-ip a
-```
+### Obtención de los nombres de las interfaces
> [!primary]
>
-> Este comando mostrará diversas interfaces. Si tiene dificultad para determinar qué interfaces corresponden a sus NIC físicos, la primera interfaz todavía tendrá la dirección de la IP pública del servidor asignada por defecto.
+> Si pierde la conexión de red con su servidor, siga los pasos de "**Abrir KVM**" de [esta guía](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Una vez que haya determinado el nombre de los dos NIC, ya puede asociar los NIC en el sistema operativo. Para ello, cree el siguiente archivo de configuración en el editor de texto que desee:
+Para obtener los nombres de las interfaces, ejecute el siguiente comando:
```bash
-vi /etc/network/interfaces
-```
-
-Se abrirá un archivo de texto vacío. Para configurar la interfaz de enlace, introduzca el siguiente texto al final del archivo:
-
-```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> Para el parámetro `hwaddress`, recomendamos utilizar la menor de las dos direcciones MAC de sus NIC, ya que pertenece a la interfaz de respaldo (fallback) LACP.
+> Este comando mostrará diversas interfaces. Si tiene dificultad para determinar cuáles son sus interfaces físicas, la primera interfaz todavía tendrá la dirección IP pública del servidor asignada por defecto.
>
-> [!primary]
->
-> Añada la última línea de comando si piensa configurar una red privada a través de IPv6.
->
+Aquí tiene un ejemplo de salida:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Por último, reinicie el servicio de red utilizando el siguiente comando:
+Una vez que haya determinado los nombres de sus interfaces, puede configurar la agregación de interfaces en el sistema operativo.
+
+### Configuración de la agregación de interfaces
+
+Seleccione la pestaña siguiente que corresponda a la configuración de su servidor:
+
+- **Dos interfaces**: servidores Advance con dos NIC físicas.
+- **Cuatro interfaces - Double LAG**: servidores Scale y High-Grade con OLA en modo **Active - Double LAG** (agregados público + privado). Requiere [activar OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) en el área de cliente de OVHcloud.
+- **Cuatro interfaces - Fully Private**: servidores Scale y High-Grade con OLA en modo **Active - Fully Private** (único agregado privado para vRack). Requiere [activar OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) en el área de cliente de OVHcloud.
+
+> [!tabs]
+> Dos interfaces
+>> Sustituya el contenido de `/etc/network/interfaces` por lo siguiente:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Dirección MAC de la interfaz pública principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Dirección MAC de la interfaz pública principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Cuatro interfaces - Double LAG
+>> Esta configuración agrupa las interfaces públicas en `bond0` (con IP pública) y las interfaces privadas en `bond1` (para vRack).
+>>
+>> Sustituya el contenido de `/etc/network/interfaces` por lo siguiente:
+>>
+>> **IP estática**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Dirección MAC de la interfaz pública principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opcional: configuración del agregado privado
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Dirección MAC de la interfaz privada principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Dirección MAC de la interfaz pública principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opcional: configuración del agregado privado
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Dirección MAC de la interfaz privada principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Cuatro interfaces - Fully Private
+>> Esta configuración agrega todas las interfaces físicas en un único agregado exclusivamente para uso con vRack. No hay conectividad IP pública.
+>>
+>> > [!warning]
+>> >
+>> > Tras la implementación de OLA en modo Fully Private, la IP pública deja de estar accesible. Asegúrese de tener un medio alternativo de acceso (p. ej., a través de otro servidor en el vRack o mediante KVM/IPMI) antes de aplicar esta configuración.
+>> >
+>>
+>> Sustituya el contenido de `/etc/network/interfaces` por lo siguiente:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # Dirección MAC de la interfaz privada principal del servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > En modo Fully Private, el agregado utiliza la dirección MAC de la interfaz **privada principal**. El campo `address` debe configurarse con su IP privada de vRack.
+>> >
+
+### Aplicación de la configuración
+
+Aplique la configuración reiniciando el servicio de red:
```bash
systemctl restart networking
```
-Este reinicio puede tardar unos segundos ya que se está creando la interfaz de enlace. Para comprobar que el enlace funciona correctamente, haga ping en otro servidor en el mismo vRack. Si funciona, ha configurado el enlace correctamente. En caso contrario, compruebe que la configuración es correcta o reinicie el servidor.
+Este reinicio puede tardar unos segundos ya que se está creando la interfaz de agregado. Para comprobar que el agregado funciona correctamente, haga ping a otro servidor en el mismo vRack. Si funciona, está todo listo. En caso contrario, compruebe sus configuraciones o intente reiniciar el servidor.
## Más información
-[Configurar el servicio OVHcloud Link Aggregation desde el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
[Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
[Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
+Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.fr-ca.md
index ffb06cf8b4b..cde038c0578 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.fr-ca.md
@@ -1,14 +1,35 @@
---
-title: 'Comment configurer votre NIC pour la fonctionnalité OVHcloud Link Aggregation sur Debian 9 à 11'
-excerpt: 'Activer OVHcloud Link Aggregation sur votre Debian (versions 9 à 11)'
-updated: 2026-01-09
+title: "Comment configurer votre NIC pour la fonctionnalité OVHcloud Link Aggregation sur Debian 9 à 11"
+excerpt: "Activer l'agrégation de liens OVHcloud Link Aggregation sur votre serveur Debian (de Debian 9 à Debian 11, avec ifupdown) pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau"
+updated: 2026-04-20
---
+
+
## Objectif
-La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible.
+La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible. La bande passante disponible est également doublée grâce à l'agrégation.
+L'agrégation repose sur la technologie IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Ce guide explique comment configurer vos interfaces en agrégation pour les utiliser avec OLA sous Debian 9 à 11 (configuration ifupdown).**
-**Découvrez comment regrouper vos NIC (Network Interface Controller) pour les utiliser avec le service OLA sur Debian (versions de 9 à 11).**
+> [!warning]
+> Ce guide fournit des instructions pour configurer l'agrégation d'interfaces réseau spécifiquement avec `ifupdown`, dont le fichier de configuration se trouve à l'emplacement `/etc/network/interfaces`. Il est aussi applicable au mode rescue.
+>
+> Si la configuration réseau de votre système utilise plutôt `Netplan` (Debian 12 ou plus récent, Ubuntu 24.04), veuillez vous référer à [ce guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Prérequis
@@ -25,89 +46,242 @@ La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour
---
+## En pratique
+
+> [!primary]
+> Les valeurs (adresses MAC, adresses IP, etc.) indiquées dans les configurations et exemples ci-dessous sont fournies à titre d'exemple. Vous devez bien sûr les remplacer par vos propres valeurs.
+>
+
> [!warning]
>
-> Vous devez télécharger le paquet ifenslave sur votre serveur avant d’activer la fonctionnalité OLA sur l’API ou l’espace client OVHcloud. Pour ce faire, utilisez la commande suivante :
+> Vous devez installer le paquet ifenslave sur le serveur avant d'activer OLA dans l'espace client OVHcloud ou via l'API. Pour ce faire, utilisez la commande suivante :
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Récupération des adresses MAC
+
+Connectez-vous à l'[espace client OVHcloud](/links/manager), accédez à la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur dans **Serveurs dédiés**.
+
+Rendez-vous dans l'onglet `Interfaces réseau`{.action} et notez les adresses MAC de chaque interface (publique/privée) qui sont affichées en bas du menu.
+
+{.thumbnail}
+
> [!primary]
+> Veuillez noter que l'adresse MAC de l'interface **publique principale** est celle qui reçoit les offres DHCP, aussi bien dans le système d'exploitation du serveur qu'en mode rescue. Cette interface gère la connectivité publique dans la configuration par défaut.
>
-> Ce guide fournit des instructions pour configurer l'agrégation d'interfaces réseau spécifiquement avec `ifupdown`, dont le fichier de configuration est `/etc/network/interfaces`. Il est aussi applicable au mode rescue.
+> Quant à l'adresse MAC de l'interface **privée principale**, il s'agit de celle dont la valeur est la plus faible. Dans l'image exemple ci-dessus, il s'agit de l'adresse `a1:b2:c3:d4:e5:d6`.
>
> Si la configuration réseau de votre système utilise plutôt `Netplan`, veuillez vous référer à [ce guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
>
-## En pratique
-
Étant donné que nous avons une configuration privée-privée pour nos NIC sur OLA, il est impossible de se connecter en SSH au serveur. Par conséquent, vous devrez utiliser l’outil IPMI pour accéder au serveur.
-
Pour cela, connectez-vous à votre [espace client OVHcloud](/links/manager) et allez à l'onglet `Bare Metal Cloud`{.action}. Sélectionnez votre serveur dans la liste sous la rubrique `Serveurs dédiés`{.action}.
-Cliquez ensuite sur l'onglet `IPMI`{.action} (1) puis sur le bouton `Depuis un applet Java (KVM)`{.action} (2).
+Maintenant que vous savez quelles adresses MAC sont associées à chaque type (public/privé) d'interface, vous devez récupérer les noms des interfaces.
-{.thumbnail}
-
-Un logiciel JNLP sera téléchargé. Lancez le logiciel pour accéder à l’IPMI. Connectez-vous en utilisant les informations d’identification associées au serveur.
-
-Par défaut, en utilisant un modèle d’OVHcloud, les NIC seront nommés soit *ethX*, soit *enoX*. Si vous n’utilisez pas un modèle OVHcloud, vous pouvez retrouver les noms de vos interfaces en utilisant la commande suivante :
-
-```bash
-ip a
-```
+### Récupération des noms d'interfaces
> [!primary]
>
-> Cette commande retournera plusieurs « interfaces ». Si vous avez du mal à identifier vos NIC physiques, la première interface aura toujours l’adresse IP publique du serveur assignée par défaut.
+> Si vous perdez la connexion réseau à votre serveur, suivez les étapes intitulées « **Ouvrir un KVM** » de [ce guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Une fois les noms de vos deux NIC identifiés, il faut à présent créer le NIC bonding ou agrégation de lien sur le système d’exploitation. Pour ce faire, créez le fichier d’interfaces sur l'éditeur de texte de votre choix à l’aide de la commande suivante :
-
-```bash
-vi /etc/network/interfaces
-```
-
-Ceci ouvrira un fichier texte vide. Pour configurer l’interface d’agrégation, insérez les lignes suivantes au bout du fichier texte :
+Pour récupérer les noms des interfaces, lancez la commande suivante :
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> Pour le paramètre `hwaddress`, nous recommandons d'utiliser la plus petite des deux adresses MAC de vos NIC, car il elle appartient à l'interface de secours (fallback) LACP.
+> Cette commande va afficher de nombreuses interfaces. Si vous avez du mal à déterminer lesquelles sont vos interfaces physiques, l'adresse IP publique du serveur reste attachée par défaut à la première interface.
>
-> [!primary]
->
-> Il vous suffit d’ajouter la dernière ligne à ce fichier si vous envisagez de configurer un réseau privé via IPv6.
->
+Voici un exemple de sortie :
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Pour finir, il faudra redémarrer le service réseau à l’aide de la commande suivante :
+Une fois que vous avez déterminé les noms de vos interfaces, vous pouvez configurer l'agrégation d'interfaces dans le système d'exploitation.
+
+### Configuration de l'agrégation d'interfaces
+
+Sélectionnez l'onglet ci-dessous correspondant à la configuration de votre serveur :
+
+- **Deux interfaces** : serveurs Advance avec deux cartes réseau physiques.
+- **Quatre interfaces - Double LAG** : serveurs Scale et High Grade avec OLA en mode **Active - Double LAG** (agrégats public + privé). Cela nécessite l'[activation d'OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) dans l'espace client OVHcloud.
+- **Quatre interfaces - Fully Private** : serveurs Scale et High Grade avec OLA en mode **Active - Fully Private** (agrégat privé unique pour le vRack). Cela nécessite l'[activation d'OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) dans l'espace client OVHcloud.
+
+> [!tabs]
+> Deux interfaces
+>> Remplacez le contenu de `/etc/network/interfaces` par ce qui suit :
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Adresse MAC de l'interface publique principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Adresse MAC de l'interface publique principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Quatre interfaces - Double LAG
+>> Cette configuration lie les interfaces publiques dans `bond0` (avec l'IP publique) et les interfaces privées dans `bond1` (pour le vRack).
+>>
+>> Remplacez le contenu de `/etc/network/interfaces` par ce qui suit :
+>>
+>> **IP fixe**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Adresse MAC de l'interface publique principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optionnel : configuration de l'agrégat privé
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Adresse MAC de l'interface privée principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Adresse MAC de l'interface publique principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optionnel : configuration de l'agrégat privé
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Adresse MAC de l'interface privée principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Quatre interfaces - Fully Private
+>> Cette configuration agrège toutes les interfaces physiques en un seul agrégat pour une utilisation vRack uniquement. Il n'y a pas de connectivité IP publique.
+>>
+>> > [!warning]
+>> >
+>> > Suite à la mise en œuvre d'OLA en mode Fully Private, l'IP publique n'est plus accessible. Assurez-vous de disposer d'un moyen d'accès alternatif (par exemple via un autre serveur dans le vRack, ou via KVM/IPMI) avant d'appliquer cette configuration.
+>> >
+>>
+>> Remplacez le contenu de `/etc/network/interfaces` par ce qui suit :
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # Adresse MAC de l'interface privée principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > En mode Fully Private, l'agrégat utilise l'adresse MAC de l'interface **privée principale**. Le champ `address` doit être défini avec votre IP privée vRack.
+>> >
+
+### Application de la configuration
+
+Appliquez la configuration en redémarrant le service réseau :
```bash
systemctl restart networking
```
-Ce redémarrage peut prendre quelques secondes puisqu’il permet de mettre en place l’interface d’agrégation. Pour vérifier que cette agrégation fonctionne, effectuez un ping vers un autre serveur sur le même vRack. Si cela fonctionne, vous avez configuré la connexion correctement. Si ce n’est pas le cas, vérifiez vos configurations ou essayez de redémarrer le serveur.
+Ce redémarrage peut prendre plusieurs secondes car il met en place l'interface d'agrégation. Pour vérifier que l'agrégat fonctionne, pingez un autre serveur sur le même vRack. Si cela fonctionne, la configuration est correcte. Si ce n'est pas le cas, vérifiez vos configurations ou essayez de redémarrer le serveur.
## Aller plus loin
-[Configurer l’agrégation de liens OLA dans votre espace client](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurer l'agrégation de liens OLA dans l'espace client OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 12 ou Ubuntu 24.04 avec Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
+Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.fr-fr.md
index d72b0c7319c..cde038c0578 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.fr-fr.md
@@ -1,14 +1,35 @@
---
-title: 'Comment configurer votre NIC pour la fonctionnalité OVHcloud Link Aggregation sur Debian 9 à 11'
-excerpt: 'Activer OVHcloud Link Aggregation sur votre Debian (versions 9 à 11)'
-updated: 2026-01-09
+title: "Comment configurer votre NIC pour la fonctionnalité OVHcloud Link Aggregation sur Debian 9 à 11"
+excerpt: "Activer l'agrégation de liens OVHcloud Link Aggregation sur votre serveur Debian (de Debian 9 à Debian 11, avec ifupdown) pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau"
+updated: 2026-04-20
---
+
+
## Objectif
-La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible.
+La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible. La bande passante disponible est également doublée grâce à l'agrégation.
+L'agrégation repose sur la technologie IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Ce guide explique comment configurer vos interfaces en agrégation pour les utiliser avec OLA sous Debian 9 à 11 (configuration ifupdown).**
-**Découvrez comment regrouper vos NIC (Network Interface Controller) pour les utiliser avec le service OLA sur Debian (versions de 9 à 11).**
+> [!warning]
+> Ce guide fournit des instructions pour configurer l'agrégation d'interfaces réseau spécifiquement avec `ifupdown`, dont le fichier de configuration se trouve à l'emplacement `/etc/network/interfaces`. Il est aussi applicable au mode rescue.
+>
+> Si la configuration réseau de votre système utilise plutôt `Netplan` (Debian 12 ou plus récent, Ubuntu 24.04), veuillez vous référer à [ce guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Prérequis
@@ -25,88 +46,242 @@ La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour
---
+## En pratique
+
+> [!primary]
+> Les valeurs (adresses MAC, adresses IP, etc.) indiquées dans les configurations et exemples ci-dessous sont fournies à titre d'exemple. Vous devez bien sûr les remplacer par vos propres valeurs.
+>
+
> [!warning]
>
-> Vous devez télécharger le paquet ifenslave sur votre serveur avant d’activer la fonctionnalité OLA sur l’API ou l’espace client OVHcloud. Pour ce faire, utilisez la commande suivante :
+> Vous devez installer le paquet ifenslave sur le serveur avant d'activer OLA dans l'espace client OVHcloud ou via l'API. Pour ce faire, utilisez la commande suivante :
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Récupération des adresses MAC
+
+Connectez-vous à l'[espace client OVHcloud](/links/manager), accédez à la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur dans **Serveurs dédiés**.
+
+Rendez-vous dans l'onglet `Interfaces réseau`{.action} et notez les adresses MAC de chaque interface (publique/privée) qui sont affichées en bas du menu.
+
+{.thumbnail}
+
> [!primary]
+> Veuillez noter que l'adresse MAC de l'interface **publique principale** est celle qui reçoit les offres DHCP, aussi bien dans le système d'exploitation du serveur qu'en mode rescue. Cette interface gère la connectivité publique dans la configuration par défaut.
>
-> Ce guide fournit des instructions pour configurer l'agrégation d'interfaces réseau spécifiquement avec `ifupdown`, dont le fichier de configuration est `/etc/network/interfaces`. Il est aussi applicable au mode rescue.
+> Quant à l'adresse MAC de l'interface **privée principale**, il s'agit de celle dont la valeur est la plus faible. Dans l'image exemple ci-dessus, il s'agit de l'adresse `a1:b2:c3:d4:e5:d6`.
>
> Si la configuration réseau de votre système utilise plutôt `Netplan`, veuillez vous référer à [ce guide](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
>
-## En pratique
-
Étant donné que nous avons une configuration privée-privée pour nos NIC sur OLA, il est impossible de se connecter en SSH au serveur. Par conséquent, vous devrez utiliser l’outil IPMI pour accéder au serveur.
-Cliquez ensuite sur l'onglet `IPMI`{.action} (1) puis sur le bouton `Depuis un applet Java (KVM)`{.action} (2).
+Maintenant que vous savez quelles adresses MAC sont associées à chaque type (public/privé) d'interface, vous devez récupérer les noms des interfaces.
-{.thumbnail}
-
-Un logiciel JNLP sera téléchargé. Lancez le logiciel pour accéder à l’IPMI. Connectez-vous en utilisant les informations d’identification associées au serveur.
-
-Par défaut, en utilisant un modèle d’OVHcloud, les NIC seront nommés soit *ethX*, soit *enoX*. Si vous n’utilisez pas un modèle OVHcloud, vous pouvez retrouver les noms de vos interfaces en utilisant la commande suivante :
-
-```bash
-ip a
-```
+### Récupération des noms d'interfaces
> [!primary]
>
-> Cette commande retournera plusieurs « interfaces ». Si vous avez du mal à identifier vos NIC physiques, la première interface aura toujours l’adresse IP publique du serveur assignée par défaut.
+> Si vous perdez la connexion réseau à votre serveur, suivez les étapes intitulées « **Ouvrir un KVM** » de [ce guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Une fois les noms de vos deux NIC identifiés, il faut à présent créer le NIC bonding ou agrégation de lien sur le système d’exploitation. Pour ce faire, créez le fichier d’interfaces sur l'éditeur de texte de votre choix à l’aide de la commande suivante :
-
-```bash
-vi /etc/network/interfaces
-```
-
-Ceci ouvrira un fichier texte vide. Pour configurer l’interface d’agrégation, insérez les lignes suivantes au bout du fichier texte :
+Pour récupérer les noms des interfaces, lancez la commande suivante :
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> Pour le paramètre `hwaddress`, nous recommandons d'utiliser la plus petite des deux adresses MAC de vos NIC, car il elle appartient à l'interface de secours (fallback) LACP.
+> Cette commande va afficher de nombreuses interfaces. Si vous avez du mal à déterminer lesquelles sont vos interfaces physiques, l'adresse IP publique du serveur reste attachée par défaut à la première interface.
>
-> [!primary]
->
-> Il vous suffit d’ajouter la dernière ligne à ce fichier si vous envisagez de configurer un réseau privé via IPv6.
->
+Voici un exemple de sortie :
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Pour finir, il faudra redémarrer le service réseau à l’aide de la commande suivante :
+Une fois que vous avez déterminé les noms de vos interfaces, vous pouvez configurer l'agrégation d'interfaces dans le système d'exploitation.
+
+### Configuration de l'agrégation d'interfaces
+
+Sélectionnez l'onglet ci-dessous correspondant à la configuration de votre serveur :
+
+- **Deux interfaces** : serveurs Advance avec deux cartes réseau physiques.
+- **Quatre interfaces - Double LAG** : serveurs Scale et High Grade avec OLA en mode **Active - Double LAG** (agrégats public + privé). Cela nécessite l'[activation d'OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) dans l'espace client OVHcloud.
+- **Quatre interfaces - Fully Private** : serveurs Scale et High Grade avec OLA en mode **Active - Fully Private** (agrégat privé unique pour le vRack). Cela nécessite l'[activation d'OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) dans l'espace client OVHcloud.
+
+> [!tabs]
+> Deux interfaces
+>> Remplacez le contenu de `/etc/network/interfaces` par ce qui suit :
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Adresse MAC de l'interface publique principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Adresse MAC de l'interface publique principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Quatre interfaces - Double LAG
+>> Cette configuration lie les interfaces publiques dans `bond0` (avec l'IP publique) et les interfaces privées dans `bond1` (pour le vRack).
+>>
+>> Remplacez le contenu de `/etc/network/interfaces` par ce qui suit :
+>>
+>> **IP fixe**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Adresse MAC de l'interface publique principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optionnel : configuration de l'agrégat privé
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Adresse MAC de l'interface privée principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Adresse MAC de l'interface publique principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Optionnel : configuration de l'agrégat privé
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Adresse MAC de l'interface privée principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Quatre interfaces - Fully Private
+>> Cette configuration agrège toutes les interfaces physiques en un seul agrégat pour une utilisation vRack uniquement. Il n'y a pas de connectivité IP publique.
+>>
+>> > [!warning]
+>> >
+>> > Suite à la mise en œuvre d'OLA en mode Fully Private, l'IP publique n'est plus accessible. Assurez-vous de disposer d'un moyen d'accès alternatif (par exemple via un autre serveur dans le vRack, ou via KVM/IPMI) avant d'appliquer cette configuration.
+>> >
+>>
+>> Remplacez le contenu de `/etc/network/interfaces` par ce qui suit :
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # Adresse MAC de l'interface privée principale du serveur
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > En mode Fully Private, l'agrégat utilise l'adresse MAC de l'interface **privée principale**. Le champ `address` doit être défini avec votre IP privée vRack.
+>> >
+
+### Application de la configuration
+
+Appliquez la configuration en redémarrant le service réseau :
```bash
systemctl restart networking
```
-Ce redémarrage peut prendre quelques secondes puisqu’il permet de mettre en place l’interface d’agrégation. Pour vérifier que cette agrégation fonctionne, effectuez un ping vers un autre serveur sur le même vRack. Si cela fonctionne, vous avez configuré la connexion correctement. Si ce n’est pas le cas, vérifiez vos configurations ou essayez de redémarrer le serveur.
+Ce redémarrage peut prendre plusieurs secondes car il met en place l'interface d'agrégation. Pour vérifier que l'agrégat fonctionne, pingez un autre serveur sur le même vRack. Si cela fonctionne, la configuration est correcte. Si ce n'est pas le cas, vérifiez vos configurations ou essayez de redémarrer le serveur.
## Aller plus loin
-[Configurer l’agrégation de liens OLA dans votre espace client](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurer l'agrégation de liens OLA dans l'espace client OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 12 ou Ubuntu 24.04 avec Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
+Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.it-it.md
index 518a9fb1881..6655b5e8062 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.it-it.md
@@ -1,18 +1,39 @@
---
-title: 'Configurare un NIC per il servizio OVHcloud Link Aggregation in Debian 9 a 11'
-excerpt: "Attivare l'opzione OVHcloud Link Aggregation sul tuo server Debian 9 a 11"
-updated: 2026-01-09
+title: "Configurare un NIC per il servizio OVHcloud Link Aggregation in Debian 9 a 11"
+excerpt: "Attiva l'aggregazione di collegamenti sul tuo server Debian (da Debian 9 a Debian 11, con ifupdown) per aumentare la disponibilità del tuo server e migliorare l'efficienza delle tue connessioni di rete"
+updated: 2026-04-20
---
+
+
## Obiettivo
-La tecnologia OVHcloud Link Aggregation (OLA) è stata progettata dai team OVHcloud per aumentare la disponibilità dei server e potenziare le connessioni di rete. L’attivazione dell’opzione permette di aggregare in pochi click le schede di rete e rendere i collegamenti ridondati in modo che, in caso di malfunzionamenti, il traffico venga reindirizzato automaticamente verso il collegamento disponibile.
+La tecnologia OVHcloud Link Aggregation (OLA) è stata progettata dai team OVHcloud per aumentare la disponibilità dei server e potenziare le connessioni di rete. L'attivazione dell'opzione permette di aggregare in pochi click le schede di rete e rendere i collegamenti ridondati in modo che, in caso di malfunzionamenti, il traffico venga reindirizzato automaticamente verso il collegamento disponibile. La larghezza di banda disponibile viene anche raddoppiata grazie all'aggregazione.
+L'aggregazione si basa sulla tecnologia IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Scopri come raggruppare le tue NIC (Network Interface Controller) per utilizzarle con il servizio OLA su Debian (versioni da 9 a 11).**
+**Questa guida spiega come configurare le interfacce in aggregazione per utilizzarle con OLA in Debian 9 a 11 (configurazione ifupdown).**
+
+> [!warning]
+> Questa guida fornisce istruzioni per configurare l'aggregazione delle interfacce di rete specificamente con `ifupdown`, il cui file di configurazione è `/etc/network/interfaces`. È applicabile anche alla modalità di ripristino.
+>
+> Se la configurazione di rete del tuo sistema utilizza invece `Netplan` (Debian 12 o versioni successive, Ubuntu 24.04), fai riferimento a [questa guida](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Prerequisiti
-- [Configurare un NIC per il servizio OVHcloud Link Aggregation nello Spazio Cliente](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Configurare OVHcloud Link Aggregation nello Spazio Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -25,89 +46,241 @@ La tecnologia OVHcloud Link Aggregation (OLA) è stata progettata dai team OVHcl
---
+## Procedura
+
+> [!primary]
+> I valori (indirizzi MAC, indirizzi IP, ecc.) indicati nelle configurazioni e negli esempi seguenti sono forniti a titolo di esempio. Naturalmente è necessario sostituirli con i propri valori.
+>
+
> [!warning]
>
-> Prima di attivare OVHcloud Link Aggregation nello Spazio Cliente o nell’API, è necessario scaricare il pacchetto ifenslave tramite questo comando:
+> Prima di attivare OLA nello Spazio Cliente o nell'API, è necessario installare il pacchetto ifenslave sul server tramite questo comando:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
-> [!primary]
->
-> Questa guida fornisce istruzioni per configurare l'aggregazione delle interfacce di rete specificamente con `ifupdown`, il cui file di configurazione è `/etc/network/interfaces`. È applicabile anche alla modalità di ripristino.
->
-> Se la configurazione di rete del tuo sistema utilizza invece `Netplan`, fai riferimento a [questa guida](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
->
+### Recupero degli indirizzi MAC
-## Procedura
+Accedi allo [Spazio Cliente OVHcloud](/links/manager), vai nella sezione `Bare Metal Cloud`{.action} e seleziona il tuo server tra i **Server dedicati**.
-Il tipo di configurazione disponibile in OLA per i nostri NIC non permette di accedere al server in SSH. Per stabilire la connessione alla macchina è quindi necessario utilizzare IPMI.
-
Per attivare il tool accedi allo [Spazio Cliente OVHcloud](/links/manager). Nella sezione `Bare Metal Cloud`{.action}, seleziona il tuo server tra `Server dedicati`{.action} e clicca sulla scheda `IPMI`{.action} (1).
+Vai alla scheda `Interfacce di rete`{.action} e prendi nota degli indirizzi MAC di ciascuna interfaccia (pubblica/privata) visualizzati in fondo al menu.
-Clicca sul pulsante `Da una applet Java (KVM)`{.action} (2).
+{.thumbnail}
-{.thumbnail}
+> [!primary]
+> L'indirizzo MAC dell'interfaccia **pubblica principale** è quello che riceve le offerte DHCP, sia nel sistema operativo del server che in modalità rescue. Questa interfaccia gestisce la connettività pubblica nella configurazione predefinita.
+>
+> Inoltre, l'indirizzo MAC dell'interfaccia **privata principale** è quello con il valore più basso. Nell'immagine di esempio sopra, si tratta dell'indirizzo `a1:b2:c3:d4:e5:d6`.
+>
-Verrà scaricato un programma JNLP: aprilo e utilizza le credenziali associate al server per accedere.
+Poiché la configurazione dei NIC in OLA è di tipo privato-privato, non sarà possibile accedere al server in SSH. Sarà quindi necessario utilizzare lo strumento IPMI per accedere al server.
+
Clicca sulla scheda `IPMI`{.action} (1).
-Se utilizzi un template OVHcloud, il nome delle schede di rete assegnato di default sarà **ethX** o **enoX**. In caso contrario è possibile trovare i nomi delle interfacce eseguendo questo comando:
+Clicca sul pulsante `Da una applet Java (KVM)`{.action} (2).
-```bash
-ip a
-```
+### Recupero dei nomi delle interfacce
> [!primary]
>
-> Il risultato restituito mostrerà diverse "interfacce". In caso di difficoltà nel determinare i propri NIC fisici, è utile considerare che gli indirizzi IP pubblici del server sono associati di default alla prima interfaccia.
+> Se perdi la connessione di rete al server, segui i passaggi "**Apri KVM**" di [questa guida](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Una volta individuati i nomi dei due NIC sarà possibile configurarne il bonding nel sistema operativo. Per creare il file **interfaces** in un editor di testo, utilizza questo comando:
-
-```bash
-vi /etc/network/interfaces
-```
-
-Si aprirà un file di testo vuoto. Per configurare l’interfaccia bond, inserisci queste righe:
+Per recuperare i nomi delle interfacce, esegui il seguente comando:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> Per il parametro `hwaddress`, si consiglia di utilizzare il più piccolo dei due indirizzi MAC delle schede di rete, poiché appartiene all'interfaccia di riserva (fallback) LACP.
+> Questo comando mostrerà numerose interfacce. In caso di difficoltà nel determinare quali siano le interfacce fisiche, l'indirizzo IP pubblico del server è ancora associato di default alla prima interfaccia.
>
-> [!primary]
->
-> Per configurare una rete privata via IPv6 è sufficiente aggiungere al file solo l’ultima riga.
->
+Ecco un esempio di output:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-A questo punto riavvia il servizio di rete con il comando:
+Una volta determinati i nomi delle interfacce, è possibile configurare l'aggregazione nel sistema operativo.
+
+### Configurazione dell'aggregazione delle interfacce
+
+Seleziona la scheda seguente corrispondente alla configurazione del tuo server:
+
+- **Due interfacce**: server Advance con due NIC fisiche.
+- **Quattro interfacce - Double LAG**: server Scale e High-Grade con OLA in modalità **Active - Double LAG** (aggregati pubblico + privato). Richiede l'[attivazione di OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) nello Spazio Cliente OVHcloud.
+- **Quattro interfacce - Fully Private**: server Scale e High-Grade con OLA in modalità **Active - Fully Private** (unico aggregato privato per vRack). Richiede l'[attivazione di OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) nello Spazio Cliente OVHcloud.
+
+> [!tabs]
+> Due interfacce
+>> Sostituisci il contenuto di `/etc/network/interfaces` con quanto segue:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Indirizzo MAC dell'interfaccia pubblica principale del server
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Indirizzo MAC dell'interfaccia pubblica principale del server
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Quattro interfacce - Double LAG
+>> Questa configurazione raggruppa le interfacce pubbliche in `bond0` (con IP pubblico) e le interfacce private in `bond1` (per vRack).
+>>
+>> Sostituisci il contenuto di `/etc/network/interfaces` con quanto segue:
+>>
+>> **IP statico**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Indirizzo MAC dell'interfaccia pubblica principale del server
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opzionale: configurazione dell'aggregato privato
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Indirizzo MAC dell'interfaccia privata principale del server
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Indirizzo MAC dell'interfaccia pubblica principale del server
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opzionale: configurazione dell'aggregato privato
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Indirizzo MAC dell'interfaccia privata principale del server
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Quattro interfacce - Fully Private
+>> Questa configurazione aggrega tutte le interfacce fisiche in un unico aggregato esclusivamente per l'utilizzo con vRack. Non è prevista connettività IP pubblica.
+>>
+>> > [!warning]
+>> >
+>> > In seguito all'implementazione di OLA in modalità Fully Private, l'IP pubblico non è più accessibile. Assicurati di disporre di un mezzo di accesso alternativo (ad esempio tramite un altro server nel vRack o via KVM/IPMI) prima di applicare questa configurazione.
+>> >
+>>
+>> Sostituisci il contenuto di `/etc/network/interfaces` con quanto segue:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # Indirizzo MAC dell'interfaccia privata principale del server
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In modalità Fully Private, l'aggregato utilizza l'indirizzo MAC dell'interfaccia **privata principale**. Il campo `address` deve essere impostato sul tuo indirizzo IP privato vRack.
+>> >
+
+### Applicazione della configurazione
+
+Applica la configurazione riavviando il servizio di rete:
```bash
systemctl restart networking
```
-Questa operazione potrebbe richiedere alcuni secondi per costruire l’interfaccia bond. Per testare il corretto funzionamento della nuova interfaccia creata, effettua il ping di un altro server presente nella stessa vRack. Se funziona, la procedura è conclusa. In caso contrario, verifica nuovamente la configurazione o prova a riavviare il server.
+Questa operazione potrebbe richiedere alcuni secondi per costruire l'interfaccia di aggregazione. Per verificare che l'aggregato funzioni correttamente, effettua il ping di un altro server nella stessa vRack. Se funziona, la procedura è conclusa. In caso contrario, verifica nuovamente le configurazioni o prova a riavviare il server.
## Per saperne di più
-[Configurare un NIC per il servizio OVHcloud Link Aggregation nello Spazio Cliente](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurare OVHcloud Link Aggregation nello Spazio Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Come configurare la NIC per OVHcloud Link Aggregation in Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Configurare un NIC per il servizio OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Configurare un NIC per il servizio OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[Configurare un NIC per il servizio OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[Configurare un NIC per il servizio OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Contatta la nostra [Community di utenti](/links/community).
\ No newline at end of file
+Contatta la nostra [Community di utenti](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.pl-pl.md
index 186e5830e94..3fe1283e80c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.pl-pl.md
@@ -1,18 +1,39 @@
---
-title: 'Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debian 9-11'
-excerpt: 'Dowiedz się, jak włączyć OVHcloud Link Aggregation na serwerze Debian 9-11'
-updated: 2026-01-09
+title: "Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 9–11"
+excerpt: "Aktywuj agregację łączy na serwerze Debian (od Debian 9 do Debian 11, przy użyciu ifupdown), aby zwiększyć dostępność serwera i wydajność połączeń sieciowych"
+updated: 2026-04-20
---
+
+
## Wprowadzenie
-Technologia OVHcloud Link Aggregation (OLA) została przez nas zaprojektowana w celu zwiększenia dostępności serwera oraz podniesienia wydajności połączeń sieciowych. Możesz w prosty sposób przeprowadzić agregację kart sieciowych, dzięki czemu Twoje połączenia sieciowe staną się redundantne. Jeśli jedno połączenie zostanie zerwane, ruch zostanie automatycznie przekierowany do innego dostępnego łącza.
+Technologia OVHcloud Link Aggregation (OLA) została zaprojektowana przez nasze zespoły w celu zwiększenia dostępności serwera oraz podniesienia wydajności połączeń sieciowych. Za pomocą kilku kliknięć możesz połączyć karty sieciowe i sprawić, że Twoje połączenia sieciowe staną się redundantne. Oznacza to, że jeśli jedno połączenie zostanie zerwane, ruch zostanie automatycznie przekierowany do innego dostępnego łącza. Dostępna przepustowość jest również podwajana dzięki agregacji.
+Agregacja oparta jest na technologii IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Dowiedz się, jak połączyć swoje karty sieciowe (NIC) w celu korzystania z usługi OLA w systemie Debian (wersje od 9 do 11).**
+**Niniejszy przewodnik wyjaśnia, jak skonfigurować agregację interfejsów do użycia z OLA w Debianie 9–11 (konfiguracja ifupdown).**
+
+> [!warning]
+> Niniejszy przewodnik zawiera instrukcje dotyczące konfiguracji agregacji interfejsów sieciowych przy użyciu programu `ifupdown`, którego plik konfiguracyjny znajduje się w katalogu `/etc/network/interfaces`. Ma on również zastosowanie w trybie ratunkowym.
+>
+> Jeśli konfiguracja sieciowa systemu wykorzystuje `Netplan` (Debian 12 lub nowszy, Ubuntu 24.04), zapoznaj się z [tym przewodnikiem](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Wymagania początkowe
-- [Konfiguracja karty sieciowej dla OVHcloud Link Aggregation w Panelu klienta](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Konfiguracja OVHcloud Link Aggregation w Panelu klienta OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -25,93 +46,241 @@ Technologia OVHcloud Link Aggregation (OLA) została przez nas zaprojektowana w
---
+## W praktyce
+
+> [!primary]
+> Wartości (adresy MAC, adresy IP itp.) podane w poniższych konfiguracjach i przykładach służą wyłącznie jako przykłady. Należy oczywiście zastąpić je własnymi wartościami.
+>
+
> [!warning]
>
-> Zanim włączysz OLA w Panelu klienta lub za pośrednictwem API, pobierz na serwer pakiet ifenslave. W tym celu zastosuj następujące polecenie:
+> Przed włączeniem OLA w Panelu klienta lub za pośrednictwem API należy zainstalować pakiet ifenslave na serwerze. W tym celu użyj następującego polecenia:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
-> [!primary]
->
-> Niniejszy przewodnik zawiera instrukcje dotyczące konfiguracji agregacji interfejsów sieciowych przy użyciu programu `ifupdown`, którego plik konfiguracyjny znajduje się w katalogu `/etc/network/interfaces`. Ma on również zastosowanie w trybie ratunkowym.
->
-> Jeśli konfiguracja sieciowa systemu wykorzystuje raczej `Netplan`, zapoznaj się z [tym przewodnikiem](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
->
+### Pobieranie adresów MAC
-## W praktyce
+Zaloguj się do [Panelu klienta OVHcloud](/links/manager), przejdź do sekcji `Bare Metal Cloud`{.action} i wybierz serwer z listy **Serwery dedykowane**.
-Ponieważ konfiguracja kart sieciowych w OLA jest prywatna, nie będziesz mógł połączyć się z serwerem za pomocą SSH. W związku z tym do uzyskania dostępu do serwera użyj narzędzia IPMI.
-
Zaloguj się do [Panelu klienta OVHcloud](/links/manager). W części `Bare Metal Cloud`{.action} wybierz serwer z `Serwery dedykowane`{.action} i kliknij zakładkę `IPMI`{.action} (1).
+Przejdź do zakładki `Interfejsy sieciowe`{.action} i zanotuj adresy MAC dla każdego interfejsu (publicznego/prywatnego), które są wyświetlane na dole menu.
-Teraz kliknij przycisk `Z apletu Java (KVM)`{.action} (2).
+{.thumbnail}
-{.thumbnail}
+> [!primary]
+> Należy pamiętać, że adres MAC interfejsu **głównego publicznego** jest tym, który odbiera oferty DHCP, zarówno w systemie operacyjnym serwera, jak i w trybie ratunkowym. Ten interfejs obsługuje łączność publiczną w domyślnej konfiguracji.
+>
+> Ponadto adres MAC interfejsu **głównego prywatnego** to ten o najniższej wartości. Na powyższym przykładowym obrazku jest to adres `a1:b2:c3:d4:e5:d6`.
+>
-Zostanie pobrany program JNLP. Otwórz program, aby skorzystać z połączenia IPMI. Zaloguj się, używając aktualnych danych do logowania do serwera.
+Ponieważ konfiguracja kart sieciowych w OLA jest prywatna, nie będziesz mógł połączyć się z serwerem za pomocą SSH. W związku z tym do uzyskania dostępu do serwera użyj narzędzia IPMI.
+
Kliknij zakładkę `IPMI`{.action} (1).
-Po zastosowaniu szablonu systemu operacyjnego dostarczanego przez OVHcloud interfejsy sieciowe będą miały domyślnie nazwy *ethX* lub *enoX*. Jeśli nie używasz szablonu OVHcloud, odszukaj nazwy Twoich interfejsów, używając następującego polecenia:
+Następnie kliknij przycisk `Z apletu Java (KVM)`{.action} (2).
-```bash
-ip a
-```
+### Pobieranie nazw interfejsów
> [!primary]
>
-> Wprowadzenie tego polecenie spowoduje wywołanie wielu “interfejsów”. Jeśli masz problem z ustaleniem, które z nich są Twoimi fizycznymi interfejsami sieciowymi, do pierwszego interfejsu nadal będzie domyślnie przypisany publiczny adres IP serwera.
+> Jeśli utracisz połączenie sieciowe z serwerem, wykonaj kroki opisane w sekcji "**Otwórz KVM**" z [tego przewodnika](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Kiedy ustalisz nazwy dwóch interfejsów, powiąż je w systemie operacyjnym. Utwórz plik interfejsu w dowolnym edytorze tekstowym za pomocą następującego polecenia:
-
-```bash
-vi /etc/network/interfaces
-```
-
-Spowoduje to otwarcie pustego pliku tekstowego. Aby skonfigurować powiązanie, w dolnej części pliku tekstowego umieść poniższe elementy:
+Aby pobrać nazwy interfejsów, wykonaj następujące polecenie:
```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> W przypadku parametru `hwaddress` zalecamy użycie mniejszego z dwóch adresów MAC kart sieciowych, ponieważ należy on do interfejsu rezerwowego (fallback) LACP.
+> To polecenie wyświetli wiele interfejsów. Jeśli masz trudności z określeniem, które z nich są Twoimi interfejsami fizycznymi, pierwszemu interfejsowi domyślnie przypisany jest publiczny adres IP serwera.
>
-> [!primary]
->
-> Dodaj ostatnią linię do tego pliku, jeśli zamierzasz skonfigurować sieć prywatną za pośrednictwem IPv6.
->
+Oto przykład wyniku:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Na koniec zrestartuj demona sieciowego za pomocą następującego polecenia:
+Po ustaleniu nazw interfejsów możesz skonfigurować agregację interfejsów w systemie operacyjnym.
+
+### Konfiguracja agregacji interfejsów
+
+Wybierz poniższą zakładkę odpowiadającą konfiguracji serwera:
+
+- **Dwa interfejsy**: serwery Advance z dwoma fizycznymi kartami NIC.
+- **Cztery interfejsy - Double LAG**: serwery Scale i High-Grade z OLA w trybie **Active - Double LAG** (agregaty publiczny + prywatny). Wymaga [włączenia OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) w Panelu klienta OVHcloud.
+- **Cztery interfejsy - Fully Private**: serwery Scale i High-Grade z OLA w trybie **Active - Fully Private** (jeden prywatny agregat dla vRack). Wymaga [włączenia OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) w Panelu klienta OVHcloud.
+
+> [!tabs]
+> Dwa interfejsy
+>> Zastąp zawartość pliku `/etc/network/interfaces` następującymi danymi:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Adres MAC głównego publicznego interfejsu serwera
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Adres MAC głównego publicznego interfejsu serwera
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Cztery interfejsy - Double LAG
+>> Ta konfiguracja łączy publiczne interfejsy w `bond0` (z publicznym IP) i prywatne interfejsy w `bond1` (dla vRack).
+>>
+>> Zastąp zawartość pliku `/etc/network/interfaces` następującymi danymi:
+>>
+>> **Statyczny IP**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Adres MAC głównego publicznego interfejsu serwera
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opcjonalnie: konfiguracja prywatnego agregatu
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Adres MAC głównego prywatnego interfejsu serwera
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Adres MAC głównego publicznego interfejsu serwera
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opcjonalnie: konfiguracja prywatnego agregatu
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Adres MAC głównego prywatnego interfejsu serwera
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Cztery interfejsy - Fully Private
+>> Ta konfiguracja agreguje wszystkie fizyczne interfejsy w jednym agregacie wyłącznie do użytku z vRack. Brak publicznej łączności IP.
+>>
+>> > [!warning]
+>> >
+>> > Po wdrożeniu OLA w trybie Fully Private publiczny adres IP nie jest już dostępny. Upewnij się, że masz alternatywny sposób dostępu (np. przez inny serwer w vRack lub przez KVM/IPMI) przed zastosowaniem tej konfiguracji.
+>> >
+>>
+>> Zastąp zawartość pliku `/etc/network/interfaces` następującymi danymi:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # Adres MAC głównego prywatnego interfejsu serwera
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > W trybie Fully Private agregat używa adresu MAC interfejsu **głównego prywatnego**. Pole `address` powinno być ustawione na Twój prywatny adres IP vRack.
+>> >
+
+### Zastosowanie konfiguracji
+
+Zastosuj konfigurację, restartując usługę sieciową:
```bash
-restart sieci systemctl
+systemctl restart networking
```
-Restart może trwać kilka sekund, w tym czasie budowany jest interfejs powiązania.Aby sprawdzić, czy powiązanie działa, podłącz inny serwer do tego samego vRacka. Jeśli wszystko działa poprawnie, ustawienie jest prawidłowe. W przeciwnym razie sprawdź dokładnie Twoje konfiguracje lub spróbuj zrestartować serwer.
-
-## Podsumowanie
-
-OVHcloud zapewnia klientom swobodę i elastyczność wykorzystania sprzętu w sposób najlepiej odpowiadający ich potrzebom. Po przeczytaniu tego przewodnika będziesz potrafił skonfigurować OVHcloud Link Aggregation (OLA) w Debianie 9 w celu wykorzystania obu interfejsów sieciowych jako powiązanych interfejsów prywatnych.
+Restart może trwać kilka sekund, ponieważ tworzony jest interfejs agregatu. Aby sprawdzić, czy agregat działa prawidłowo, wyślij polecenie ping do innego serwera w tym samym vRack. Jeśli działa, wszystko jest gotowe. Jeśli nie, sprawdź konfiguracje lub spróbuj zrestartować serwer.
## Sprawdź również
-[Konfiguracja OVHcloud Link Aggregation w Panelu klienta](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[Konfiguracja OVHcloud Link Aggregation w Panelu klienta OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 12 lub Ubuntu 24.04 z Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Dołącz do [grona naszych użytkowników](/links/community).
\ No newline at end of file
+Dołącz do [grona naszych użytkowników](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.pt-pt.md
index 8beb053f271..f30b71ea054 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.pt-pt.md
@@ -1,18 +1,39 @@
---
-title: 'Como configurar a NIC para o OVHcloud Link Aggregation em Debian 9 a 11'
-excerpt: 'Ative o OVHcloud Link Aggregation no seu servidor Debian 9 a 11'
-updated: 2026-01-09
+title: "Como configurar a NIC para o OVHcloud Link Aggregation em Debian 9 a 11"
+excerpt: "Ative a agregação de ligações no seu servidor Debian (de Debian 9 a Debian 11, com ifupdown) para aumentar a disponibilidade do seu servidor e melhorar a eficiência das suas ligações de rede"
+updated: 2026-04-20
---
-## Sumário
+
-A tecnologia OVHcloud Link Aggregation (OLA) foi criada pelas nossas equipas para aumentar a disponibilidade do seu servidor e aumentar a eficiência das suas ligações de rede. Em apenas alguns cliques, pode agregar as suas placas de rede e tornar as suas ligações de rede redundantes. Isto significa que se uma ligação for interrompida, o tráfego é automaticamente redirecionado para outra ligação disponível.
+## Objetivo
-**Descubra como agrupar as suas NIC (Network Interface Controller) para utilizá-las com o serviço OLA no Debian (versões 9 a 11).**
+A tecnologia OVHcloud Link Aggregation (OLA) foi criada pelas nossas equipas para aumentar a disponibilidade do seu servidor e aumentar a eficiência das suas ligações de rede. Em apenas alguns cliques, pode agregar as suas placas de rede e tornar as suas ligações de rede redundantes. Isto significa que se uma ligação for interrompida, o tráfego é automaticamente redirecionado para outra ligação disponível. A largura de banda disponível é também duplicada graças à agregação.
+A agregação baseia-se na tecnologia IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Este guia explica como configurar as suas interfaces em agregação para as utilizar com OLA em Debian 9 a 11 (configuração ifupdown).**
+
+> [!warning]
+> Este guia fornece instruções para configurar a agregação de interfaces de rede especificamente com `ifupdown`, cujo ficheiro de configuração é `/etc/network/interfaces`. Também é aplicável ao modo de recuperação.
+>
+> Se a configuração de rede do seu sistema utiliza `Netplan` (Debian 12 ou mais recente, Ubuntu 24.04), consulte [este guia](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+>
## Requisitos
-- [Como configurar a NIC para o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Configurar o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -25,89 +46,241 @@ A tecnologia OVHcloud Link Aggregation (OLA) foi criada pelas nossas equipas par
---
+## Instruções
+
+> [!primary]
+> Os valores (endereços MAC, endereços IP, etc.) indicados nas configurações e exemplos abaixo são fornecidos a título de exemplo. Naturalmente, deve substituí-los pelos seus próprios valores.
+>
+
> [!warning]
>
-> Será necessário descarregar o pacote ifenslave no servidor antes de ativar o OLA na Área de Cliente ou API da OVHcloud. Para isso, utilize o seguinte comando:
+> Será necessário instalar o pacote ifenslave no servidor antes de ativar o OLA na Área de Cliente ou API da OVHcloud. Para isso, utilize o seguinte comando:
>
-> ```
+> ```bash
> apt install ifenslave
> ```
>
+### Obtenção dos endereços MAC
+
+Aceda à [Área de Cliente OVHcloud](/links/manager), vá à secção `Bare Metal Cloud`{.action} e selecione o seu servidor em **Servidores dedicados**.
+
+Vá ao separador `Interfaces de rede`{.action} e tome nota dos endereços MAC de cada interface (pública/privada) que são apresentados na parte inferior do menu.
+
+{.thumbnail}
+
> [!primary]
+> O endereço MAC da interface **pública principal** é o que recebe as ofertas DHCP, tanto no sistema operativo do servidor como no modo de recuperação. Esta interface gere a conectividade pública na configuração predefinida.
>
-> Este guia fornece instruções para configurar a agregação de interfaces de rede especificamente com `ifupdown`, cujo ficheiro de configuração é `/etc/network/interfaces`. Ele também é aplicável ao modo de recuperação.
+> Além disso, o endereço MAC da interface **privada principal** é o de valor mais baixo. Na imagem de exemplo acima, este é o endereço `a1:b2:c3:d4:e5:d6`.
>
-> Se a configuração de rede do seu sistema usa `Netplan`, consulte [este guia](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
->
-
-## Instruções
A configuração private-private disponível no OLA para as nossas NIC não permite aceder ao servidor em SSH. Para aceder ao servidor, é necessário utilizar a ferramenta IPMI.
-
Para o fazer, aceda à [Área de Cliente OVHcloud](/links/manager). Na secção `Bare Metal Cloud`{.action}, selecione o seu servidor em `Servidores dedicados`{.action} e clique no separador `IPMI`{.action} (1).
+
Clique no separador `IPMI`{.action} (1).
Em seguida, clique no botão `A partir de applet java (KVM)`{.action} (2).
-{.thumbnail}
-
-Um programa JNLP será descarregado. Abra o programa para entrar no IPMI. Inicie a sua sessão usando credenciais válidas para o servidor.
-
-Por predefinição, com um modelo OVHcloud, as NIC são designadas *ethX* e *enoX*. Se não estiver a utilizar um modelo OVHcloud, pode encontrar os nomes das suas interfaces através do seguinte comando:
-
-```bash
-ip a
-```
+### Obtenção dos nomes das interfaces
> [!primary]
>
-> Este comando irá produzir várias "interfaces". Se tiver dificuldade em determinar quais são as suas NIC físicas, a primeira interface ainda terá o endereço IP público do servidor anexado por predefinição.
+> Se perder a ligação de rede ao servidor, siga os passos "**Abrir KVM**" de [este guia](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Assim que tivermos determinado os nomes das nossas duas NIC, configuraremos a ligação entre as NIC no sistema operativo. Crie o ficheiro de interfaces num editor de texto à sua escolha através do seguinte comando:
+Para obter os nomes das interfaces, execute o seguinte comando:
```bash
-vi /etc/network/interfaces
-```
-
-Um ficheiro de texto vazio aparecerá. Para configurar a interface de ligação, introduza o seguinte na parte inferior do ficheiro de texto:
-
-```bash
-auto bond0
-iface bond0 inet static
- address 10.0.0.1/24
- hwaddress ether 00:11:22:33:44:55
- bond-mode 802.3ad
- bond-slaves eno1 eno2
- bond-lacp-rate fast
- bond-xmit_hash_policy layer3+4
-
- up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
+ip a
```
> [!primary]
>
-> Para o parâmetro `hwaddress`, recomendamos usar o menor dos dois endereços MAC das suas NICs, pois ele pertence à interface reserva (fallback) LACP.
+> Este comando irá produzir várias interfaces. Se tiver dificuldade em determinar quais são as suas interfaces físicas, a primeira interface ainda terá o endereço IP público do servidor associado por predefinição.
>
-> [!primary]
->
-> Para configurar uma rede privada através do IPv6, só precisará de adicionar a última linha a este ficheiro.
->
+Aqui tem um exemplo de saída:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
+```
-Finalmente, iremos reiniciar o daemon de rede usando o seguinte comando:
+Após determinar os nomes das suas interfaces, pode configurar a agregação de interfaces no sistema operativo.
+
+### Configuração da agregação de interfaces
+
+Selecione o separador seguinte que corresponde à configuração do seu servidor:
+
+- **Duas interfaces**: servidores Advance com duas NIC físicas.
+- **Quatro interfaces - Double LAG**: servidores Scale e High-Grade com OLA no modo **Active - Double LAG** (agregados público + privado). Requer a [ativação do OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) na Área de Cliente OVHcloud.
+- **Quatro interfaces - Fully Private**: servidores Scale e High-Grade com OLA no modo **Active - Fully Private** (único agregado privado para vRack). Requer a [ativação do OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) na Área de Cliente OVHcloud.
+
+> [!tabs]
+> Duas interfaces
+>> Substitua o conteúdo de `/etc/network/interfaces` pelo seguinte:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Endereço MAC da interface pública principal do servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Endereço MAC da interface pública principal do servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>> ```
+>>
+>> ///
+>>
+> Quatro interfaces - Double LAG
+>> Esta configuração agrupa as interfaces públicas em `bond0` (com IP público) e as interfaces privadas em `bond1` (para vRack).
+>>
+>> Substitua o conteúdo de `/etc/network/interfaces` pelo seguinte:
+>>
+>> **IP estático**
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 203.0.113.1/32
+>> gateway 100.64.0.1
+>> # Endereço MAC da interface pública principal do servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> dns-nameservers 213.186.33.99
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opcional: configuração do agregado privado
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Endereço MAC da interface privada principal do servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet dhcp
+>> # Endereço MAC da interface pública principal do servidor
+>> hwaddress ether a1:b2:c3:d4:e5:c6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>>
+>> up ip -6 addr add 2001:db8:1:1b00:203:0:112:0/56 dev bond0
+>> up ip -6 route add default via fe80::1 dev bond0
+>>
+>> # Opcional: configuração do agregado privado
+>> auto bond1
+>> iface bond1 inet static
+>> address 10.0.0.1/24
+>> # Endereço MAC da interface privada principal do servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> ///
+>>
+> Quatro interfaces - Fully Private
+>> Esta configuração agrega todas as interfaces físicas num único agregado exclusivamente para utilização com vRack. Não há conectividade IP pública.
+>>
+>> > [!warning]
+>> >
+>> > Após a implementação do OLA em modo Fully Private, o IP público deixa de estar acessível. Certifique-se de que dispõe de um meio alternativo de acesso (por exemplo, através de outro servidor no vRack ou via KVM/IPMI) antes de aplicar esta configuração.
+>> >
+>>
+>> Substitua o conteúdo de `/etc/network/interfaces` pelo seguinte:
+>>
+>> ```bash
+>> auto bond0
+>> iface bond0 inet static
+>> address 10.0.0.1/24
+>> # Endereço MAC da interface privada principal do servidor
+>> hwaddress ether a1:b2:c3:d4:e5:d6
+>> bond-mode 802.3ad
+>> bond-slaves ens22f0np0 ens22f1np1 ens33f0np0 ens33f1np1
+>> bond-lacp-rate fast
+>> bond-xmit_hash_policy layer3+4
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > No modo Fully Private, o agregado utiliza o endereço MAC da interface **privada principal**. O campo `address` deve ser definido com o seu endereço IP privado de vRack.
+>> >
+
+### Aplicação da configuração
+
+Aplique a configuração reiniciando o serviço de rede:
```bash
systemctl restart networking
```
-Este reinício pode levar vários segundos, uma vez que está a construir a interface de ligação. Para testar se a ligação está a funcionar, faça um teste de ping noutro servidor da mesma rede vRack. Se funcionar, está tudo pronto. Caso contrário, volte a verificar as suas configurações ou tente reiniciar o servidor.
+Este reinício pode levar vários segundos, uma vez que está a construir a interface de agregação. Para testar se o agregado está a funcionar, faça um ping noutro servidor da mesma rede vRack. Se funcionar, está tudo pronto. Caso contrário, volte a verificar as suas configurações ou tente reiniciar o servidor.
+
+## Saiba mais
-## Quer saber mais?
+[Configurar o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
-[Como configurar a NIC para o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[Como configurar a NIC para o OVHcloud Link Aggregation em Debian 12 ou Ubuntu 24.04 com Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
[Como configurar a NIC para o OVHcloud Link Aggregation em Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[Como configurar a NIC para o OVHcloud Link Aggregation em SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
+[Como configurar a NIC para o OVHcloud Link Aggregation em SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Fale com nossa [comunidade de utilizadores](/links/community).
\ No newline at end of file
+Fale com nossa [comunidade de utilizadores](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.de-de.md
index d9b87612403..9773631ecb2 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.de-de.md
@@ -1,7 +1,7 @@
---
title: 'Konfigurieren der OVHcloud Link Aggregation'
excerpt: 'Erfahren Sie hier, wie Sie OLA im OVHcloud Kundencenter aktivieren'
-updated: 2022-05-18
+updated: 2026-04-20
---
## Ziel
@@ -38,31 +38,42 @@ Die Aggregation basiert auf dem Standard IEEE 802.3ad, Link Aggregation Control
### OLA in Ihrem OVHcloud Kundencenter konfigurieren
-Klicken Sie auf `Dedicated Server`{.action} und wählen Sie Ihren Server aus der Liste aus.
+Öffnen Sie den Tab `Netzwerkinterfaces`{.action} auf der Verwaltungsseite Ihres Servers.
-{.thumbnail}
+Klicken Sie auf den Button `Netzwerk-Aggregation`{.action} im Abschnitt **Netzwerkinterface-Controller (NICs)**.
-Klicken Sie im Tab `Netzwerkinterfaces`{.action} (1) auf den Button `...`{.action} (2) rechts von "Modus" in **OLA: OVHcloud Link Aggregation**. Klicken Sie auf `Private Aggregation konfigurieren`{.action} (2).
+Es werden zwei Tabellen angezeigt:
+- Auf der linken Seite die aktuelle Konfiguration Ihrer Netzwerkinterfaces;
+- Auf der rechten Seite die simulierte Konfiguration Ihrer aggregierten Netzwerkinterfaces.
-{.thumbnail}
+Geben Sie im Feld unterhalb der Tabellen einen Namen für Ihre Link-Aggregation ein.
-Überprüfen Sie, dass Ihre beiden Interfaces oder Schnittstellengruppen ausgewählt sind, und geben Sie dem OLA Interface einen Namen. Klicken Sie auf `Bestätigen`{.action}, sobald Ihre Überprüfungen abgeschlossen sind.
+Sobald Sie überprüft haben, dass das Aggregations-Layout Ihren Netzwerkanforderungen entspricht, klicken Sie auf `Aggregation aktivieren`{.action}, um fortzufahren.
Es kann einige Minuten dauern, bis der Vorgang abgeschlossen ist. Anschließend werden im nächsten Schritt die Schnittstellen in Ihrem Betriebssystem in einem "NIC link" oder einem "NIC team" konfiguriert. In den folgenden Anleitungen finden Sie Informationen zu den beliebtesten Betriebssystemen:
-[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 9 über ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+- [Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 9 über ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+- [Konfigurieren der OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+- [How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
+### OLA-Status prüfen
-[Konfigurieren der OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
+Sie können den Status Ihrer Link-Aggregation (OLA) im Tab `Netzwerkinterfaces`{.action} überprüfen. Suchen Sie unten im Abschnitt **Bandbreite** die Zeile **OVHcloud Link Aggregation**.
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+Es gibt vier mögliche Statuskennzeichnungen:
+- **Nicht verfügbar**: OLA wird von diesem Dedicated-Server-Modell nicht unterstützt.
+- **Verfügbar**: OLA wird unterstützt, ist aber nicht konfiguriert.
+- **Aktiv - Vollständig privat**: OLA ist aktiviert; alle physischen Interfaces werden zu einem einzigen privaten Link für den vRack-Einsatz aggregiert.
+- **Aktiv - Doppeltes LAG**: OLA ist voraktiviert; die physischen Interfaces werden in zwei separate Aggregate aufgeteilt (eines öffentlich, eines privat).
-### OLA auf die Standardwerte zurücksetzen
+> [!primary]
+> **Hinweis:** Der Status **Aktiv - Doppeltes LAG** ist eine spezifische Konfiguration, die in der Regel den Scale- und High-Grade-Server-Reihen vorbehalten ist, die über vier physische Netzwerkinterfaces verfügen.
+>
-Um OLA auf die Standardwerte wiederherzustellen, klicken Sie auf `...`{.action} rechts neben "Modus" in **OLA: OVHcloud Link Aggregation**. Klicken Sie auf `Private Aggregation dekonfigurieren`{.action}. Klicken Sie im Kontextmenü auf `Bestätigen`{.action}.
+### OLA auf die Standardwerte zurücksetzen
-{.thumbnail}
+Um OLA auf die Standardwerte zurückzusetzen, klicken Sie auf den Button `Netzwerke disaggregieren`{.action} im Abschnitt **Netzwerk-Interface-Controller**. Klicken Sie im Kontextmenü auf `Bestätigen`{.action}.
Die Operation kann einige Minuten in Anspruch nehmen.
@@ -74,6 +85,6 @@ Die Operation kann einige Minuten in Anspruch nehmen.
[Konfigurieren der OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Treten Sie unserer [User Community](/links/community) bei.
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-asia.md
index 278f98c0a3e..6f236670c8c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-asia.md
@@ -1,7 +1,7 @@
---
title: 'Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel'
excerpt: 'Find out how to enable OVHcloud Link Aggregation in the OVHcloud Control Panel'
-updated: 2023-03-07
+updated: 2026-04-20
---
## Objective
@@ -38,28 +38,42 @@ Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) t
### Configuring OLA in the OVHcloud Control Panel
-Click on `Dedicated Servers`{.action} and select your server from the list.
+To start configuring OLA, open the `Network interfaces`{.action} tab on your server's management page.
-{.thumbnail}
+Click the `Network Aggregation`{.action} button in the **Network Interface Controllers (NICs)** section.
-In the tab `Network interfaces`{.action} (1), click on the `...`{.action} button (2) to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Next, click `Configure private aggregation`{.action} (2).
+You will be shown two tables:
+- On the left, the current configuration of your network interfaces;
+- On the right, the simulated configuration of your aggregated network interfaces.
-{.thumbnail}
+In the field below the tables, enter a name for your link aggregation.
-Make sure that both your interfaces, or interface groups, are selected and give the OLA a name. Click `Confirm`{.action} when your checks are complete.
+Once you have verified that the aggregation layout matches your network requirements, click `Enable Aggregation`{.action} to proceed.
This may take a few minutes. Once it is complete, the next step is to configure the interfaces in your operating system via a NIC link or NIC team. For the method to use, refer to the following guides for the most popular operating systems:
- [How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9 using ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
- [How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
- [How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-### Restoring OLA to default values
+### Checking the OLA status
+
+You can verify your Link Aggregation (OLA) status in the `Network interfaces`{.action} tab. At the bottom of the **Bandwidth** section, locate the **OVHcloud Link Aggregation** row.
-To restore OLA to the default values, click on the `...`{.action} button to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Then click `Unconfigure private aggregation`{.action}. Click `Confirm`{.action} in the popup menu.
+There are four possible status tags:
+- **Unavailable**: OLA is not supported on this dedicated server model.
+- **Available**: OLA is supported but is not configured.
+- **Active - Fully Private**: OLA is enabled; all physical interfaces are aggregated into a single private link for vRack use.
+- **Active - Double LAG**: OLA is pre-enabled; physical interfaces are split into two separate aggregates (one public, one private).
-{.thumbnail}
+> [!primary]
+> **Note:** The **Active - Double LAG** status is a specific configuration typically reserved for Scale and High-Grade server ranges, which feature four physical network interfaces.
+>
+
+### Restoring OLA to default values
+
+To restore OLA to the default values, click the `Disaggregate networks`{.action} button in the **Network Interface Controllers (NICs)** section. Click `Confirm`{.action} in the popup menu.
This may take a few minutes.
@@ -74,4 +88,3 @@ This may take a few minutes.
[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Join our [community of users](/links/community).
-
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-au.md
index 278f98c0a3e..6f236670c8c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-au.md
@@ -1,7 +1,7 @@
---
title: 'Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel'
excerpt: 'Find out how to enable OVHcloud Link Aggregation in the OVHcloud Control Panel'
-updated: 2023-03-07
+updated: 2026-04-20
---
## Objective
@@ -38,28 +38,42 @@ Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) t
### Configuring OLA in the OVHcloud Control Panel
-Click on `Dedicated Servers`{.action} and select your server from the list.
+To start configuring OLA, open the `Network interfaces`{.action} tab on your server's management page.
-{.thumbnail}
+Click the `Network Aggregation`{.action} button in the **Network Interface Controllers (NICs)** section.
-In the tab `Network interfaces`{.action} (1), click on the `...`{.action} button (2) to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Next, click `Configure private aggregation`{.action} (2).
+You will be shown two tables:
+- On the left, the current configuration of your network interfaces;
+- On the right, the simulated configuration of your aggregated network interfaces.
-{.thumbnail}
+In the field below the tables, enter a name for your link aggregation.
-Make sure that both your interfaces, or interface groups, are selected and give the OLA a name. Click `Confirm`{.action} when your checks are complete.
+Once you have verified that the aggregation layout matches your network requirements, click `Enable Aggregation`{.action} to proceed.
This may take a few minutes. Once it is complete, the next step is to configure the interfaces in your operating system via a NIC link or NIC team. For the method to use, refer to the following guides for the most popular operating systems:
- [How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9 using ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
- [How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
- [How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-### Restoring OLA to default values
+### Checking the OLA status
+
+You can verify your Link Aggregation (OLA) status in the `Network interfaces`{.action} tab. At the bottom of the **Bandwidth** section, locate the **OVHcloud Link Aggregation** row.
-To restore OLA to the default values, click on the `...`{.action} button to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Then click `Unconfigure private aggregation`{.action}. Click `Confirm`{.action} in the popup menu.
+There are four possible status tags:
+- **Unavailable**: OLA is not supported on this dedicated server model.
+- **Available**: OLA is supported but is not configured.
+- **Active - Fully Private**: OLA is enabled; all physical interfaces are aggregated into a single private link for vRack use.
+- **Active - Double LAG**: OLA is pre-enabled; physical interfaces are split into two separate aggregates (one public, one private).
-{.thumbnail}
+> [!primary]
+> **Note:** The **Active - Double LAG** status is a specific configuration typically reserved for Scale and High-Grade server ranges, which feature four physical network interfaces.
+>
+
+### Restoring OLA to default values
+
+To restore OLA to the default values, click the `Disaggregate networks`{.action} button in the **Network Interface Controllers (NICs)** section. Click `Confirm`{.action} in the popup menu.
This may take a few minutes.
@@ -74,4 +88,3 @@ This may take a few minutes.
[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Join our [community of users](/links/community).
-
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-ca.md
index 278f98c0a3e..6f236670c8c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-ca.md
@@ -1,7 +1,7 @@
---
title: 'Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel'
excerpt: 'Find out how to enable OVHcloud Link Aggregation in the OVHcloud Control Panel'
-updated: 2023-03-07
+updated: 2026-04-20
---
## Objective
@@ -38,28 +38,42 @@ Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) t
### Configuring OLA in the OVHcloud Control Panel
-Click on `Dedicated Servers`{.action} and select your server from the list.
+To start configuring OLA, open the `Network interfaces`{.action} tab on your server's management page.
-{.thumbnail}
+Click the `Network Aggregation`{.action} button in the **Network Interface Controllers (NICs)** section.
-In the tab `Network interfaces`{.action} (1), click on the `...`{.action} button (2) to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Next, click `Configure private aggregation`{.action} (2).
+You will be shown two tables:
+- On the left, the current configuration of your network interfaces;
+- On the right, the simulated configuration of your aggregated network interfaces.
-{.thumbnail}
+In the field below the tables, enter a name for your link aggregation.
-Make sure that both your interfaces, or interface groups, are selected and give the OLA a name. Click `Confirm`{.action} when your checks are complete.
+Once you have verified that the aggregation layout matches your network requirements, click `Enable Aggregation`{.action} to proceed.
This may take a few minutes. Once it is complete, the next step is to configure the interfaces in your operating system via a NIC link or NIC team. For the method to use, refer to the following guides for the most popular operating systems:
- [How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9 using ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
- [How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
- [How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-### Restoring OLA to default values
+### Checking the OLA status
+
+You can verify your Link Aggregation (OLA) status in the `Network interfaces`{.action} tab. At the bottom of the **Bandwidth** section, locate the **OVHcloud Link Aggregation** row.
-To restore OLA to the default values, click on the `...`{.action} button to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Then click `Unconfigure private aggregation`{.action}. Click `Confirm`{.action} in the popup menu.
+There are four possible status tags:
+- **Unavailable**: OLA is not supported on this dedicated server model.
+- **Available**: OLA is supported but is not configured.
+- **Active - Fully Private**: OLA is enabled; all physical interfaces are aggregated into a single private link for vRack use.
+- **Active - Double LAG**: OLA is pre-enabled; physical interfaces are split into two separate aggregates (one public, one private).
-{.thumbnail}
+> [!primary]
+> **Note:** The **Active - Double LAG** status is a specific configuration typically reserved for Scale and High-Grade server ranges, which feature four physical network interfaces.
+>
+
+### Restoring OLA to default values
+
+To restore OLA to the default values, click the `Disaggregate networks`{.action} button in the **Network Interface Controllers (NICs)** section. Click `Confirm`{.action} in the popup menu.
This may take a few minutes.
@@ -74,4 +88,3 @@ This may take a few minutes.
[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Join our [community of users](/links/community).
-
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-gb.md
index 5701b920ee8..a0a791c7373 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-gb.md
@@ -1,7 +1,7 @@
---
title: 'Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel'
excerpt: 'Find out how to enable OVHcloud Link Aggregation in the OVHcloud Control Panel'
-updated: 2022-05-18
+updated: 2026-04-20
---
## Objective
@@ -40,26 +40,40 @@ Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) t
To start configuring OLA, open the `Network interfaces`{.action} tab on your server's management page.
-{.thumbnail}
+Click the `Network Aggregation`{.action} button in the **Network Interface Controllers (NICs)** section.
-In the tab `Network interfaces`{.action} (1), click on the `...`{.action} button (2) to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Next, click `Configure private aggregation`{.action} (2).
+You will be shown two tables:
+- On the left, the current configuration of your network interfaces;
+- On the right, the simulated configuration of your aggregated network interfaces.
-{.thumbnail}
+In the field below the tables, enter a name for your link aggregation.
-Make sure that both your interfaces, or interface groups, are selected and give the OLA a name. Click `Confirm`{.action} when your checks are complete.
+Once you have verified that the aggregation layout matches your network requirements, click `Enable Aggregation`{.action} to proceed.
This may take a few minutes. Once it is complete, the next step is to configure the interfaces in your operating system via a NIC link or NIC team. For the method to use, refer to the following guides for the most popular operating systems:
- [How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9 using ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
- [How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
- [How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-### Restoring OLA to default values
+### Checking the OLA status
+
+You can verify your Link Aggregation (OLA) status in the `Network interfaces`{.action} tab. At the bottom of the **Bandwidth** section, locate the **OVHcloud Link Aggregation** row.
+
+There are four possible status tags:
+- **Unavailable**: OLA is not supported on this dedicated server model.
+- **Available**: OLA is supported but is not configured.
+- **Active - Fully Private**: OLA is enabled; all physical interfaces are aggregated into a single private link for vRack use.
+- **Active - Double LAG**: OLA is pre-enabled; physical interfaces are split into two separate aggregates (one public, one private).
-To restore OLA to the default values, click on the `...`{.action} button to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Then click `Unconfigure private aggregation`{.action}. Click `Confirm`{.action} in the popup menu.
+> [!primary]
+> **Note:** The **Active - Double LAG** status is a specific configuration typically reserved for Scale and High-Grade server ranges, which feature four physical network interfaces.
+>
+
+### Restoring OLA to default values
-{.thumbnail}
+To restore OLA to the default values, click on the `Disaggregate networks`{.action} button at the top of the **Network Interface Controllers** section. Click `Confirm`{.action} in the popup menu.
This may take a few minutes.
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-ie.md
index 278f98c0a3e..6f236670c8c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-ie.md
@@ -1,7 +1,7 @@
---
title: 'Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel'
excerpt: 'Find out how to enable OVHcloud Link Aggregation in the OVHcloud Control Panel'
-updated: 2023-03-07
+updated: 2026-04-20
---
## Objective
@@ -38,28 +38,42 @@ Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) t
### Configuring OLA in the OVHcloud Control Panel
-Click on `Dedicated Servers`{.action} and select your server from the list.
+To start configuring OLA, open the `Network interfaces`{.action} tab on your server's management page.
-{.thumbnail}
+Click the `Network Aggregation`{.action} button in the **Network Interface Controllers (NICs)** section.
-In the tab `Network interfaces`{.action} (1), click on the `...`{.action} button (2) to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Next, click `Configure private aggregation`{.action} (2).
+You will be shown two tables:
+- On the left, the current configuration of your network interfaces;
+- On the right, the simulated configuration of your aggregated network interfaces.
-{.thumbnail}
+In the field below the tables, enter a name for your link aggregation.
-Make sure that both your interfaces, or interface groups, are selected and give the OLA a name. Click `Confirm`{.action} when your checks are complete.
+Once you have verified that the aggregation layout matches your network requirements, click `Enable Aggregation`{.action} to proceed.
This may take a few minutes. Once it is complete, the next step is to configure the interfaces in your operating system via a NIC link or NIC team. For the method to use, refer to the following guides for the most popular operating systems:
- [How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9 using ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
- [How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
- [How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-### Restoring OLA to default values
+### Checking the OLA status
+
+You can verify your Link Aggregation (OLA) status in the `Network interfaces`{.action} tab. At the bottom of the **Bandwidth** section, locate the **OVHcloud Link Aggregation** row.
-To restore OLA to the default values, click on the `...`{.action} button to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Then click `Unconfigure private aggregation`{.action}. Click `Confirm`{.action} in the popup menu.
+There are four possible status tags:
+- **Unavailable**: OLA is not supported on this dedicated server model.
+- **Available**: OLA is supported but is not configured.
+- **Active - Fully Private**: OLA is enabled; all physical interfaces are aggregated into a single private link for vRack use.
+- **Active - Double LAG**: OLA is pre-enabled; physical interfaces are split into two separate aggregates (one public, one private).
-{.thumbnail}
+> [!primary]
+> **Note:** The **Active - Double LAG** status is a specific configuration typically reserved for Scale and High-Grade server ranges, which feature four physical network interfaces.
+>
+
+### Restoring OLA to default values
+
+To restore OLA to the default values, click the `Disaggregate networks`{.action} button in the **Network Interface Controllers (NICs)** section. Click `Confirm`{.action} in the popup menu.
This may take a few minutes.
@@ -74,4 +88,3 @@ This may take a few minutes.
[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Join our [community of users](/links/community).
-
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-sg.md
index 278f98c0a3e..6f236670c8c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-sg.md
@@ -1,7 +1,7 @@
---
title: 'Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel'
excerpt: 'Find out how to enable OVHcloud Link Aggregation in the OVHcloud Control Panel'
-updated: 2023-03-07
+updated: 2026-04-20
---
## Objective
@@ -38,28 +38,42 @@ Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) t
### Configuring OLA in the OVHcloud Control Panel
-Click on `Dedicated Servers`{.action} and select your server from the list.
+To start configuring OLA, open the `Network interfaces`{.action} tab on your server's management page.
-{.thumbnail}
+Click the `Network Aggregation`{.action} button in the **Network Interface Controllers (NICs)** section.
-In the tab `Network interfaces`{.action} (1), click on the `...`{.action} button (2) to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Next, click `Configure private aggregation`{.action} (2).
+You will be shown two tables:
+- On the left, the current configuration of your network interfaces;
+- On the right, the simulated configuration of your aggregated network interfaces.
-{.thumbnail}
+In the field below the tables, enter a name for your link aggregation.
-Make sure that both your interfaces, or interface groups, are selected and give the OLA a name. Click `Confirm`{.action} when your checks are complete.
+Once you have verified that the aggregation layout matches your network requirements, click `Enable Aggregation`{.action} to proceed.
This may take a few minutes. Once it is complete, the next step is to configure the interfaces in your operating system via a NIC link or NIC team. For the method to use, refer to the following guides for the most popular operating systems:
- [How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9 using ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
- [How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
- [How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-### Restoring OLA to default values
+### Checking the OLA status
+
+You can verify your Link Aggregation (OLA) status in the `Network interfaces`{.action} tab. At the bottom of the **Bandwidth** section, locate the **OVHcloud Link Aggregation** row.
-To restore OLA to the default values, click on the `...`{.action} button to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Then click `Unconfigure private aggregation`{.action}. Click `Confirm`{.action} in the popup menu.
+There are four possible status tags:
+- **Unavailable**: OLA is not supported on this dedicated server model.
+- **Available**: OLA is supported but is not configured.
+- **Active - Fully Private**: OLA is enabled; all physical interfaces are aggregated into a single private link for vRack use.
+- **Active - Double LAG**: OLA is pre-enabled; physical interfaces are split into two separate aggregates (one public, one private).
-{.thumbnail}
+> [!primary]
+> **Note:** The **Active - Double LAG** status is a specific configuration typically reserved for Scale and High-Grade server ranges, which feature four physical network interfaces.
+>
+
+### Restoring OLA to default values
+
+To restore OLA to the default values, click the `Disaggregate networks`{.action} button in the **Network Interface Controllers (NICs)** section. Click `Confirm`{.action} in the popup menu.
This may take a few minutes.
@@ -74,4 +88,3 @@ This may take a few minutes.
[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Join our [community of users](/links/community).
-
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-us.md
index 278f98c0a3e..6f236670c8c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.en-us.md
@@ -1,7 +1,7 @@
---
title: 'Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel'
excerpt: 'Find out how to enable OVHcloud Link Aggregation in the OVHcloud Control Panel'
-updated: 2023-03-07
+updated: 2026-04-20
---
## Objective
@@ -38,28 +38,42 @@ Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) t
### Configuring OLA in the OVHcloud Control Panel
-Click on `Dedicated Servers`{.action} and select your server from the list.
+To start configuring OLA, open the `Network interfaces`{.action} tab on your server's management page.
-{.thumbnail}
+Click the `Network Aggregation`{.action} button in the **Network Interface Controllers (NICs)** section.
-In the tab `Network interfaces`{.action} (1), click on the `...`{.action} button (2) to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Next, click `Configure private aggregation`{.action} (2).
+You will be shown two tables:
+- On the left, the current configuration of your network interfaces;
+- On the right, the simulated configuration of your aggregated network interfaces.
-{.thumbnail}
+In the field below the tables, enter a name for your link aggregation.
-Make sure that both your interfaces, or interface groups, are selected and give the OLA a name. Click `Confirm`{.action} when your checks are complete.
+Once you have verified that the aggregation layout matches your network requirements, click `Enable Aggregation`{.action} to proceed.
This may take a few minutes. Once it is complete, the next step is to configure the interfaces in your operating system via a NIC link or NIC team. For the method to use, refer to the following guides for the most popular operating systems:
- [How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9 using ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
- [How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
- [How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+- [How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-### Restoring OLA to default values
+### Checking the OLA status
+
+You can verify your Link Aggregation (OLA) status in the `Network interfaces`{.action} tab. At the bottom of the **Bandwidth** section, locate the **OVHcloud Link Aggregation** row.
-To restore OLA to the default values, click on the `...`{.action} button to the right of "Mode" in the **OLA: OVHcloud Link Aggregation** box. Then click `Unconfigure private aggregation`{.action}. Click `Confirm`{.action} in the popup menu.
+There are four possible status tags:
+- **Unavailable**: OLA is not supported on this dedicated server model.
+- **Available**: OLA is supported but is not configured.
+- **Active - Fully Private**: OLA is enabled; all physical interfaces are aggregated into a single private link for vRack use.
+- **Active - Double LAG**: OLA is pre-enabled; physical interfaces are split into two separate aggregates (one public, one private).
-{.thumbnail}
+> [!primary]
+> **Note:** The **Active - Double LAG** status is a specific configuration typically reserved for Scale and High-Grade server ranges, which feature four physical network interfaces.
+>
+
+### Restoring OLA to default values
+
+To restore OLA to the default values, click the `Disaggregate networks`{.action} button in the **Network Interface Controllers (NICs)** section. Click `Confirm`{.action} in the popup menu.
This may take a few minutes.
@@ -74,4 +88,3 @@ This may take a few minutes.
[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Join our [community of users](/links/community).
-
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.es-es.md
index 1b404a43b75..ba14a46b06e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.es-es.md
@@ -1,7 +1,7 @@
---
title: 'Configurar el servicio OVHcloud Link Aggregation desde el área de cliente de OVHcloud'
excerpt: 'Activar el servicio OVHcloud Link Aggregation en el área de cliente'
-updated: 2022-05-18
+updated: 2026-04-20
---
## Objetivo
@@ -38,42 +38,53 @@ La agregación se basa en la tecnología IEEE 802.3ad o Link Aggregation Control
### Configurar OLA en el área de cliente de OVHcloud
-Haga clic en `Servidores dedicados`{.action} y seleccione el servidor en la lista.
+Para comenzar la configuración de OLA, abra la pestaña `Interfaces de red`{.action} en la página de administración de su servidor.
-{.thumbnail}
+Haga clic en el botón `Agregación de redes`{.action} en la sección **Controladores de interfaz de red (NIC)**.
-En la pestaña `Interfaces de red`{.action} (1), haga clic en el botón `...`{.action} (2) a la derecha de "Modo" en el cuadro **OLA: OVHcloud Link Aggregation**. Haga clic en `Configurar la agregación privada`{.action} (2).
+Se le mostrarán dos tablas:
+- A la izquierda, la configuración actual de sus interfaces de red;
+- A la derecha, la configuración simulada de sus interfaces de red agregadas.
-{.thumbnail}
+En el campo situado debajo de las tablas, introduzca un nombre para su agregación de enlaces.
-Compruebe que las dos interfaces, o grupos de interfaces, estén bien seleccionadas y asigne un nombre a la interfaz OLA. Haga clic en `Confirmar`{.action} una vez que haya finalizado la verificación.
+Una vez que haya verificado que la configuración de la agregación cumple con sus requisitos de red, haga clic en `Activar la agregación`{.action} para continuar.
La operación puede tardar unos minutos. Cuando haya terminado, el paso siguiente será configurar las interfaces de su sistema operativo con un vínculo NIC o un equipo NIC. Para saber cómo proceder, puede consultar las siguientes guías diseñadas para los sistemas operativos más populares:
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9 a través de ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+- [Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+- [How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+### Verificar el estado de OLA
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+Puede verificar el estado de su agregación de enlaces (OLA) en la pestaña `Interfaces de red`{.action}. En la parte inferior de la sección **Tráfico**, localice la fila **OVHcloud Link Aggregation**.
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+Existen cuatro posibles etiquetas de estado:
+- **No disponible**: OLA no es compatible con este modelo de servidor dedicado.
+- **Disponible**: OLA es compatible pero no está configurado.
+- **Activo - Totalmente privado**: OLA está activado; todas las interfaces físicas están agregadas en un único enlace privado para uso de vRack.
+- **Activo - LAG doble**: OLA está preactivado; las interfaces físicas se dividen en dos agregados separados (uno público, uno privado).
-### Restaurar OLA a los valores predeterminados
+> [!primary]
+> **Nota:** El estado **Activo - LAG doble** es una configuración específica generalmente reservada para las gamas de servidores Scale y High-Grade, que cuentan con cuatro interfaces de red físicas.
+>
-Para restablecer OLA a los valores predeterminados, haga clic en el botón `...`{.action} a la derecha de "Modo" en el recuadro **OLA: OVHcloud Link Aggregation**. Haga clic en `Desconfigurar la agregación privada`{.action}. Haga clic en `Confirmar`{.action} en el menú contextual.
+### Restaurar OLA a los valores predeterminados
-{.thumbnail}
+Para restablecer OLA a los valores predeterminados, haga clic en el botón `Desagregar redes`{.action} en la sección **Controladores de interfaz de red (NIC)**. Haga clic en `Confirmar`{.action} en el menú contextual.
La operación puede tardar unos minutos.
## Más información
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9 a través de ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
[Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
[Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.es-us.md
index 7a90beb6d39..ba14a46b06e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.es-us.md
@@ -1,7 +1,7 @@
---
title: 'Configurar el servicio OVHcloud Link Aggregation desde el área de cliente de OVHcloud'
excerpt: 'Activar el servicio OVHcloud Link Aggregation en el área de cliente'
-updated: 2022-05-18
+updated: 2026-04-20
---
## Objetivo
@@ -38,31 +38,42 @@ La agregación se basa en la tecnología IEEE 802.3ad o Link Aggregation Control
### Configurar OLA en el área de cliente de OVHcloud
-Haga clic en `Servidores dedicados`{.action} y seleccione el servidor en la lista.
+Para comenzar la configuración de OLA, abra la pestaña `Interfaces de red`{.action} en la página de administración de su servidor.
-{.thumbnail}
+Haga clic en el botón `Agregación de redes`{.action} en la sección **Controladores de interfaz de red (NIC)**.
-En la pestaña `Interfaces de red`{.action} (1), haga clic en el botón `...`{.action} (2) a la derecha de "Modo" en el cuadro **OLA: OVHcloud Link Aggregation**. Haga clic en `Configurar la agregación privada`{.action} (2).
+Se le mostrarán dos tablas:
+- A la izquierda, la configuración actual de sus interfaces de red;
+- A la derecha, la configuración simulada de sus interfaces de red agregadas.
-{.thumbnail}
+En el campo situado debajo de las tablas, introduzca un nombre para su agregación de enlaces.
-Compruebe que las dos interfaces, o grupos de interfaces, estén bien seleccionadas y asigne un nombre a la interfaz OLA. Haga clic en `Confirmar`{.action} una vez que haya finalizado la verificación.
+Una vez que haya verificado que la configuración de la agregación cumple con sus requisitos de red, haga clic en `Activar la agregación`{.action} para continuar.
La operación puede tardar unos minutos. Cuando haya terminado, el paso siguiente será configurar las interfaces de su sistema operativo con un vínculo NIC o un equipo NIC. Para saber cómo proceder, puede consultar las siguientes guías diseñadas para los sistemas operativos más populares:
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+- [Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+- [How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+### Verificar el estado de OLA
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+Puede verificar el estado de su agregación de enlaces (OLA) en la pestaña `Interfaces de red`{.action}. En la parte inferior de la sección **Tráfico**, localice la fila **OVHcloud Link Aggregation**.
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+Existen cuatro posibles etiquetas de estado:
+- **No disponible**: OLA no es compatible con este modelo de servidor dedicado.
+- **Disponible**: OLA es compatible pero no está configurado.
+- **Activo - Totalmente privado**: OLA está activado; todas las interfaces físicas están agregadas en un único enlace privado para uso de vRack.
+- **Activo - LAG doble**: OLA está preactivado; las interfaces físicas se dividen en dos agregados separados (uno público, uno privado).
-### Restaurar OLA a los valores predeterminados
+> [!primary]
+> **Nota:** El estado **Activo - LAG doble** es una configuración específica generalmente reservada para las gamas de servidores Scale y High-Grade, que cuentan con cuatro interfaces de red físicas.
+>
-Para restablecer OLA a los valores predeterminados, haga clic en el botón `...`{.action} a la derecha de "Modo" en el recuadro **OLA: OVHcloud Link Aggregation**. Haga clic en `Desconfigurar la agregación privada`{.action}. Haga clic en `Confirmar`{.action} en el menú contextual.
+### Restaurar OLA a los valores predeterminados
-{.thumbnail}
+Para restablecer OLA a los valores predeterminados, haga clic en el botón `Desagregar redes`{.action} en la sección **Controladores de interfaz de red (NIC)**. Haga clic en `Confirmar`{.action} en el menú contextual.
La operación puede tardar unos minutos.
@@ -74,6 +85,6 @@ La operación puede tardar unos minutos.
[Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.fr-ca.md
index a8a6d6b627b..9e850988ea3 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.fr-ca.md
@@ -1,15 +1,15 @@
---
-title: 'Configurer l’agrégation de liens OLA dans votre espace client'
-excerpt: 'Découvrez comment activer l’agrégation de liens OVHcloud dans votre espace client.'
-updated: 2023-03-07
+title: "Configurer l'agrégation de liens OLA dans votre espace client"
+excerpt: "Découvrez comment activer l'agrégation de liens OVHcloud dans votre espace client."
+updated: 2026-04-20
---
## Objectif
La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible.
-L'aggrégation se base sur la technologie IEEE 802.3ad, ou Link Aggregation Control Protocol (LACP).
+L'agrégation se base sur la technologie IEEE 802.3ad, ou Link Aggregation Control Protocol (LACP).
-**Découvrez comment configurer OLA dans votre espace client.**
+**Découvrez comment configurer OLA dans votre espace client OVHcloud.**
## Prérequis
@@ -31,49 +31,60 @@ L'aggrégation se base sur la technologie IEEE 802.3ad, ou Link Aggregation Cont
> [!warning]
>
-> La configuration OLA se fait sur la totalité des interfaces réseaux. Elles formeront un agrégat de type « agrégation privée ».
+> La configuration OLA se fait sur la totalité des interfaces réseaux. Elles formeront une « agrégation privée ».
>
-> Suite à la mise en oeuvre d'OLA, l'IP publique ne sera donc plus accessible.
+> Suite à la mise en œuvre d'OLA, l'IP publique ne sera donc plus accessible.
>
### Configurer OLA dans votre espace client OVHcloud
-Cliquez sur `Serveurs dédiés`{.action} et sélectionnez votre serveur dans la liste.
+Pour commencer à configurer OLA, ouvrez l'onglet `Interfaces réseau`{.action} sur la page de gestion de votre serveur.
-{.thumbnail}
+Dans l'onglet `Interfaces réseau`{.action}, cliquez sur le bouton `Agrégation réseaux`{.action} dans la section **Contrôleurs d'interfaces réseau (NICs)**.
-Dans l'onglet `Interfaces réseau`{.action} (1), cliquez sur le bouton `...`{.action} (2) à droite de « Mode » dans le cadre **OLA: OVHcloud Link Aggregation**. Cliquez alors sur `Configurer l'agrégation privée`{.action} (2).
+Deux tableaux vous seront présentés :
+- À gauche, la configuration actuelle de vos interfaces réseau ;
+- À droite, la configuration simulée de vos interfaces réseau agrégées.
-{.thumbnail}
+Dans le champ situé sous les tableaux, saisissez un nom pour votre agrégation de liens.
-Vérifiez que vos deux interfaces, ou groupes d'interfaces, sont bien sélectionnés et donnez un nom à l'interface OLA. Cliquez sur `Confirmer`{.action} une fois vos vérifications terminées.
+Une fois que vous avez vérifié que la configuration de l'agrégation correspond à vos besoins réseau, cliquez sur `Activer l'agrégation`{.action} pour procéder.
L'opération peut prendre quelques minutes. Une fois celle-ci terminée, l'étape suivante consiste à configurer les interfaces dans votre système d'exploitation via une liaison NIC ou une équipe NIC. Pour connaître la méthode à appliquer, consultez les guides suivants qui la détaillent pour les systèmes d'exploitation les plus populaires :
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 via ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 via ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+- [Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+- [Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans Debian 12 ou Ubuntu 24.04 via Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+### Vérification du statut OLA
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+Vous pouvez vérifier le statut de votre agrégation de liens (OLA) dans l'onglet `Interfaces réseau`{.action}. En bas de la section **Bande passante**, repérez la ligne **OVHcloud Link Aggregation**.
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans Debian 12 ou Ubuntu 24.04 via Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+Il existe quatre statuts possibles :
+- **Unavailable** : OLA n'est pas pris en charge sur ce modèle de serveur dédié.
+- **Available** : OLA est pris en charge mais n'est pas configuré.
+- **Active - Fully Private** : OLA est activé ; toutes les interfaces physiques sont agrégées dans un seul lien privé pour une utilisation vRack.
+- **Active - Double LAG** : OLA est pré-activé ; les interfaces physiques sont réparties en deux agrégats distincts (un public, un privé).
-### Restaurer OLA aux valeurs par défaut
+> [!primary]
+> Le statut **Active - Double LAG** est une configuration spécifique généralement réservée aux gammes de serveurs Scale et High-Grade, qui disposent de quatre interfaces réseau physiques.
+>
-Pour restaurer OLA aux valeurs par défaut, cliquez sur le bouton `...`{.action} à droite de « Mode » dans le cadre **OLA: OVHcloud Link Aggregation**. Cliquez alors sur `Déconfigurer l'agrégation privée`{.action}. Cliquez sur `Confirmer`{.action} dans le menu contextuel.
+### Restauration des valeurs par défaut d'OLA
-{.thumbnail}
+Pour restaurer OLA aux valeurs par défaut, cliquez sur le bouton `Désagréger les réseaux`{.action} dans la section **Contrôleurs d'interfaces réseau (NICs)**. Cliquez sur `Confirmer`{.action} dans le menu contextuel.
L'opération peut prendre quelques minutes.
## Aller plus loin
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 via ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 via ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans Debian 12 ou Ubuntu 24.04 via Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans Debian 12 ou Ubuntu 24.04 via Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.fr-fr.md
index 3c12376f40a..9e850988ea3 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.fr-fr.md
@@ -1,13 +1,13 @@
---
-title: 'Configurer l’agrégation de liens OLA dans votre espace client'
-excerpt: 'Découvrez comment activer l’agrégation de liens OVHcloud dans votre espace client.'
-updated: 2023-03-07
+title: "Configurer l'agrégation de liens OLA dans votre espace client"
+excerpt: "Découvrez comment activer l'agrégation de liens OVHcloud dans votre espace client."
+updated: 2026-04-20
---
## Objectif
La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible.
-L'aggrégation se base sur la technologie IEEE 802.3ad, ou Link Aggregation Control Protocol (LACP).
+L'agrégation se base sur la technologie IEEE 802.3ad, ou Link Aggregation Control Protocol (LACP).
**Découvrez comment configurer OLA dans votre espace client OVHcloud.**
@@ -31,49 +31,60 @@ L'aggrégation se base sur la technologie IEEE 802.3ad, ou Link Aggregation Cont
> [!warning]
>
-> La configuration OLA se fait sur la totalité des interfaces réseaux. Elles formeront un agrégat de type « agrégation privée ».
+> La configuration OLA se fait sur la totalité des interfaces réseaux. Elles formeront une « agrégation privée ».
>
-> Suite à la mise en oeuvre d'OLA, l'IP publique ne sera donc plus accessible.
+> Suite à la mise en œuvre d'OLA, l'IP publique ne sera donc plus accessible.
>
### Configurer OLA dans votre espace client OVHcloud
Pour commencer à configurer OLA, ouvrez l'onglet `Interfaces réseau`{.action} sur la page de gestion de votre serveur.
-{.thumbnail}
+Dans l'onglet `Interfaces réseau`{.action}, cliquez sur le bouton `Agrégation réseaux`{.action} dans la section **Contrôleurs d'interfaces réseau (NICs)**.
-Dans l'onglet `Interfaces réseau`{.action} (1), cliquez sur le bouton `...`{.action} (2) à droite de « Mode » dans le cadre **OLA: OVHcloud Link Aggregation**. Cliquez alors sur `Configurer l'agrégation privée`{.action} (2).
+Deux tableaux vous seront présentés :
+- À gauche, la configuration actuelle de vos interfaces réseau ;
+- À droite, la configuration simulée de vos interfaces réseau agrégées.
-{.thumbnail}
+Dans le champ situé sous les tableaux, saisissez un nom pour votre agrégation de liens.
-Vérifiez que vos deux interfaces, ou groupes d'interfaces, sont bien sélectionnés et donnez un nom à l'interface OLA. Cliquez sur `Confirmer`{.action} une fois vos vérifications terminées.
+Une fois que vous avez vérifié que la configuration de l'agrégation correspond à vos besoins réseau, cliquez sur `Activer l'agrégation`{.action} pour procéder.
L'opération peut prendre quelques minutes. Une fois celle-ci terminée, l'étape suivante consiste à configurer les interfaces dans votre système d'exploitation via une liaison NIC ou une équipe NIC. Pour connaître la méthode à appliquer, consultez les guides suivants qui la détaillent pour les systèmes d'exploitation les plus populaires :
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 via ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 via ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+- [Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+- [Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans Debian 12 ou Ubuntu 24.04 via Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+### Vérification du statut OLA
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+Vous pouvez vérifier le statut de votre agrégation de liens (OLA) dans l'onglet `Interfaces réseau`{.action}. En bas de la section **Bande passante**, repérez la ligne **OVHcloud Link Aggregation**.
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans Debian 12 ou Ubuntu 24.04 via Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+Il existe quatre statuts possibles :
+- **Unavailable** : OLA n'est pas pris en charge sur ce modèle de serveur dédié.
+- **Available** : OLA est pris en charge mais n'est pas configuré.
+- **Active - Fully Private** : OLA est activé ; toutes les interfaces physiques sont agrégées dans un seul lien privé pour une utilisation vRack.
+- **Active - Double LAG** : OLA est pré-activé ; les interfaces physiques sont réparties en deux agrégats distincts (un public, un privé).
-### Restaurer OLA aux valeurs par défaut
+> [!primary]
+> Le statut **Active - Double LAG** est une configuration spécifique généralement réservée aux gammes de serveurs Scale et High-Grade, qui disposent de quatre interfaces réseau physiques.
+>
-Pour restaurer OLA aux valeurs par défaut, cliquez sur le bouton `...`{.action} à droite de « Mode » dans le cadre **OLA: OVHcloud Link Aggregation**. Cliquez alors sur `Déconfigurer l'agrégation privée`{.action}. Cliquez sur `Confirmer`{.action} dans le menu contextuel.
+### Restauration des valeurs par défaut d'OLA
-{.thumbnail}
+Pour restaurer OLA aux valeurs par défaut, cliquez sur le bouton `Désagréger les réseaux`{.action} dans la section **Contrôleurs d'interfaces réseau (NICs)**. Cliquez sur `Confirmer`{.action} dans le menu contextuel.
L'opération peut prendre quelques minutes.
## Aller plus loin
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 via ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 via ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans Debian 12 ou Ubuntu 24.04 via Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans Debian 12 ou Ubuntu 24.04 via Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.it-it.md
index ee181ee34a8..9469f982691 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.it-it.md
@@ -1,7 +1,7 @@
---
title: 'Configurare un NIC per il servizio OVHcloud Link Aggregation nello Spazio Cliente'
excerpt: "Attivare l'opzione OVHcloud Link Aggregation dalla tua area Cliente OVHcloud"
-updated: 2022-05-18
+updated: 2026-04-20
---
## Obiettivo
@@ -38,31 +38,42 @@ L'aggregazione si basa sulla tecnologia IEEE 802.3ad o Link Aggregation Control
### Configurare OLA nel tuo Spazio Cliente OVHcloud
-Clicca su `Server dedicati`{.action} e seleziona il tuo server nella lista.
+Per iniziare la configurazione di OLA, apri la scheda `Interfacce di rete`{.action} nella pagina di gestione del tuo server.
-{.thumbnail}
+Clicca sul pulsante `Aggregazione delle reti`{.action} nella sezione **Controller delle interfacce di rete (NIC)**.
-Nella scheda `Interfacce di rete`{.action} (1), clicca sul pulsante `...`{.action} (2) a destra di "Modo" nell'ambito **OLA: OVHcloud Link Aggregation**. Clicca su `Configura l'aggregazione privata`{.action} (2).
+Verranno visualizzate due tabelle:
+- A sinistra, la configurazione attuale delle tue interfacce di rete;
+- A destra, la configurazione simulata delle tue interfacce di rete aggregate.
-{.thumbnail}
+Nel campo sotto le tabelle, inserisci un nome per la tua aggregazione di collegamenti.
-Verifica che le tue due interfacce, o gruppi di interfacce, siano selezionate correttamente e assegna un nome all'interfaccia OLA. Clicca su `Conferma`{.action} una volta completata la verifica.
+Dopo aver verificato che la configurazione dell'aggregazione soddisfi i requisiti di rete, clicca su `Attivare aggregazione`{.action} per procedere.
Questa operazione potrebbe richiedere qualche minuto. Lo step successivo consisterà nella configurazione delle interfacce del sistema operativo come NIC bond o NIC team. Per conoscere la procedura da seguire, consulta la nostra documentazione disponibile relativa ai sistemi operativi più diffusi:
-[Configurare un NIC per il servizio OVHcloud Link Aggregation in Debian 9 tramite ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+- [Configurare un NIC per il servizio OVHcloud Link Aggregation in Debian 9 tramite ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Configurare un NIC per il servizio OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+- [Configurare un NIC per il servizio OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+- [How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-[Configurare un NIC per il servizio OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
+### Verifica dello stato OLA
-[Configurare un NIC per il servizio OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+Puoi verificare lo stato della tua aggregazione di collegamenti (OLA) nella scheda `Interfacce di rete`{.action}. In fondo alla sezione **Banda passante**, individua la riga **OVHcloud Link Aggregation**.
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+Esistono quattro possibili etichette di stato:
+- **Non disponibile**: OLA non è supportato su questo modello di server dedicato.
+- **Disponibile**: OLA è supportato ma non è configurato.
+- **Attivo - Completamente privato**: OLA è attivato; tutte le interfacce fisiche sono aggregate in un unico collegamento privato per l'utilizzo con vRack.
+- **Attivo - LAG doppio**: OLA è pre-attivato; le interfacce fisiche sono divise in due aggregati separati (uno pubblico, uno privato).
-### Ripristina OLA ai valori predefiniti
+> [!primary]
+> **Nota:** Lo stato **Attivo - LAG doppio** è una configurazione specifica generalmente riservata alle gamme di server Scale e High-Grade, che dispongono di quattro interfacce di rete fisiche.
+>
-Per ripristinare OLA ai valori predefiniti, clicca sul pulsante `...`{.action} a destra di "Modo" nell'ambito **OLA: OVHcloud Link Aggregation**. Clicca su `Deconfigurare l'aggregazione privata`{.action}. Clicca su `Conferma`{.action} nel menu contestuale.
+### Ripristina OLA ai valori predefiniti
-{.thumbnail}
+Per ripristinare OLA ai valori predefiniti, clicca sul pulsante `Disaggrega le reti`{.action} nella sezione **Controller delle interfacce di rete (NIC)**. Clicca su `Conferma`{.action} nel menu contestuale.
L'operazione potrebbe richiedere alcuni minuti.
@@ -74,6 +85,6 @@ L'operazione potrebbe richiedere alcuni minuti.
[Configurare un NIC per il servizio OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
Contatta la nostra [Community di utenti](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.pl-pl.md
index 1883d0dea7d..365926860fd 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.pl-pl.md
@@ -1,7 +1,7 @@
---
title: 'Konfiguracja OVHcloud Link Aggregation w Panelu klienta'
excerpt: 'Dowiedz się, jak włączyć OVHcloud Link Aggregation w Panelu klienta'
-updated: 2022-05-18
+updated: 2026-04-20
---
## Wprowadzenie
@@ -38,31 +38,42 @@ Aggregacja oparta jest na technologii IEEE 802.3ad lub Link Aggregation Control
### Konfiguracja OLA w Panelu klienta OVHcloud
-Kliknij `Serwery Dedykowane`{.action} i wybierz Twój serwer z listy.
+Aby rozpocząć konfigurację OLA, otwórz zakładkę `Interfejsy sieciowe`{.action} na stronie zarządzania serwerem.
-{.thumbnail}
+W zakładce `Interfejsy sieciowe`{.action} kliknij przycisk `Agregacja sieci`{.action} w sekcji **Kontrolery interfejsów sieciowych**.
-W zakładce `Interfejsy sieciowe`{.action} (1) kliknij przycisk `...`{.action} (2) po prawej stronie "Tryb" w ramach **OLA: OVHcloud Link Aggregation**. Następnie kliknij `Skonfiguruj agregację prywatną`{.action} (2).
+Zostaną wyświetlone dwie tabele:
+- Po lewej stronie aktualna konfiguracja interfejsów sieciowych;
+- Po prawej stronie symulowana konfiguracja zagregowanych interfejsów sieciowych.
-{.thumbnail}
+W polu poniżej tabel wprowadź nazwę dla swojej agregacji łączy.
-Upewnij się, czy Twoje dwa interfejsy, czyli grupy interfejsów, są właściwie wybrane i nadaj nazwę interfejsowi OLA. Kliknij na `Potwierdź`{.action} po zakończeniu weryfikacji.
+Po sprawdzeniu, że układ agregacji spełnia wymagania sieciowe, kliknij `Włącz agregację`{.action}, aby kontynuować.
Zakończenie operacji może potrwać kilka minut. Kolejny krok to powiązanie interfejsów w systemie operacyjnym. Szczegółowe informacje na temat konfiguracji znajdziesz w przewodnikach:
-[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 9 przez ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+- [Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 9 przez ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+- [Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+- [How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
+### Sprawdzanie statusu OLA
-[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
+Możesz sprawdzić status agregacji łączy (OLA) w zakładce `Interfejsy sieciowe`{.action}. Na dole sekcji **Przepustowość** znajdź wiersz **OVHcloud Link Aggregation**.
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+Istnieją cztery możliwe oznaczenia statusu:
+- **Niedostępny**: OLA nie jest obsługiwany na tym modelu serwera dedykowanego.
+- **Dostępny**: OLA jest obsługiwany, ale nie jest skonfigurowany.
+- **Aktywny - W pełni prywatny**: OLA jest włączony; wszystkie fizyczne interfejsy są zagregowane w jedno prywatne łącze do użytku z vRack.
+- **Aktywny - Podwójny LAG**: OLA jest wstępnie włączony; fizyczne interfejsy są podzielone na dwa osobne agregaty (jeden publiczny, jeden prywatny).
-### Przywróć OLA do wartości domyślnych
+> [!primary]
+> **Uwaga:** Status **Aktywny - Podwójny LAG** to specyficzna konfiguracja zazwyczaj zarezerwowana dla serwerów z gamy Scale i High-Grade, które wyposażone są w cztery fizyczne interfejsy sieciowe.
+>
-Aby przywrócić OLA do wartości domyślnych, kliknij przycisk `...`{.action} po prawej stronie "Tryb" w ramce **OLA: OVHcloud Link Aggregation**. Następnie kliknij `Dekonfiguruj agregację prywatną`{.action}. Kliknij `Potwierdź`{.action} w menu kontekstowym.
+### Przywróć OLA do wartości domyślnych
-{.thumbnail}
+Aby przywrócić OLA do wartości domyślnych, kliknij przycisk `Dezagreguj sieci`{.action} u góry sekcji **Kontrolery interfejsów sieciowych**. Kliknij `Potwierdź`{.action} w menu kontekstowym.
Operacja może zająć kilka minut.
@@ -74,6 +85,6 @@ Operacja może zająć kilka minut.
[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Dołącz do [grona naszych użytkowników](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.pt-pt.md
index 5d85e045efa..93e585967e6 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager/guide.pt-pt.md
@@ -1,7 +1,7 @@
---
title: 'Como configurar a NIC para o OVHcloud Link Aggregation na Área de Cliente OVHcloud'
excerpt: 'Ative o OVHcloud Link Aggregation na sua Área de Cliente'
-updated: 2022-05-18
+updated: 2026-04-20
---
## Objetivo
@@ -38,31 +38,42 @@ A agregação baseia-se na tecnologia IEEE 802.3ad, ou Link Aggregation Control
### Configurar o OLA na Área de Cliente OVHcloud
-Clique em `Servidores dedicados`{.action} e selecione o seu servidor na lista.
+Para começar a configurar o OLA, abra o separador `Interfaces de rede`{.action} na página de gestão do seu servidor.
-{.thumbnail}
+Clique no botão `Agregação de redes`{.action} na secção **Controladores de interfaces de rede (NIC)**.
-No separador `Interfaces de rede`{.action} (1), clique no botão `...`{.action} (2) À direita de "Modo" no quadro **OLA: OVHcloud Link Aggregation**. A seguir, clique em `Configurar a agregação privada`{.action} (2).
+Serão apresentadas duas tabelas:
+- À esquerda, a configuração atual das suas interfaces de rede;
+- À direita, a configuração simulada das suas interfaces de rede agregadas.
-{.thumbnail}
+No campo abaixo das tabelas, introduza um nome para a sua agregação de ligações.
-Verifique que as suas duas interfaces, ou grupos de interfaces, são bem selecionados e dê um nome à interface OLA. Clique em `Confirmar`{.action} depois de as suas verificações estarem terminadas.
+Depois de verificar que a configuração da agregação corresponde aos seus requisitos de rede, clique em `Ativar a agregação`{.action} para continuar.
A operação pode demorar alguns minutos até ficar concluída. O próximo passo consistirá em configurar as interfaces do seu sistema operativo como NIC bond ou NIC team. Para ficar a conhecer o procedimento, consulte os nossos manuais relativos aos sistemas operativos mais populares:
-[Como configurar a NIC para o OVHcloud Link Aggregation em Debian 9 através do ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+- [Como configurar a NIC para o OVHcloud Link Aggregation em Debian 9 através do ifupdown](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+- [Como configurar a NIC para o OVHcloud Link Aggregation em Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+- [Como configurar a NIC para o OVHcloud Link Aggregation em SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+- [How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan).
-[Como configurar a NIC para o OVHcloud Link Aggregation em Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
+### Verificar o estado do OLA
-[Como configurar a NIC para o OVHcloud Link Aggregation em SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
+Pode verificar o estado da sua agregação de ligações (OLA) no separador `Interfaces de rede`{.action}. Na parte inferior da secção **Largura de banda**, localize a linha **OVHcloud Link Aggregation**.
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+Existem quatro etiquetas de estado possíveis:
+- **Indisponível**: O OLA não é suportado neste modelo de servidor dedicado.
+- **Disponível**: O OLA é suportado, mas não está configurado.
+- **Ativo - Totalmente privado**: O OLA está ativado; todas as interfaces físicas estão agregadas numa única ligação privada para uso de vRack.
+- **Ativo - LAG duplo**: O OLA está pré-ativado; as interfaces físicas estão divididas em dois agregados separados (um público, um privado).
-### Restaurar OLA aos valores predefinidos
+> [!primary]
+> **Nota:** O estado **Ativo - LAG duplo** é uma configuração específica geralmente reservada para as gamas de servidores Scale e High-Grade, que dispõem de quatro interfaces de rede físicas.
+>
-Para restaurar OLA aos valores predefinidos, clique no botão `...`{.action} à direita de "Modo" no quadro **OLA: OVHcloud Link Aggregation**. A seguir, clique em `Desconfigurar a agregação privada`{.action}. Clique em `Confirmar`{.action} no menu contextual.
+### Restaurar OLA aos valores predefinidos
-{.thumbnail}
+Para restaurar OLA aos valores predefinidos, clique no botão `Desagregar as redes`{.action} na secção **Controladores de interfaces de rede (NIC)**. Clique em `Confirmar`{.action} no menu contextual.
A operação pode demorar alguns minutos.
@@ -74,6 +85,6 @@ A operação pode demorar alguns minutos.
[Como configurar a NIC para o OVHcloud Link Aggregation em SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-[How to configure Your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
Fale com nossa [comunidade de utilizadores](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.de-de.md
index 3a8089d88ef..ec4dc198fbd 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.de-de.md
@@ -1,23 +1,38 @@
---
-title: "Konfigurieren der OVHcloud Link Aggregation in SLES 15"
-excerpt: "Erfahren Sie hier, wie Sie OLA für Ihren SLES 15 Server aktivieren"
-updated: 2024-11-26
+title: "Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in SLES 15"
+excerpt: "Link Aggregation auf Ihrem SLES-15-Server aktivieren, um die Verfügbarkeit Ihres Servers zu erhöhen und die Effizienz Ihrer Netzwerkverbindungen zu steigern"
+updated: 2026-04-20
---
+
+
## Ziel
-Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die Verfügbarkeit Ihres Servers zu erhöhen und die Effizienz Ihrer Netzwerkverbindungen zu steigern. Mit nur wenigen Klicks können Sie Ihre Netzwerkkarten aggregieren und Ihre Netzwerkverbindungen redundant machen. Wenn also eine Verbindung ausfällt, wird der Datenverkehr automatisch auf eine andere verfügbare Verbindung umgeleitet.
+Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die Verfügbarkeit Ihres Servers zu erhöhen und die Effizienz Ihrer Netzwerkverbindungen zu steigern. Mit nur wenigen Klicks können Sie Ihre Netzwerkkarten aggregieren und Ihre Netzwerkverbindungen redundant machen. Wenn also eine Verbindung ausfällt, wird der Datenverkehr automatisch auf eine andere verfügbare Verbindung umgeleitet. Die verfügbare Bandbreite wird durch Aggregation ebenfalls verdoppelt.
+Die Aggregation basiert auf dem Standard IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Diese Anleitung erklärt, wie Sie Ihre NICs (Network Interface Controller) zusammenfassen, um sie mit OLA in SLES 15 zu verwenden.**
+**Diese Anleitung erklärt, wie Sie Ihre Schnittstellen zur Verwendung mit OLA in SLES 15 zusammenfassen.**
## Voraussetzungen
-- Sie haben Ihre [Netzwerkkarte für die OVHcloud Link Aggregation im OVHcloud Kundencenter konfiguriert](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [OVHcloud Link Aggregation im OVHcloud Kundencenter konfigurieren](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
-### Zugang zum OVHcloud Kundencenter
+### Zugriff auf das OVHcloud Kundencenter
- **Direktlink:** [Dedicated Server](/links/control-panel/baremetal-dedicated-servers)
- **Navigationspfad:** `Bare Metal Cloud`{.action} > `Dedicated Server`{.action} > Wählen Sie Ihren Server aus
@@ -27,121 +42,301 @@ Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die V
## In der praktischen Anwendung
-Da die NICs in OLA privat-zu-privat konfiguriert sind, ist es nicht möglich, sich via SSH mit dem Server zu verbinden. Verwenden Sie daher das IPMI-Tool, um auf den Server zuzugreifen.
+Da wir für unsere NICs in OLA eine privat-private Konfiguration haben, können wir keine SSH-Verbindung zum Server herstellen. Daher müssen wir das IPMI-Tool nutzen, um auf den Server zuzugreifen.
Klicken Sie anschließend auf den Tab `IPMI`{.action} (1) und dann auf den Button `Mit einem Java-Applet (KVM)`{.action} (2).
{.thumbnail}
-Ein JNLP-Applet wird heruntergeladen. Öffnen Sie es, um IPMI aufzurufen. Melden Sie sich mit gültigen Anmeldedaten für den Server an.
+Ein JNLP-Applet wird heruntergeladen. Öffnen Sie es, um auf IPMI zuzugreifen. Melden Sie sich mit den dem Server zugeordneten Zugangsdaten an.
-Bei Verwendung eines OVHcloud Templates werden die NICs standardmäßig mit *eth0* und *eth1* gekennzeichnet. Wenn Sie kein OVHcloud Template verwenden, können Sie die Namen Ihrer Schnittstellen mit dem folgenden Befehl ermitteln:
+Standardmäßig werden die NICs bei Verwendung einer OVHcloud Vorlage als *eth0* und *eth1* bezeichnet. Wenn Sie keine OVHcloud Vorlage verwenden, können Sie die Namen Ihrer Schnittstellen mit folgendem Befehl ermitteln:
```bash
ip a
```
> [!primary]
->
-> Mit diesem Befehl werden mehrere Interfaces ausgegeben. Wenn Sie Schwierigkeiten haben, die physischen NICs zu bestimmen: Die öffentliche IP-Adresse des Servers wird standardmäßig der ersten Schnittstelle zugeordnet.
+> Die in den Konfigurationen und Beispielen unten angezeigten Werte (MAC-Adressen, IP-Adressen usw.) dienen nur als Beispiele. Sie müssen diese Werte natürlich durch Ihre eigenen ersetzen.
>
-Sobald die Namen Ihrer beiden Netzwerkkarten identifiziert sind, erstellen Sie die Netzwerkkartenbindung im Betriebssystem. Dazu muss ein *bond interface* konfiguriert werden. Erstellen Sie die Schnittstellendatei mit dem folgenden Befehl in einem Texteditor Ihrer Wahl:
+### Ermittlung der MAC-Adressen
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Melden Sie sich im [OVHcloud Kundencenter](/links/manager) an, wechseln Sie zum Bereich `Bare Metal Cloud`{.action} und wählen Sie Ihren Server unter **Dedicated Server** aus.
-Damit wird eine leere Textdatei geöffnet. Um die Aggregationsschnittstelle zu konfigurieren, fügen Sie folgende Zeilen in die Textdatei ein:
+Wechseln Sie zum Tab `Netzwerkinterfaces`{.action} und notieren Sie die MAC-Adressen für jede Schnittstelle (öffentlich/privat), die am unteren Ende des Menüs angezeigt werden.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Bitte beachten Sie, dass die MAC-Adresse der **öffentlichen Hauptschnittstelle** diejenige ist, die DHCP-Angebote empfängt, sowohl im Betriebssystem des Servers als auch im Rescue-Modus. Diese Schnittstelle verwaltet die öffentliche Konnektivität in der Standardkonfiguration.
>
-> Sie können jede gewünschte IP-Adresse privater Subnetze verwenden.
-> Wenn Ihr Server über mehr als 2 Netzwerkschnittstellen verfügt, können Sie diese in die Konfiguration hinzufügen, indem Sie die Nummer des Parameters `BONDING_SLAVE_` erhöhen, zum Beispiel: `BONDING_SLAVE_2= eth3`.
+> Außerdem ist die MAC-Adresse der **privaten Hauptschnittstelle** diejenige mit dem niedrigsten Wert. Im obigen Beispielbild ist dies die Adresse `a1:b2:c3:d4:e5:d6`.
>
-Speichern und schließen Sie die Datei, sobald Sie bestätigt haben, dass die Informationen korrekt sind. Sie müssen nun beide physischen Interfaces konfigurieren. Standardmäßig existiert auf einem OVHcloud Server nur für *eth0* eine Konfigurationsdatei. Öffnen Sie ihn mit folgendem Befehl:
+Nun, da Sie wissen, welche MAC-Adressen den einzelnen Schnittstellentypen (öffentlich/privat) zugeordnet sind, müssen Sie die Interface-Namen ermitteln.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-Standardmäßig wird die Datei folgenden Text anzeigen:
-
-```bash
-# Created by cloud-init on instance boot automatically, do not edit.
-#
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Ermittlung der Interface-Namen
-> [!warning]
+> [!primary]
>
-> Die IP-Adressen sind für jeden Server verschieden.
+> Wenn Sie die Netzwerkverbindung zu Ihrem Server verlieren, folgen Sie den Schritten unter "**KVM öffnen**" in [dieser Anleitung](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Bearbeiten Sie den Dateiinhalt folgendermaßen:
+Führen Sie den folgenden Befehl aus, um die Interface-Namen abzurufen:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> Die Hardware-Adresse (MAC-Adresse) der NIC kann mit dem zuvor verwendeten Befehl `ip a` gefunden werden. Es handelt sich um den Wert neben `link/ether` in der Ausgabe.
+> Dieser Befehl zeigt mehrere Interfaces an. Wenn Sie Schwierigkeiten haben, Ihre physischen Interfaces zu identifizieren, ist an der ersten Schnittstelle standardmäßig die öffentliche IP-Adresse des Servers angehängt.
>
-Ein *#* vor einer Zeile bedeutet, dass der Server diese Zeile beim Lesen der Datei überspringt. Ignorieren Sie daher diese Zeilen bei der Erstellung der Schnittstellendatei für *eth1*.
-
-Erstellen Sie die Konfigurationsdatei für *eth1* mit folgendem Befehl:
-
-```bash
-vi /etc/sysconfig/network/ifcfg-eth1
+Hier ein Beispiel der Ausgabe:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-Diese Datei ist leer. Fügen Sie folgenden Inhalt hinzu:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Um den Vorgang abzuschließen, starten Sie den Netzwerkdienst mit folgendem Befehl neu:
+Sobald Sie die Namen Ihrer Interfaces ermittelt haben, können Sie die Interface-Aggregation im Betriebssystem konfigurieren.
+
+### Konfiguration der Interface-Aggregation
+
+Wählen Sie den unten stehenden Tab entsprechend Ihrer Server-Konfiguration:
+
+- **Zwei Interfaces**: Advance-Server mit zwei physischen NICs.
+- **Vier Interfaces - Double LAG**: Scale- und High-Grade-Server mit OLA im Modus **Active - Double LAG** (öffentliche + private Aggregate). Dies erfordert die [Aktivierung von OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) im OVHcloud Kundencenter.
+- **Vier Interfaces - Fully Private**: Scale- und High-Grade-Server mit OLA im Modus **Active - Fully Private** (einzelnes privates Aggregat für vRack). Dies erfordert die [Aktivierung von OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) im OVHcloud Kundencenter.
+
+> [!tabs]
+> Zwei Interfaces
+>> Erstellen Sie die Konfigurationsdatei des Aggregats `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Statische IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Konfigurieren Sie dann jede physische Schnittstelle. Bearbeiten Sie `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Erstellen Sie `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Die Konfigurationsdateien der physischen Schnittstellen bleiben wie oben angegeben.
+>>
+>> ///
+>>
+> Vier Interfaces - Double LAG
+>> Diese Konfiguration aggregiert öffentliche Interfaces in `bond0` (mit öffentlicher IP) und private Interfaces in `bond1` (für vRack).
+>>
+>> Erstellen Sie die Konfigurationsdatei des öffentlichen Aggregats `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Statische IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Erstellen Sie die Konfigurationsdatei des privaten Aggregats `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Konfigurieren Sie dann jede physische Schnittstelle. Bearbeiten Sie `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Erstellen Sie `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Erstellen Sie `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Erstellen Sie `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (nur bond0)
+>>
+>> Verwenden Sie DHCP für das öffentliche Aggregat:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Das private Aggregat (`ifcfg-bond1`) und alle Konfigurationsdateien der physischen Schnittstellen bleiben wie oben angegeben.
+>>
+>> ///
+>>
+> Vier Interfaces - Fully Private
+>> Diese Konfiguration aggregiert alle physischen Interfaces in einem einzigen Aggregat ausschließlich für den vRack-Einsatz. Es gibt keine öffentliche IP-Konnektivität.
+>>
+>> > [!warning]
+>> >
+>> > Nach der Implementierung von OLA im Fully-Private-Modus ist die öffentliche IP nicht mehr erreichbar. Stellen Sie sicher, dass Sie über einen alternativen Zugangsweg verfügen (z. B. über einen anderen Server im vRack oder via KVM/IPMI), bevor Sie diese Konfiguration anwenden.
+>> >
+>>
+>> Erstellen Sie die Konfigurationsdatei des Aggregats `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Konfigurieren Sie dann jede physische Schnittstelle. Bearbeiten Sie `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Erstellen Sie `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Erstellen Sie `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Erstellen Sie `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > Im Fully-Private-Modus verwendet das Aggregat die MAC-Adresse der **privaten Hauptschnittstelle**. Das Feld `IPADDR` sollte auf Ihre private vRack-IP gesetzt werden.
+>> >
+
+### Anwenden der Konfiguration
+
+Wenden Sie die Konfiguration an, indem Sie alle Interfaces mit wicked neu laden:
```bash
wicked ifreload all
```
-Um zu überprüfen, ob diese Aggregation funktioniert, pingen Sie einen anderen Server im gleichen vRack. Wenn das funktioniert, ist der Konfigurationsprozess abgeschlossen. Ist das nicht der Fall, überprüfen Sie Ihre Konfigurationen oder starten Sie den Server neu.
+Dieser Vorgang kann einige Sekunden dauern, da die Bond-Schnittstelle erstellt wird. Um zu testen, ob das Aggregat funktioniert, senden Sie einen Ping an einen anderen Server im selben vRack. Wenn es funktioniert, sind Sie fertig. Wenn nicht, überprüfen Sie Ihre Konfigurationen oder versuchen Sie, den Server neu zu starten.
-Sie können die über das Interface `ifcfg-bond0` verwendeten Einstellungen auch mit folgendem Befehl überprüfen:
+Sie können die Aggregat-Einstellungen auch mit folgendem Befehl überprüfen:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Weiterführende Informationen
-[Konfiguration der OVHcloud Link Aggregation in Ihrem Kundencenter](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[OVHcloud Link Aggregation im OVHcloud Kundencenter konfigurieren](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 12 oder Ubuntu 24.04 mit Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 9 bis 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
-Treten Sie unserer [User Community](/links/community) bei.
\ No newline at end of file
+Treten Sie unserer [User Community](/links/community) bei.
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-asia.md
index 55b484aeb21..4f8cb405d32 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-asia.md
@@ -1,14 +1,29 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15
-excerpt: Enable OVHcloud Link Aggregation in your SLES 15 server
-updated: 2024-11-26
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15"
+excerpt: "Enable Link Aggregation in your SLES 15 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-The OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, the traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in SLES 15.**
+**This guide explains how to bond your interfaces to use them for OLA in SLES 15.**
## Requirements
@@ -28,8 +43,9 @@ The OVHcloud Link Aggregation (OLA) technology is designed by our teams to incre
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+Click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -42,104 +58,286 @@ ip a
```
> [!primary]
->
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
>
-Once you have determined the names of your two NICs, you need to configure NIC bonding in the OS. The first step is to create a bond interface. To do so, create the following configuration file in a text editor of your choice:
+### Retrieving MAC addresses
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
-This will open an empty text file. To configure the bond interface, insert the following into the text file:
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> You can use any private IP address and subnet you wish.
-> If your server has more than 2 network interfaces, you can add them in the configuration, by incrementing the number of the `BONDING_SLAVE_` parameter, for example, `BONDING_SLAVE_2='eth2'`.
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-Save and exit the file once you have confirmed that the information is correct. Next, you need to configure both physical interfaces. By default, on an OVHcloud server, only *eth0* will have a configuration file. Open it using the following command:
+Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interface names.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-By default, the file will appear as follows:
-
-```bash
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Retrieving interface names
-> [!warning]
+> [!primary]
>
-> The IP addresses will be different for each server.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Edit the file to make it appear as follows:
+To retrieve the names of the interfaces, execute the following command:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> The hardware address (MAC address) of the NIC can be found using the `ip a` command that you used earlier. It will be the number next to `link/ether` in the output.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-The *#* in front of a line means that the server will ignore this line when reading the file. Thus, please ignore these lines entirely when creating your interface file for *eth0*.
-
-Create the *eth1* configuration file using the following command:
-
-```bash
-vi /etc/sysconfig/network-scripts/ifcfg-eth2
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-This time, the file will be blank so add the following content to the file:
-
-```bash
-BOOTPROTO='none'
-STARTMODUS= hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Finally, restart the network daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interface bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Create the public bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Create the private bond configuration file `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 only)
+>>
+>> For the public bond, use DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The private bond (`ifcfg-bond1`) and all physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `IPADDR` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by reloading all interfaces with wicked:
```bash
wicked ifreload all
```
-To test that your bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
+This may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
-You can also check the used parameters by your ifcfg-bond0 interface using the following command:
+You can also verify the bonding parameters using the following command:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-au.md
index 1ff919838ff..4f8cb405d32 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-au.md
@@ -1,14 +1,29 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15
-excerpt: Enable OVHcloud Link Aggregation in your SLES 15 server
-updated: 2024-11-26
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15"
+excerpt: "Enable Link Aggregation in your SLES 15 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-The OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, the traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in SLES 15.**
+**This guide explains how to bond your interfaces to use them for OLA in SLES 15.**
## Requirements
@@ -28,8 +43,9 @@ The OVHcloud Link Aggregation (OLA) technology is designed by our teams to incre
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+Click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -42,104 +58,286 @@ ip a
```
> [!primary]
->
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
>
-Once you have determined the names of your two NICs, you need to configure NIC bonding in the OS. The first step is to create a bond interface. To do so, create the following configuration file in a text editor of your choice:
+### Retrieving MAC addresses
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
-This will open an empty text file. To configure the bond interface, insert the following into the text file:
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> You can use any private IP address and subnet you wish.
-> If your server has more than 2 network interfaces, you can add them in the configuration, by incrementing the number of the `BONDING_SLAVE_` parameter, for example, `BONDING_SLAVE_2='eth2'`.
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-Save and exit the file once you have confirmed that the information is correct. Next, you need to configure both physical interfaces. By default, on an OVHcloud server, only *eth0* will have a configuration file. Open it using the following command:
+Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interface names.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-By default, the file will appear as follows:
-
-```bash
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Retrieving interface names
-> [!warning]
+> [!primary]
>
-> The IP addresses will be different for each server.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Edit the file to make it appear as follows:
+To retrieve the names of the interfaces, execute the following command:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> The hardware address (MAC address) of the NIC can be found using the `ip a` command that you used earlier. It will be the number next to `link/ether` in the output.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-The *#* in front of a line means that the server will ignore this line when reading the file. Thus, please ignore these lines entirely when creating your interface file for *eth0*.
-
-Create the *eth1* configuration file using the following command:
-
-```bash
-vi /etc/sysconfig/network-scripts/ifcfg-eth2
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-This time, the file will be blank so add the following content to the file:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Finally, restart the network daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interface bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Create the public bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Create the private bond configuration file `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 only)
+>>
+>> For the public bond, use DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The private bond (`ifcfg-bond1`) and all physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `IPADDR` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by reloading all interfaces with wicked:
```bash
wicked ifreload all
```
-To test that your bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
+This may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
-You can also check the used parameters by your ifcfg-bond0 interface using the following command:
+You can also verify the bonding parameters using the following command:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-ca.md
index 1ff919838ff..4f8cb405d32 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-ca.md
@@ -1,14 +1,29 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15
-excerpt: Enable OVHcloud Link Aggregation in your SLES 15 server
-updated: 2024-11-26
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15"
+excerpt: "Enable Link Aggregation in your SLES 15 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-The OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, the traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in SLES 15.**
+**This guide explains how to bond your interfaces to use them for OLA in SLES 15.**
## Requirements
@@ -28,8 +43,9 @@ The OVHcloud Link Aggregation (OLA) technology is designed by our teams to incre
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+Click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -42,104 +58,286 @@ ip a
```
> [!primary]
->
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
>
-Once you have determined the names of your two NICs, you need to configure NIC bonding in the OS. The first step is to create a bond interface. To do so, create the following configuration file in a text editor of your choice:
+### Retrieving MAC addresses
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
-This will open an empty text file. To configure the bond interface, insert the following into the text file:
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> You can use any private IP address and subnet you wish.
-> If your server has more than 2 network interfaces, you can add them in the configuration, by incrementing the number of the `BONDING_SLAVE_` parameter, for example, `BONDING_SLAVE_2='eth2'`.
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-Save and exit the file once you have confirmed that the information is correct. Next, you need to configure both physical interfaces. By default, on an OVHcloud server, only *eth0* will have a configuration file. Open it using the following command:
+Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interface names.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-By default, the file will appear as follows:
-
-```bash
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Retrieving interface names
-> [!warning]
+> [!primary]
>
-> The IP addresses will be different for each server.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Edit the file to make it appear as follows:
+To retrieve the names of the interfaces, execute the following command:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> The hardware address (MAC address) of the NIC can be found using the `ip a` command that you used earlier. It will be the number next to `link/ether` in the output.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-The *#* in front of a line means that the server will ignore this line when reading the file. Thus, please ignore these lines entirely when creating your interface file for *eth0*.
-
-Create the *eth1* configuration file using the following command:
-
-```bash
-vi /etc/sysconfig/network-scripts/ifcfg-eth2
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-This time, the file will be blank so add the following content to the file:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Finally, restart the network daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interface bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Create the public bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Create the private bond configuration file `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 only)
+>>
+>> For the public bond, use DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The private bond (`ifcfg-bond1`) and all physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `IPADDR` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by reloading all interfaces with wicked:
```bash
wicked ifreload all
```
-To test that your bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
+This may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
-You can also check the used parameters by your ifcfg-bond0 interface using the following command:
+You can also verify the bonding parameters using the following command:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-gb.md
index 9db342232bf..4f8cb405d32 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-gb.md
@@ -1,14 +1,29 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15
-excerpt: Enable OVHcloud Link Aggregation in your SLES 15 server
-updated: 2024-11-26
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15"
+excerpt: "Enable Link Aggregation in your SLES 15 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-The OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, the traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in SLES 15.**
+**This guide explains how to bond your interfaces to use them for OLA in SLES 15.**
## Requirements
@@ -28,7 +43,7 @@ The OVHcloud Link Aggregation (OLA) technology is designed by our teams to incre
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
-
Click the `IPMI`{.action} tab (1).
+Click the `IPMI`{.action} tab (1).
Next, click the `From a Java applet (KVM)`{.action} button (2).
@@ -43,104 +58,286 @@ ip a
```
> [!primary]
->
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
>
-Once you have determined the names of your two NICs, you need to configure NIC bonding in the OS. The first step is to create a bond interface. To do so, create the following configuration file in a text editor of your choice:
+### Retrieving MAC addresses
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
-This will open an empty text file. To configure the bond interface, insert the following into the text file:
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> You can use any private IP address and subnet you wish.
-> If your server has more than 2 network interfaces, you can add them in the configuration, by incrementing the number of the `BONDING_SLAVE_` parameter, for example, `BONDING_SLAVE_2='eth2'`.
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-Save and exit the file once you have confirmed that the information is correct. Next, you need to configure both physical interfaces. By default, on an OVHcloud server, only *eth0* will have a configuration file. Open it using the following command:
+Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interface names.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-By default, the file will appear as follows:
-
-```bash
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Retrieving interface names
-> [!warning]
+> [!primary]
>
-> The IP addresses will be different for each server.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Edit the file to make it appear as follows:
+To retrieve the names of the interfaces, execute the following command:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> The hardware address (MAC address) of the NIC can be found using the `ip a` command that you used earlier. It will be the number next to `link/ether` in the output.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-The *#* in front of a line means that the server will ignore this line when reading the file. Thus, please ignore these lines entirely when creating your interface file for *eth0*.
-
-Create the *eth1* configuration file using the following command:
-
-```bash
-vi /etc/sysconfig/network-scripts/ifcfg-eth2
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-This time, the file will be blank so add the following content to the file:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Finally, restart the network daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interface bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Create the public bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Create the private bond configuration file `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 only)
+>>
+>> For the public bond, use DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The private bond (`ifcfg-bond1`) and all physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `IPADDR` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by reloading all interfaces with wicked:
```bash
wicked ifreload all
```
-To test that your bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
+This may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
-You can also check the used parameters by your ifcfg-bond0 interface using the following command:
+You can also verify the bonding parameters using the following command:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-ie.md
index 1ff919838ff..4f8cb405d32 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-ie.md
@@ -1,14 +1,29 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15
-excerpt: Enable OVHcloud Link Aggregation in your SLES 15 server
-updated: 2024-11-26
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15"
+excerpt: "Enable Link Aggregation in your SLES 15 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-The OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, the traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in SLES 15.**
+**This guide explains how to bond your interfaces to use them for OLA in SLES 15.**
## Requirements
@@ -28,8 +43,9 @@ The OVHcloud Link Aggregation (OLA) technology is designed by our teams to incre
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+Click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -42,104 +58,286 @@ ip a
```
> [!primary]
->
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
>
-Once you have determined the names of your two NICs, you need to configure NIC bonding in the OS. The first step is to create a bond interface. To do so, create the following configuration file in a text editor of your choice:
+### Retrieving MAC addresses
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
-This will open an empty text file. To configure the bond interface, insert the following into the text file:
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> You can use any private IP address and subnet you wish.
-> If your server has more than 2 network interfaces, you can add them in the configuration, by incrementing the number of the `BONDING_SLAVE_` parameter, for example, `BONDING_SLAVE_2='eth2'`.
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-Save and exit the file once you have confirmed that the information is correct. Next, you need to configure both physical interfaces. By default, on an OVHcloud server, only *eth0* will have a configuration file. Open it using the following command:
+Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interface names.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-By default, the file will appear as follows:
-
-```bash
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Retrieving interface names
-> [!warning]
+> [!primary]
>
-> The IP addresses will be different for each server.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Edit the file to make it appear as follows:
+To retrieve the names of the interfaces, execute the following command:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> The hardware address (MAC address) of the NIC can be found using the `ip a` command that you used earlier. It will be the number next to `link/ether` in the output.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-The *#* in front of a line means that the server will ignore this line when reading the file. Thus, please ignore these lines entirely when creating your interface file for *eth0*.
-
-Create the *eth1* configuration file using the following command:
-
-```bash
-vi /etc/sysconfig/network-scripts/ifcfg-eth2
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-This time, the file will be blank so add the following content to the file:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Finally, restart the network daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interface bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Create the public bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Create the private bond configuration file `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 only)
+>>
+>> For the public bond, use DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The private bond (`ifcfg-bond1`) and all physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `IPADDR` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by reloading all interfaces with wicked:
```bash
wicked ifreload all
```
-To test that your bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
+This may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
-You can also check the used parameters by your ifcfg-bond0 interface using the following command:
+You can also verify the bonding parameters using the following command:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-sg.md
index 1ff919838ff..4f8cb405d32 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-sg.md
@@ -1,14 +1,29 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15
-excerpt: Enable OVHcloud Link Aggregation in your SLES 15 server
-updated: 2024-11-26
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15"
+excerpt: "Enable Link Aggregation in your SLES 15 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-The OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, the traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in SLES 15.**
+**This guide explains how to bond your interfaces to use them for OLA in SLES 15.**
## Requirements
@@ -28,8 +43,9 @@ The OVHcloud Link Aggregation (OLA) technology is designed by our teams to incre
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+Click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -42,104 +58,286 @@ ip a
```
> [!primary]
->
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
>
-Once you have determined the names of your two NICs, you need to configure NIC bonding in the OS. The first step is to create a bond interface. To do so, create the following configuration file in a text editor of your choice:
+### Retrieving MAC addresses
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
-This will open an empty text file. To configure the bond interface, insert the following into the text file:
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> You can use any private IP address and subnet you wish.
-> If your server has more than 2 network interfaces, you can add them in the configuration, by incrementing the number of the `BONDING_SLAVE_` parameter, for example, `BONDING_SLAVE_2='eth2'`.
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-Save and exit the file once you have confirmed that the information is correct. Next, you need to configure both physical interfaces. By default, on an OVHcloud server, only *eth0* will have a configuration file. Open it using the following command:
+Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interface names.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-By default, the file will appear as follows:
-
-```bash
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Retrieving interface names
-> [!warning]
+> [!primary]
>
-> The IP addresses will be different for each server.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Edit the file to make it appear as follows:
+To retrieve the names of the interfaces, execute the following command:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> The hardware address (MAC address) of the NIC can be found using the `ip a` command that you used earlier. It will be the number next to `link/ether` in the output.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-The *#* in front of a line means that the server will ignore this line when reading the file. Thus, please ignore these lines entirely when creating your interface file for *eth0*.
-
-Create the *eth1* configuration file using the following command:
-
-```bash
-vi /etc/sysconfig/network-scripts/ifcfg-eth2
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-This time, the file will be blank so add the following content to the file:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Finally, restart the network daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interface bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Create the public bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Create the private bond configuration file `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 only)
+>>
+>> For the public bond, use DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The private bond (`ifcfg-bond1`) and all physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `IPADDR` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by reloading all interfaces with wicked:
```bash
wicked ifreload all
```
-To test that your bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
+This may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
-You can also check the used parameters by your ifcfg-bond0 interface using the following command:
+You can also verify the bonding parameters using the following command:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-us.md
index 1ff919838ff..4f8cb405d32 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.en-us.md
@@ -1,14 +1,29 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15
-excerpt: Enable OVHcloud Link Aggregation in your SLES 15 server
-updated: 2024-11-26
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15"
+excerpt: "Enable Link Aggregation in your SLES 15 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
+
+
## Objective
-The OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, the traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
-**This guide explains how to bond your NICs to use them for OLA in SLES 15.**
+**This guide explains how to bond your interfaces to use them for OLA in SLES 15.**
## Requirements
@@ -28,8 +43,9 @@ The OVHcloud Link Aggregation (OLA) technology is designed by our teams to incre
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+Click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -42,104 +58,286 @@ ip a
```
> [!primary]
->
-> This command will yield numerous "interfaces." If you are having trouble determining which ones are your physical NICs, the first interface will still have the server's public IP address attached to it by default.
+> The values (MAC addresses, IP addresses, etc.) shown in the configurations and examples below are provided as examples. Of course, you must replace these values with your own.
>
-Once you have determined the names of your two NICs, you need to configure NIC bonding in the OS. The first step is to create a bond interface. To do so, create the following configuration file in a text editor of your choice:
+### Retrieving MAC addresses
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from **Dedicated Servers**.
-This will open an empty text file. To configure the bond interface, insert the following into the text file:
+Switch to the tab `Network Interfaces`{.action} and take note of the MAC addresses for each interface (public/private) which are displayed at the bottom of the menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Please note that the MAC address of the **main public** interface is the one receiving DHCP offers, both in the server's operating system and in rescue mode. This interface handles public connectivity in the default configuration.
>
-> You can use any private IP address and subnet you wish.
-> If your server has more than 2 network interfaces, you can add them in the configuration, by incrementing the number of the `BONDING_SLAVE_` parameter, for example, `BONDING_SLAVE_2='eth2'`.
+> Additionally, the MAC address of the **main private** interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:d6`.
>
-Save and exit the file once you have confirmed that the information is correct. Next, you need to configure both physical interfaces. By default, on an OVHcloud server, only *eth0* will have a configuration file. Open it using the following command:
+Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interface names.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-By default, the file will appear as follows:
-
-```bash
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Retrieving interface names
-> [!warning]
+> [!primary]
>
-> The IP addresses will be different for each server.
+> If you lose network connection to your server, follow the "**Open KVM**" steps from [this guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Edit the file to make it appear as follows:
+To retrieve the names of the interfaces, execute the following command:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> The hardware address (MAC address) of the NIC can be found using the `ip a` command that you used earlier. It will be the number next to `link/ether` in the output.
+> This command will yield numerous interfaces. If you are having trouble determining which ones are your physical interfaces, the first interface will still have the server's public IP address attached to it by default.
>
-The *#* in front of a line means that the server will ignore this line when reading the file. Thus, please ignore these lines entirely when creating your interface file for *eth0*.
-
-Create the *eth1* configuration file using the following command:
-
-```bash
-vi /etc/sysconfig/network-scripts/ifcfg-eth2
+Here's an output example:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-This time, the file will be blank so add the following content to the file:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Finally, restart the network daemon using the following command:
+Once you have determined the names of your interfaces, you can configure interface bonding in the OS.
+
+### Configuring interface bonding
+
+Select the tab below that matches your server configuration:
+
+- **Two interfaces**: Advance servers with two physical NICs.
+- **Four interfaces - Double LAG**: Scale and High-Grade servers with OLA in **Active - Double LAG** mode (public + private aggregates). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+- **Four interfaces - Fully Private**: Scale and High-Grade servers with OLA in **Active - Fully Private** mode (single private aggregate for vRack). This requires [OLA to be enabled](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) in the OVHcloud Control Panel.
+
+> [!tabs]
+> Two interfaces
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Double LAG
+>> This configuration bonds public interfaces into `bond0` (with public IP) and private interfaces into `bond1` (for vRack).
+>>
+>> Create the public bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Static IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Create the private bond configuration file `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 only)
+>>
+>> For the public bond, use DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> The private bond (`ifcfg-bond1`) and all physical interface configuration files remain the same as above.
+>>
+>> ///
+>>
+> Four interfaces - Fully Private
+>> This configuration aggregates all physical interfaces into a single bond for vRack use only. There is no public IP connectivity.
+>>
+>> > [!warning]
+>> >
+>> > Following the implementation of OLA in Fully Private mode, the public IP is no longer accessible. Make sure you have an alternative means of access (e.g. through another server in the vRack, or via KVM/IPMI) before applying this configuration.
+>> >
+>>
+>> Create the bond configuration file `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Then configure each physical interface. Edit `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Create `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In Fully Private mode, the bond uses the MAC address of the **main private** interface. The `IPADDR` field should be set to your vRack private IP.
+>> >
+
+### Applying the configuration
+
+Apply the configuration by reloading all interfaces with wicked:
```bash
wicked ifreload all
```
-To test that your bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
+This may take several seconds since it is building the bond interface. To test that the bond is working, ping another server on the same vRack. If it works, you are all set. If it does not, double-check your configurations or try rebooting the server.
-You can also check the used parameters by your ifcfg-bond0 interface using the following command:
+You can also verify the bonding parameters using the following command:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.es-es.md
index a74ededd0f3..ea588ff9fac 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.es-es.md
@@ -1,18 +1,33 @@
---
-title: Cómo configurar el ID de cliente para la agrupación de enlaces OVHcloud en SLES 15
-excerpt: 'Activar OVHcloud Link Aggregation en su servidor SLES 15'
-updated: 2024-11-26
+title: "Cómo configurar la NIC para OVHcloud Link Aggregation en SLES 15"
+excerpt: "Active la agregación de enlaces en su servidor SLES 15 para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red"
+updated: 2026-04-20
---
+
+
## Objetivo
-La tecnología OVHcloud Link Aggregation (OLA) está diseñada por nuestros equipos para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, podrá agregar sus mapas de red y hacer redundantes sus conexiones de red. Esto significa que si un enlace se rompe, el tráfico se redirige automáticamente a otro enlace disponible.
+La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible. El ancho de banda disponible también se duplica gracias a la agregación.
+La agregación se basa en la tecnología IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Esta guía explica cómo agrupar sus NIC (Network Interface Controller) para utilizarlos con el servicio OLA en SLES 15.**
+**Esta guía explica cómo configurar sus interfaces en agregación para utilizarlas con OLA en SLES 15.**
## Requisitos
-- [Haber configurado su ID de cliente para la funcionalidad de OVHcloud Link Aggregation desde el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -27,121 +42,301 @@ La tecnología OVHcloud Link Aggregation (OLA) está diseñada por nuestros equi
## Procedimiento
-Debido a que OLA ofrece una configuración privado-privada para sus ID de cliente, no es posible conectarse al servidor por SSH. Por lo tanto, deberá utilizar la herramienta IPMI para acceder al servidor.
+Dado que nuestros NIC en OLA tienen una configuración privada-privada, no es posible acceder al servidor por SSH. Por lo tanto, es necesario utilizar la herramienta IPMI para acceder al servidor.
-A continuación, abra la pestaña `IPMI`{.action} (1) y haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
+Haga clic en la pestaña `IPMI`{.action} (1) y, a continuación, en el botón `Desde un applet Java (KVM)`{.action} (2).
{.thumbnail}
-Se descargará un programa JNLP. Lance el programa para acceder a IPMI. Conéctese utilizando las claves de acceso asociadas al servidor.
+Se descargará un programa JNLP. Lánce el programa para acceder a IPMI. Conéctese utilizando las credenciales asociadas al servidor.
-Por defecto, utilizando el modelo de OVHcloud, los ID de cliente se denominarán *eth0* y *eth1*. Si no utiliza un modelo de OVHcloud, puede encontrar los nombres de las interfaces utilizando el siguiente comando:
+Por defecto, al utilizar un modelo de OVHcloud, los NIC se denominarán *eth0* y *eth1*. Si no utiliza un modelo de OVHcloud, puede encontrar los nombres de las interfaces utilizando el siguiente comando:
```bash
ip a
```
> [!primary]
->
-> Este comando devolverá varias interfaces. Si tiene dificultades para identificar sus NIC físicas, la primera interfaz siempre tendrá la dirección IP pública del servidor asignado por defecto.
+> Los valores (direcciones MAC, direcciones IP, etc.) que aparecen en las configuraciones y ejemplos a continuación se proporcionan como ejemplos. Por supuesto, debe reemplazarlos por los suyos propios.
>
-Una vez que haya identificado los dos ID de cliente, deberá crear el NIC bonding o la agregación de los enlaces en el sistema operativo. Para ello, cree el archivo de interfaces en el editor de texto que desee utilizando el siguiente comando:
+### Obtención de las direcciones MAC
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Conéctese al [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione su servidor en **Servidores dedicados**.
-Esto abrirá un archivo de texto vacío. Para configurar la interfaz de agregación, inserte las siguientes líneas en el archivo de texto:
+Vaya a la pestaña `Interfaces de red`{.action} y tome nota de las direcciones MAC de cada interfaz (pública/privada) que se muestran en la parte inferior del menú.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Tenga en cuenta que la dirección MAC de la interfaz **pública principal** es la que recibe las ofertas DHCP, tanto en el sistema operativo del servidor como en el modo de rescate. Esta interfaz gestiona la conectividad pública en la configuración predeterminada.
>
-> Puede utilizar cualquier dirección IP o subred privada que desee.
-> Si su servidor tiene más de 2 interfaces de red, puede añadirlos en la configuración aumentando el número del parámetro `BONDING_SLAVE_`, por ejemplo `BONDING_SLAVE_2='eth2'`.
+> Además, la dirección MAC de la interfaz **privada principal** es la de menor valor. En la imagen de ejemplo anterior, esta es la dirección `a1:b2:c3:d4:e5:d6`.
>
-Guarde y cierre el archivo una vez que haya confirmado que la información es correcta. Ahora deberá configurar las dos interfaces físicas. Por defecto, para un servidor de OVHcloud, solo *eth0* tendrá un archivo de configuración. Abra con el siguiente comando:
+Una vez que sabe qué direcciones MAC están asociadas a cada tipo de interfaz (pública/privada), debe obtener los nombres de las interfaces.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-De forma predeterminada, el archivo mostrará el siguiente texto:
-
-```bash
-# Created by cloud-init on instance boot automatically, do not edit.
-#
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Obtención de los nombres de las interfaces
-> [!warning]
+> [!primary]
>
-> Las direcciones IP serán diferentes para cada servidor.
+> Si pierde la conexión de red con su servidor, siga los pasos de "**Abrir KVM**" de [esta guía](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Es necesario modificar el archivo para que muestre el siguiente texto:
+Para obtener los nombres de las interfaces, ejecute el siguiente comando:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> La dirección de hardware (dirección MAC) del ID de cliente se puede encontrar con el comando `ip utilizado anteriormente`. Este será el número al lado de `link/ether` del resultado mostrado.
+> Este comando mostrará diversas interfaces. Si tiene dificultad para determinar cuáles son sus interfaces físicas, la primera interfaz todavía tendrá la dirección IP pública del servidor asignada por defecto.
>
-El *#* delante de una línea indica que el servidor ignorará esta línea al leer el archivo. Esto significa que estas líneas no se tendrán en cuenta al crear el archivo de interfaz para *eth0*.
-
-Para crear el archivo de configuración *eth1*, utilice el siguiente comando:
-
-```bash
-vi /etc/sysconfig/network/ifcfg-eth1
+Aquí tiene un ejemplo de salida:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-Esta vez, el archivo estará vacío. Añada el siguiente contenido:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Por último, reinicie el servicio de red con el siguiente comando:
+Una vez que haya determinado los nombres de sus interfaces, puede configurar la agregación de interfaces en el sistema operativo.
+
+### Configuración de la agregación de interfaces
+
+Seleccione la pestaña siguiente que corresponda a la configuración de su servidor:
+
+- **Dos interfaces**: servidores Advance con dos NIC físicas.
+- **Cuatro interfaces - Double LAG**: servidores Scale y High-Grade con OLA en modo **Active - Double LAG** (agregados público + privado). Requiere [activar OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) en el área de cliente de OVHcloud.
+- **Cuatro interfaces - Fully Private**: servidores Scale y High-Grade con OLA en modo **Active - Fully Private** (único agregado privado para vRack). Requiere [activar OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) en el área de cliente de OVHcloud.
+
+> [!tabs]
+> Dos interfaces
+>> Cree el archivo de configuración del agregado `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **IP estática**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure a continuación cada interfaz física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Los archivos de configuración de las interfaces físicas permanecen igual que arriba.
+>>
+>> ///
+>>
+> Cuatro interfaces - Double LAG
+>> Esta configuración agrupa las interfaces públicas en `bond0` (con IP pública) y las interfaces privadas en `bond1` (para vRack).
+>>
+>> Cree el archivo de configuración del agregado público `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **IP estática**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Cree el archivo de configuración del agregado privado `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure a continuación cada interfaz física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (solo bond0)
+>>
+>> Para el agregado público, utilice DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> El agregado privado (`ifcfg-bond1`) y todos los archivos de configuración de las interfaces físicas permanecen igual que arriba.
+>>
+>> ///
+>>
+> Cuatro interfaces - Fully Private
+>> Esta configuración agrega todas las interfaces físicas en un único agregado exclusivamente para uso con vRack. No hay conectividad IP pública.
+>>
+>> > [!warning]
+>> >
+>> > Tras la implementación de OLA en modo Fully Private, la IP pública deja de estar accesible. Asegúrese de tener un medio alternativo de acceso (p. ej., a través de otro servidor en el vRack o mediante KVM/IPMI) antes de aplicar esta configuración.
+>> >
+>>
+>> Cree el archivo de configuración del agregado `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure a continuación cada interfaz física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > En modo Fully Private, el agregado utiliza la dirección MAC de la interfaz **privada principal**. El campo `IPADDR` debe configurarse con su IP privada de vRack.
+>> >
+
+### Aplicación de la configuración
+
+Aplique la configuración recargando todas las interfaces con wicked:
```bash
wicked ifreload all
```
-Para comprobar que la agregación funciona, realice un ping a otro servidor en el mismo vRack. Si funciona, el proceso de configuración se habrá completado. En caso contrario, compruebe su configuración o intente reiniciar el servidor.
+Este reinicio puede tardar unos segundos ya que se está creando la interfaz de agregado. Para comprobar que el agregado funciona correctamente, haga ping a otro servidor en el mismo vRack. Si funciona, está todo listo. En caso contrario, compruebe sus configuraciones o intente reiniciar el servidor.
-También puede comprobar los parámetros utilizados en su interfaz ifcfg-bond0 utilizando el siguiente comando:
+También puede comprobar la configuración del agregado con el siguiente comando:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Más información
-[Configurar la agregación de enlaces OLA en el área de cliente](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Cómo configurar el ID de cliente para la agrupación de enlaces OVHcloud en Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 9 a 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Cómo configurar el ID de cliente para la agrupación de enlaces OVHcloud en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.es-us.md
index a74ededd0f3..ea588ff9fac 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.es-us.md
@@ -1,18 +1,33 @@
---
-title: Cómo configurar el ID de cliente para la agrupación de enlaces OVHcloud en SLES 15
-excerpt: 'Activar OVHcloud Link Aggregation en su servidor SLES 15'
-updated: 2024-11-26
+title: "Cómo configurar la NIC para OVHcloud Link Aggregation en SLES 15"
+excerpt: "Active la agregación de enlaces en su servidor SLES 15 para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red"
+updated: 2026-04-20
---
+
+
## Objetivo
-La tecnología OVHcloud Link Aggregation (OLA) está diseñada por nuestros equipos para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, podrá agregar sus mapas de red y hacer redundantes sus conexiones de red. Esto significa que si un enlace se rompe, el tráfico se redirige automáticamente a otro enlace disponible.
+La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible. El ancho de banda disponible también se duplica gracias a la agregación.
+La agregación se basa en la tecnología IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Esta guía explica cómo agrupar sus NIC (Network Interface Controller) para utilizarlos con el servicio OLA en SLES 15.**
+**Esta guía explica cómo configurar sus interfaces en agregación para utilizarlas con OLA en SLES 15.**
## Requisitos
-- [Haber configurado su ID de cliente para la funcionalidad de OVHcloud Link Aggregation desde el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -27,121 +42,301 @@ La tecnología OVHcloud Link Aggregation (OLA) está diseñada por nuestros equi
## Procedimiento
-Debido a que OLA ofrece una configuración privado-privada para sus ID de cliente, no es posible conectarse al servidor por SSH. Por lo tanto, deberá utilizar la herramienta IPMI para acceder al servidor.
+Dado que nuestros NIC en OLA tienen una configuración privada-privada, no es posible acceder al servidor por SSH. Por lo tanto, es necesario utilizar la herramienta IPMI para acceder al servidor.
-A continuación, abra la pestaña `IPMI`{.action} (1) y haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
+Haga clic en la pestaña `IPMI`{.action} (1) y, a continuación, en el botón `Desde un applet Java (KVM)`{.action} (2).
{.thumbnail}
-Se descargará un programa JNLP. Lance el programa para acceder a IPMI. Conéctese utilizando las claves de acceso asociadas al servidor.
+Se descargará un programa JNLP. Lánce el programa para acceder a IPMI. Conéctese utilizando las credenciales asociadas al servidor.
-Por defecto, utilizando el modelo de OVHcloud, los ID de cliente se denominarán *eth0* y *eth1*. Si no utiliza un modelo de OVHcloud, puede encontrar los nombres de las interfaces utilizando el siguiente comando:
+Por defecto, al utilizar un modelo de OVHcloud, los NIC se denominarán *eth0* y *eth1*. Si no utiliza un modelo de OVHcloud, puede encontrar los nombres de las interfaces utilizando el siguiente comando:
```bash
ip a
```
> [!primary]
->
-> Este comando devolverá varias interfaces. Si tiene dificultades para identificar sus NIC físicas, la primera interfaz siempre tendrá la dirección IP pública del servidor asignado por defecto.
+> Los valores (direcciones MAC, direcciones IP, etc.) que aparecen en las configuraciones y ejemplos a continuación se proporcionan como ejemplos. Por supuesto, debe reemplazarlos por los suyos propios.
>
-Una vez que haya identificado los dos ID de cliente, deberá crear el NIC bonding o la agregación de los enlaces en el sistema operativo. Para ello, cree el archivo de interfaces en el editor de texto que desee utilizando el siguiente comando:
+### Obtención de las direcciones MAC
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Conéctese al [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione su servidor en **Servidores dedicados**.
-Esto abrirá un archivo de texto vacío. Para configurar la interfaz de agregación, inserte las siguientes líneas en el archivo de texto:
+Vaya a la pestaña `Interfaces de red`{.action} y tome nota de las direcciones MAC de cada interfaz (pública/privada) que se muestran en la parte inferior del menú.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Tenga en cuenta que la dirección MAC de la interfaz **pública principal** es la que recibe las ofertas DHCP, tanto en el sistema operativo del servidor como en el modo de rescate. Esta interfaz gestiona la conectividad pública en la configuración predeterminada.
>
-> Puede utilizar cualquier dirección IP o subred privada que desee.
-> Si su servidor tiene más de 2 interfaces de red, puede añadirlos en la configuración aumentando el número del parámetro `BONDING_SLAVE_`, por ejemplo `BONDING_SLAVE_2='eth2'`.
+> Además, la dirección MAC de la interfaz **privada principal** es la de menor valor. En la imagen de ejemplo anterior, esta es la dirección `a1:b2:c3:d4:e5:d6`.
>
-Guarde y cierre el archivo una vez que haya confirmado que la información es correcta. Ahora deberá configurar las dos interfaces físicas. Por defecto, para un servidor de OVHcloud, solo *eth0* tendrá un archivo de configuración. Abra con el siguiente comando:
+Una vez que sabe qué direcciones MAC están asociadas a cada tipo de interfaz (pública/privada), debe obtener los nombres de las interfaces.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-De forma predeterminada, el archivo mostrará el siguiente texto:
-
-```bash
-# Created by cloud-init on instance boot automatically, do not edit.
-#
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Obtención de los nombres de las interfaces
-> [!warning]
+> [!primary]
>
-> Las direcciones IP serán diferentes para cada servidor.
+> Si pierde la conexión de red con su servidor, siga los pasos de "**Abrir KVM**" de [esta guía](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Es necesario modificar el archivo para que muestre el siguiente texto:
+Para obtener los nombres de las interfaces, ejecute el siguiente comando:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> La dirección de hardware (dirección MAC) del ID de cliente se puede encontrar con el comando `ip utilizado anteriormente`. Este será el número al lado de `link/ether` del resultado mostrado.
+> Este comando mostrará diversas interfaces. Si tiene dificultad para determinar cuáles son sus interfaces físicas, la primera interfaz todavía tendrá la dirección IP pública del servidor asignada por defecto.
>
-El *#* delante de una línea indica que el servidor ignorará esta línea al leer el archivo. Esto significa que estas líneas no se tendrán en cuenta al crear el archivo de interfaz para *eth0*.
-
-Para crear el archivo de configuración *eth1*, utilice el siguiente comando:
-
-```bash
-vi /etc/sysconfig/network/ifcfg-eth1
+Aquí tiene un ejemplo de salida:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-Esta vez, el archivo estará vacío. Añada el siguiente contenido:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Por último, reinicie el servicio de red con el siguiente comando:
+Una vez que haya determinado los nombres de sus interfaces, puede configurar la agregación de interfaces en el sistema operativo.
+
+### Configuración de la agregación de interfaces
+
+Seleccione la pestaña siguiente que corresponda a la configuración de su servidor:
+
+- **Dos interfaces**: servidores Advance con dos NIC físicas.
+- **Cuatro interfaces - Double LAG**: servidores Scale y High-Grade con OLA en modo **Active - Double LAG** (agregados público + privado). Requiere [activar OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) en el área de cliente de OVHcloud.
+- **Cuatro interfaces - Fully Private**: servidores Scale y High-Grade con OLA en modo **Active - Fully Private** (único agregado privado para vRack). Requiere [activar OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) en el área de cliente de OVHcloud.
+
+> [!tabs]
+> Dos interfaces
+>> Cree el archivo de configuración del agregado `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **IP estática**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure a continuación cada interfaz física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Los archivos de configuración de las interfaces físicas permanecen igual que arriba.
+>>
+>> ///
+>>
+> Cuatro interfaces - Double LAG
+>> Esta configuración agrupa las interfaces públicas en `bond0` (con IP pública) y las interfaces privadas en `bond1` (para vRack).
+>>
+>> Cree el archivo de configuración del agregado público `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **IP estática**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Cree el archivo de configuración del agregado privado `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure a continuación cada interfaz física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (solo bond0)
+>>
+>> Para el agregado público, utilice DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> El agregado privado (`ifcfg-bond1`) y todos los archivos de configuración de las interfaces físicas permanecen igual que arriba.
+>>
+>> ///
+>>
+> Cuatro interfaces - Fully Private
+>> Esta configuración agrega todas las interfaces físicas en un único agregado exclusivamente para uso con vRack. No hay conectividad IP pública.
+>>
+>> > [!warning]
+>> >
+>> > Tras la implementación de OLA en modo Fully Private, la IP pública deja de estar accesible. Asegúrese de tener un medio alternativo de acceso (p. ej., a través de otro servidor en el vRack o mediante KVM/IPMI) antes de aplicar esta configuración.
+>> >
+>>
+>> Cree el archivo de configuración del agregado `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure a continuación cada interfaz física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Cree `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > En modo Fully Private, el agregado utiliza la dirección MAC de la interfaz **privada principal**. El campo `IPADDR` debe configurarse con su IP privada de vRack.
+>> >
+
+### Aplicación de la configuración
+
+Aplique la configuración recargando todas las interfaces con wicked:
```bash
wicked ifreload all
```
-Para comprobar que la agregación funciona, realice un ping a otro servidor en el mismo vRack. Si funciona, el proceso de configuración se habrá completado. En caso contrario, compruebe su configuración o intente reiniciar el servidor.
+Este reinicio puede tardar unos segundos ya que se está creando la interfaz de agregado. Para comprobar que el agregado funciona correctamente, haga ping a otro servidor en el mismo vRack. Si funciona, está todo listo. En caso contrario, compruebe sus configuraciones o intente reiniciar el servidor.
-También puede comprobar los parámetros utilizados en su interfaz ifcfg-bond0 utilizando el siguiente comando:
+También puede comprobar la configuración del agregado con el siguiente comando:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Más información
-[Configurar la agregación de enlaces OLA en el área de cliente](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Cómo configurar el ID de cliente para la agrupación de enlaces OVHcloud en Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 9 a 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Cómo configurar el ID de cliente para la agrupación de enlaces OVHcloud en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.fr-ca.md
index 40abcc76f95..21628e2621c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.fr-ca.md
@@ -1,14 +1,29 @@
---
-title: "Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15"
-excerpt: 'Activer OVHcloud Link Aggregation sur votre serveur SLES 15'
-updated: 2024-11-26
+title: "Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans SLES 15"
+excerpt: "Activez l'agrégation de liens dans votre serveur SLES 15 pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau"
+updated: 2026-04-20
---
+
+
## Objectif
-La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible.
+La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible. La bande passante disponible est également doublée grâce à l'agrégation.
+L'agrégation est basée sur la technologie IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Découvrez comment regrouper vos NIC (Network Interface Controller) pour les utiliser avec le service OLA sur SLES 15.**
+**Ce guide explique comment lier vos interfaces pour les utiliser pour OLA dans SLES 15.**
## Prérequis
@@ -42,106 +57,286 @@ ip a
```
> [!primary]
->
-> Cette commande retournera plusieurs « interfaces ». Si vous avez du mal à identifier vos NIC physiques, la première interface aura toujours l’adresse IP publique du serveur assignée par défaut.
+> Les valeurs (adresses MAC, adresses IP, etc.) indiquées dans les configurations et exemples ci-dessous le sont à titre d'exemples. Vous devez bien entendu remplacer ces valeurs par les vôtres.
>
-Une fois les noms de vos deux NIC identifiés, il faut à présent créer le NIC bonding ou agrégation de lien sur le système d’exploitation. Pour ce faire, créez le fichier d’interfaces sur l'éditeur de texte de votre choix à l’aide de la commande suivante :
+### Récupération des adresses MAC
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Connectez-vous à l'[espace client OVHcloud](/links/manager), rendez-vous dans la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur parmi les **Serveurs dédiés**.
-Cela ouvrira un fichier texte vide. Pour configurer l’interface d’agrégation, insérez les lignes suivantes dans le fichier texte :
+Cliquez sur l'onglet `Interfaces réseau`{.action} et prenez note des adresses MAC de chaque interface (publique/privée) qui s'affichent en bas du menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Veuillez noter que l'adresse MAC de l'interface **publique principale** est celle qui reçoit les offres DHCP, à la fois dans le système d'exploitation du serveur et en mode rescue. Cette interface gère la connectivité publique dans la configuration par défaut.
>
-> Vous pouvez utiliser n’importe quelle adresse IP et de sous-réseau privé souhaitées.
-> Si votre serveur possède plus que 2 interfaces réseau, vous pouvez les ajouter dans la configuration en incrémentant le numéro du paramètre `BONDING_SLAVE_`, par exemple `BONDING_SLAVE_2='eth2'`.
+> Quant à l'adresse MAC de l'interface **privée principale**, il s'agit de celle dont la valeur est la plus faible. Dans l'image exemple ci-dessus, il s'agit de l'adresse `a1:b2:c3:d4:e5:d6`.
>
-Sauvegardez et quittez le fichier une fois que vous avez confirmé que l’information est correcte. Il vous faut à présent configurer les deux interfaces physiques. Par défaut, pour un serveur OVHcloud, seul *eth0* aura un fichier de configuration. Ouvrez-le à l’aide de la commande suivante :
+Maintenant que vous savez quelles adresses MAC sont associées à chaque type (public/privé) d'interface, vous devez récupérer les noms des interfaces.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-Par défaut, le fichier affichera le texte suivant :
-
-```bash
-# Created by cloud-init on instance boot automatically, do not edit.
-#
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Récupération des noms d'interfaces
-> [!warning]
+> [!primary]
>
-> Les adresses IP seront différentes pour chaque serveur.
+> Si vous perdez la connexion réseau à votre serveur, suivez les étapes intitulées « **Ouvrir un KVM** » de [ce guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Vous devez modifier ce fichier pour qu’il affiche le texte suivant :
+Pour récupérer les noms des interfaces, lancez la commande suivante :
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> L’adresse matérielle (adresse MAC) du NIC peut être retrouvée à l’aide de la commande `ip a` utilisée précédemment. Ce sera le numéro à côté de `link/ether` du résultat affiché.
+> Cette commande va afficher de nombreuses interfaces. Si vous avez des difficultés à déterminer quelles sont vos interfaces physiques, l'adresse IP publique du serveur reste attachée par défaut à la première interface.
>
-Le *#* devant une ligne indique que le serveur ignorera cette ligne lors de la lecture du fichier. Cela signifie que ces lignes ne seront pas prises en compte lors de la création du fichier d’interface pour *eth0*.
-
-Vous devrez créer le fichier de configuration *eth1* à l’aide de la commande suivante :
-
-```bash
-vi /etc/sysconfig/network/ifcfg-eth1
+Voici un exemple de sortie :
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-Cette fois-ci, le fichier sera vide. Vous devrez y ajouter le contenu suivant :
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Pour finir, il faudra redémarrer le service réseau à l’aide de la commande suivante :
+Une fois que vous avez déterminé les noms de vos interfaces, vous pouvez configurer l'agrégation d'interfaces dans le système d'exploitation.
+
+### Configuration de l'agrégation d'interfaces
+
+Sélectionnez l'onglet ci-dessous correspondant à la configuration de votre serveur :
+
+- **Deux interfaces** : serveurs Advance avec deux cartes réseau physiques.
+- **Quatre interfaces - Double LAG** : serveurs Scale et High Grade avec OLA en mode **Active - Double LAG** (agrégats public + privé). Cela nécessite l'[activation d'OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) dans l'espace client OVHcloud.
+- **Quatre interfaces - Fully Private** : serveurs Scale et High Grade avec OLA en mode **Active - Fully Private** (agrégat privé unique pour le vRack). Cela nécessite l'[activation d'OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) dans l'espace client OVHcloud.
+
+> [!tabs]
+> Deux interfaces
+>> Créez le fichier de configuration de l'agrégat `/etc/sysconfig/network/ifcfg-bond0` :
+>>
+>> **IP fixe**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configurez ensuite chaque interface physique. Éditez `/etc/sysconfig/network/ifcfg-ens22f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens22f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Les fichiers de configuration des interfaces physiques restent les mêmes que ci-dessus.
+>>
+>> ///
+>>
+> Quatre interfaces - Double LAG
+>> Cette configuration lie les interfaces publiques dans `bond0` (avec l'IP publique) et les interfaces privées dans `bond1` (pour le vRack).
+>>
+>> Créez le fichier de configuration de l'agrégat public `/etc/sysconfig/network/ifcfg-bond0` :
+>>
+>> **IP fixe**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Créez le fichier de configuration de l'agrégat privé `/etc/sysconfig/network/ifcfg-bond1` :
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configurez ensuite chaque interface physique. Éditez `/etc/sysconfig/network/ifcfg-ens22f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens22f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens33f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens33f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 uniquement)
+>>
+>> Pour l'agrégat public, utilisez DHCP :
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> L'agrégat privé (`ifcfg-bond1`) et tous les fichiers de configuration des interfaces physiques restent les mêmes que ci-dessus.
+>>
+>> ///
+>>
+> Quatre interfaces - Fully Private
+>> Cette configuration agrège toutes les interfaces physiques dans un seul agrégat pour une utilisation vRack uniquement. Il n'y a pas de connectivité IP publique.
+>>
+>> > [!warning]
+>> >
+>> > Suite à la mise en œuvre d'OLA en mode Fully Private, l'IP publique n'est plus accessible. Assurez-vous de disposer d'un moyen d'accès alternatif (par exemple via un autre serveur dans le vRack, ou via KVM/IPMI) avant d'appliquer cette configuration.
+>> >
+>>
+>> Créez le fichier de configuration de l'agrégat `/etc/sysconfig/network/ifcfg-bond0` :
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configurez ensuite chaque interface physique. Éditez `/etc/sysconfig/network/ifcfg-ens22f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens22f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens33f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens33f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > En mode Fully Private, l'agrégat utilise l'adresse MAC de l'interface **privée principale**. Le champ `IPADDR` doit être défini avec votre IP privée vRack.
+>> >
+
+### Application de la configuration
+
+Appliquez la configuration en rechargeant toutes les interfaces avec wicked :
```bash
wicked ifreload all
```
-Pour vérifier que cette agrégation fonctionne, effectuez un ping vers un autre serveur sur le même vRack. Si cela fonctionne, le processus de configuration est terminé. Si ce n’est pas le cas, vérifiez vos configurations ou essayez de redémarrer le serveur.
+Cette opération peut prendre plusieurs secondes, car l'interface d'agrégat est en cours de construction. Pour vérifier que l'agrégat fonctionne, pingez un autre serveur sur le même vRack. Si cela fonctionne, la configuration est terminée. Si ce n'est pas le cas, vérifiez vos configurations ou essayez de redémarrer le serveur.
-Vous pouvez également vérifier les paramètres utilisés par votre interface ifcfg-bond0 à l'aide de la commande suivante :
+Vous pouvez également vérifier les paramètres de l'agrégat à l'aide de la commande suivante :
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Aller plus loin
-[Configurer l’agrégation de liens OLA dans votre espace client](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuration de l'agrégation de liens OVHcloud dans l'espace client OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Comment configurer l'agrégation de liens avec LACP dans Debian 12 ou Ubuntu 24.04 (Netplan)](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 à 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.fr-fr.md
index 40abcc76f95..21628e2621c 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.fr-fr.md
@@ -1,14 +1,29 @@
---
-title: "Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15"
-excerpt: 'Activer OVHcloud Link Aggregation sur votre serveur SLES 15'
-updated: 2024-11-26
+title: "Comment configurer votre NIC pour l'agrégation de liens OVHcloud dans SLES 15"
+excerpt: "Activez l'agrégation de liens dans votre serveur SLES 15 pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau"
+updated: 2026-04-20
---
+
+
## Objectif
-La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible.
+La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible. La bande passante disponible est également doublée grâce à l'agrégation.
+L'agrégation est basée sur la technologie IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Découvrez comment regrouper vos NIC (Network Interface Controller) pour les utiliser avec le service OLA sur SLES 15.**
+**Ce guide explique comment lier vos interfaces pour les utiliser pour OLA dans SLES 15.**
## Prérequis
@@ -42,106 +57,286 @@ ip a
```
> [!primary]
->
-> Cette commande retournera plusieurs « interfaces ». Si vous avez du mal à identifier vos NIC physiques, la première interface aura toujours l’adresse IP publique du serveur assignée par défaut.
+> Les valeurs (adresses MAC, adresses IP, etc.) indiquées dans les configurations et exemples ci-dessous le sont à titre d'exemples. Vous devez bien entendu remplacer ces valeurs par les vôtres.
>
-Une fois les noms de vos deux NIC identifiés, il faut à présent créer le NIC bonding ou agrégation de lien sur le système d’exploitation. Pour ce faire, créez le fichier d’interfaces sur l'éditeur de texte de votre choix à l’aide de la commande suivante :
+### Récupération des adresses MAC
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Connectez-vous à l'[espace client OVHcloud](/links/manager), rendez-vous dans la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur parmi les **Serveurs dédiés**.
-Cela ouvrira un fichier texte vide. Pour configurer l’interface d’agrégation, insérez les lignes suivantes dans le fichier texte :
+Cliquez sur l'onglet `Interfaces réseau`{.action} et prenez note des adresses MAC de chaque interface (publique/privée) qui s'affichent en bas du menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Veuillez noter que l'adresse MAC de l'interface **publique principale** est celle qui reçoit les offres DHCP, à la fois dans le système d'exploitation du serveur et en mode rescue. Cette interface gère la connectivité publique dans la configuration par défaut.
>
-> Vous pouvez utiliser n’importe quelle adresse IP et de sous-réseau privé souhaitées.
-> Si votre serveur possède plus que 2 interfaces réseau, vous pouvez les ajouter dans la configuration en incrémentant le numéro du paramètre `BONDING_SLAVE_`, par exemple `BONDING_SLAVE_2='eth2'`.
+> Quant à l'adresse MAC de l'interface **privée principale**, il s'agit de celle dont la valeur est la plus faible. Dans l'image exemple ci-dessus, il s'agit de l'adresse `a1:b2:c3:d4:e5:d6`.
>
-Sauvegardez et quittez le fichier une fois que vous avez confirmé que l’information est correcte. Il vous faut à présent configurer les deux interfaces physiques. Par défaut, pour un serveur OVHcloud, seul *eth0* aura un fichier de configuration. Ouvrez-le à l’aide de la commande suivante :
+Maintenant que vous savez quelles adresses MAC sont associées à chaque type (public/privé) d'interface, vous devez récupérer les noms des interfaces.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-Par défaut, le fichier affichera le texte suivant :
-
-```bash
-# Created by cloud-init on instance boot automatically, do not edit.
-#
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Récupération des noms d'interfaces
-> [!warning]
+> [!primary]
>
-> Les adresses IP seront différentes pour chaque serveur.
+> Si vous perdez la connexion réseau à votre serveur, suivez les étapes intitulées « **Ouvrir un KVM** » de [ce guide](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Vous devez modifier ce fichier pour qu’il affiche le texte suivant :
+Pour récupérer les noms des interfaces, lancez la commande suivante :
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> L’adresse matérielle (adresse MAC) du NIC peut être retrouvée à l’aide de la commande `ip a` utilisée précédemment. Ce sera le numéro à côté de `link/ether` du résultat affiché.
+> Cette commande va afficher de nombreuses interfaces. Si vous avez des difficultés à déterminer quelles sont vos interfaces physiques, l'adresse IP publique du serveur reste attachée par défaut à la première interface.
>
-Le *#* devant une ligne indique que le serveur ignorera cette ligne lors de la lecture du fichier. Cela signifie que ces lignes ne seront pas prises en compte lors de la création du fichier d’interface pour *eth0*.
-
-Vous devrez créer le fichier de configuration *eth1* à l’aide de la commande suivante :
-
-```bash
-vi /etc/sysconfig/network/ifcfg-eth1
+Voici un exemple de sortie :
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-Cette fois-ci, le fichier sera vide. Vous devrez y ajouter le contenu suivant :
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Pour finir, il faudra redémarrer le service réseau à l’aide de la commande suivante :
+Une fois que vous avez déterminé les noms de vos interfaces, vous pouvez configurer l'agrégation d'interfaces dans le système d'exploitation.
+
+### Configuration de l'agrégation d'interfaces
+
+Sélectionnez l'onglet ci-dessous correspondant à la configuration de votre serveur :
+
+- **Deux interfaces** : serveurs Advance avec deux cartes réseau physiques.
+- **Quatre interfaces - Double LAG** : serveurs Scale et High Grade avec OLA en mode **Active - Double LAG** (agrégats public + privé). Cela nécessite l'[activation d'OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) dans l'espace client OVHcloud.
+- **Quatre interfaces - Fully Private** : serveurs Scale et High Grade avec OLA en mode **Active - Fully Private** (agrégat privé unique pour le vRack). Cela nécessite l'[activation d'OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) dans l'espace client OVHcloud.
+
+> [!tabs]
+> Deux interfaces
+>> Créez le fichier de configuration de l'agrégat `/etc/sysconfig/network/ifcfg-bond0` :
+>>
+>> **IP fixe**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configurez ensuite chaque interface physique. Éditez `/etc/sysconfig/network/ifcfg-ens22f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens22f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Les fichiers de configuration des interfaces physiques restent les mêmes que ci-dessus.
+>>
+>> ///
+>>
+> Quatre interfaces - Double LAG
+>> Cette configuration lie les interfaces publiques dans `bond0` (avec l'IP publique) et les interfaces privées dans `bond1` (pour le vRack).
+>>
+>> Créez le fichier de configuration de l'agrégat public `/etc/sysconfig/network/ifcfg-bond0` :
+>>
+>> **IP fixe**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Créez le fichier de configuration de l'agrégat privé `/etc/sysconfig/network/ifcfg-bond1` :
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configurez ensuite chaque interface physique. Éditez `/etc/sysconfig/network/ifcfg-ens22f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens22f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens33f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens33f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (bond0 uniquement)
+>>
+>> Pour l'agrégat public, utilisez DHCP :
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> L'agrégat privé (`ifcfg-bond1`) et tous les fichiers de configuration des interfaces physiques restent les mêmes que ci-dessus.
+>>
+>> ///
+>>
+> Quatre interfaces - Fully Private
+>> Cette configuration agrège toutes les interfaces physiques dans un seul agrégat pour une utilisation vRack uniquement. Il n'y a pas de connectivité IP publique.
+>>
+>> > [!warning]
+>> >
+>> > Suite à la mise en œuvre d'OLA en mode Fully Private, l'IP publique n'est plus accessible. Assurez-vous de disposer d'un moyen d'accès alternatif (par exemple via un autre serveur dans le vRack, ou via KVM/IPMI) avant d'appliquer cette configuration.
+>> >
+>>
+>> Créez le fichier de configuration de l'agrégat `/etc/sysconfig/network/ifcfg-bond0` :
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configurez ensuite chaque interface physique. Éditez `/etc/sysconfig/network/ifcfg-ens22f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens22f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens33f0np0` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Créez `/etc/sysconfig/network/ifcfg-ens33f1np1` :
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > En mode Fully Private, l'agrégat utilise l'adresse MAC de l'interface **privée principale**. Le champ `IPADDR` doit être défini avec votre IP privée vRack.
+>> >
+
+### Application de la configuration
+
+Appliquez la configuration en rechargeant toutes les interfaces avec wicked :
```bash
wicked ifreload all
```
-Pour vérifier que cette agrégation fonctionne, effectuez un ping vers un autre serveur sur le même vRack. Si cela fonctionne, le processus de configuration est terminé. Si ce n’est pas le cas, vérifiez vos configurations ou essayez de redémarrer le serveur.
+Cette opération peut prendre plusieurs secondes, car l'interface d'agrégat est en cours de construction. Pour vérifier que l'agrégat fonctionne, pingez un autre serveur sur le même vRack. Si cela fonctionne, la configuration est terminée. Si ce n'est pas le cas, vérifiez vos configurations ou essayez de redémarrer le serveur.
-Vous pouvez également vérifier les paramètres utilisés par votre interface ifcfg-bond0 à l'aide de la commande suivante :
+Vous pouvez également vérifier les paramètres de l'agrégat à l'aide de la commande suivante :
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Aller plus loin
-[Configurer l’agrégation de liens OLA dans votre espace client](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuration de l'agrégation de liens OVHcloud dans l'espace client OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Comment configurer l'agrégation de liens avec LACP dans Debian 12 ou Ubuntu 24.04 (Netplan)](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 à 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.it-it.md
index beccdcf335c..0ef53bf5319 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.it-it.md
@@ -1,18 +1,33 @@
---
-title: "Come configurare il NIC handle per aggregare i link OVHcloud in SLES 15"
-excerpt: Attiva OVHcloud Link Aggregation sul tuo server SLES 15
-updated: 2024-11-26
+title: "Configurare un NIC per il servizio OVHcloud Link Aggregation in SLES 15"
+excerpt: "Attiva l'aggregazione di collegamenti sul tuo server SLES 15 per aumentare la disponibilità del tuo server e migliorare l'efficienza delle tue connessioni di rete"
+updated: 2026-04-20
---
+
+
## Obiettivo
-La tecnologia OVHcloud Link Aggregation (OLA) è sviluppata dai nostri team per aumentare la disponibilità dei server e migliorare l'efficacia delle connessioni di rete. In pochi click è possibile aggregare le schede di rete e rendere ridondanti i collegamenti di rete. Ciò significa che in caso di guasto di un collegamento, il traffico viene automaticamente reindirizzato verso un altro collegamento disponibile.
+La tecnologia OVHcloud Link Aggregation (OLA) è stata progettata dai team OVHcloud per aumentare la disponibilità dei server e potenziare le connessioni di rete. L'attivazione dell'opzione permette di aggregare in pochi click le schede di rete e rendere i collegamenti ridondati in modo che, in caso di malfunzionamenti, il traffico venga reindirizzato automaticamente verso il collegamento disponibile. La larghezza di banda disponibile viene anche raddoppiata grazie all'aggregazione.
+L'aggregazione si basa sulla tecnologia IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Questa guida ti mostra come raggruppare i tuoi NIC (Network Interface Controller) per utilizzarli con il servizio OLA su SLES 15.**
+**Questa guida spiega come configurare le interfacce in aggregazione per utilizzarle con OLA in SLES 15.**
## Prerequisiti
-- [Aver configurato il NIC handle per la funzionalità OVHcloud Link Aggregation dallo Spazio Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Configurare OVHcloud Link Aggregation nello Spazio Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -27,121 +42,301 @@ La tecnologia OVHcloud Link Aggregation (OLA) è sviluppata dai nostri team per
## Procedura
-Dal momento che i nostri NIC su OLA sono configurati privatamente, non è possibile connettersi in SSH al server. Per accedere al server è quindi necessario utilizzare il tool IPMI.
+Poiché la configurazione dei NIC in OLA è di tipo privato-privato, non sarà possibile accedere al server in SSH. Sarà quindi necessario utilizzare lo strumento IPMI per accedere al server.
-Clicca sulla scheda `IPMI`{.action} (1) e poi sul pulsante `Da un applet Java (KVM)`{.action} (2).
+Clicca sulla scheda `IPMI`{.action} (1) e poi sul pulsante `Da una applet Java (KVM)`{.action} (2).
{.thumbnail}
-Verrà scaricato un software JNLP. Avvia il software per accedere all'IPMI. Accedi utilizzando le informazioni di identificazione associate al server.
+Verrà scaricato un software JNLP. Avvialo per accedere all'IPMI. Accedi utilizzando le informazioni di identificazione associate al server.
-Di default, utilizzando un modello OVHcloud, i NIC saranno nominati *eth0* e *eth1*. Se non utilizzi un modello OVHcloud, puoi recuperare i nomi delle interfacce utilizzando il seguente comando:
+Di default, utilizzando un modello OVHcloud, i NIC saranno denominati *eth0* e *eth1*. Se non utilizzi un modello OVHcloud, puoi recuperare i nomi delle interfacce utilizzando il seguente comando:
```bash
ip a
```
> [!primary]
->
-> Il comando restituirà diverse "interfacce". In caso di difficoltà nell'identificazione dei NIC fisici, la prima interfaccia avrà sempre l'indirizzo IP pubblico del server assegnato di default.
+> I valori (indirizzi MAC, indirizzi IP, ecc.) indicati nelle configurazioni e negli esempi seguenti sono forniti a titolo di esempio. Naturalmente è necessario sostituirli con i propri valori.
>
-Una volta identificati i nomi dei tuoi due NIC-handle, è necessario creare il NIC-bonding o aggregare i link sul sistema operativo. Per effettuare questa operazione, crea il file di interfacce sull'editor di testo scelto utilizzando il seguente comando:
+### Recupero degli indirizzi MAC
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Accedi allo [Spazio Cliente OVHcloud](/links/manager), vai nella sezione `Bare Metal Cloud`{.action} e seleziona il tuo server tra i **Server dedicati**.
-Aprirà un file di testo vuoto. Per configurare l'interfaccia di aggregazione, inserisci queste righe nel file di testo:
+Vai alla scheda `Interfacce di rete`{.action} e prendi nota degli indirizzi MAC di ciascuna interfaccia (pubblica/privata) visualizzati in fondo al menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> L'indirizzo MAC dell'interfaccia **pubblica principale** è quello che riceve le offerte DHCP, sia nel sistema operativo del server che in modalità rescue. Questa interfaccia gestisce la connettività pubblica nella configurazione predefinita.
>
-> Puoi utilizzare qualsiasi indirizzo IP o sottorete privata che desideri.
-> Se il tuo server possiede più di 2 interfacce di rete, puoi aggiungerle nella configurazione inserendo il numero del parametro `BONDING_SLAVE_`, ad esempio `BONDING_SLAVE_2='eth3`.
+> Inoltre, l'indirizzo MAC dell'interfaccia **privata principale** è quello con il valore più basso. Nell'immagine di esempio sopra, si tratta dell'indirizzo `a1:b2:c3:d4:e5:d6`.
>
-Salva e lascia il file una volta confermato che l'informazione è corretta. A questo punto è necessario configurare le due interfacce fisiche. Di default, su un server OVHcloud solo *eth0* dispone di un file di configurazione. Apri il comando:
+Una volta che sai quali indirizzi MAC sono associati a ciascun tipo di interfaccia (pubblica/privata), devi recuperare i nomi delle interfacce.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-Di default, il file mostrerà questo testo:
-
-```bash
-# Created by cloud-init on instance boot automatically, do not edit.
-#
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Recupero dei nomi delle interfacce
-> [!warning]
+> [!primary]
>
-> Gli indirizzi IP saranno differenti per ogni server.
+> Se perdi la connessione di rete al server, segui i passaggi "**Apri KVM**" di [questa guida](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-È necessario modificare questo file per visualizzare questo testo:
+Per recuperare i nomi delle interfacce, esegui il seguente comando:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> L'indirizzo hardware (indirizzo MAC) del NIC handle può essere recuperato utilizzando il comando `ip utilizzato in precedenza`. Sarà il numero accanto a `link/ether` del risultato visualizzato.
+> Questo comando mostrerà numerose interfacce. In caso di difficoltà nel determinare quali siano le interfacce fisiche, l'indirizzo IP pubblico del server è ancora associato di default alla prima interfaccia.
>
-L'*#* davanti a una linea indica che il server non saprà questa linea durante la lettura del file. significa che queste righe non saranno prese in carico durante la creazione del file di interfaccia per *eth0*.
-
-Per creare il file di configurazione *eth1*, utilizza questo comando:
-
-```bash
-vi /etc/sysconfig/network/ifcfg-eth1
+Ecco un esempio di output:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-Questa volta il file sarà vuoto. Aggiungi questo contenuto:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Riavvia il servizio di rete utilizzando questo comando:
+Una volta determinati i nomi delle interfacce, è possibile configurare l'aggregazione nel sistema operativo.
+
+### Configurazione dell'aggregazione delle interfacce
+
+Seleziona la scheda seguente corrispondente alla configurazione del tuo server:
+
+- **Due interfacce**: server Advance con due NIC fisiche.
+- **Quattro interfacce - Double LAG**: server Scale e High-Grade con OLA in modalità **Active - Double LAG** (aggregati pubblico + privato). Richiede l'[attivazione di OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) nello Spazio Cliente OVHcloud.
+- **Quattro interfacce - Fully Private**: server Scale e High-Grade con OLA in modalità **Active - Fully Private** (unico aggregato privato per vRack). Richiede l'[attivazione di OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) nello Spazio Cliente OVHcloud.
+
+> [!tabs]
+> Due interfacce
+>> Crea il file di configurazione dell'aggregato `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **IP statico**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configura poi ogni interfaccia fisica. Modifica `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Crea `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> I file di configurazione delle interfacce fisiche rimangono invariati come sopra.
+>>
+>> ///
+>>
+> Quattro interfacce - Double LAG
+>> Questa configurazione raggruppa le interfacce pubbliche in `bond0` (con IP pubblico) e le interfacce private in `bond1` (per vRack).
+>>
+>> Crea il file di configurazione dell'aggregato pubblico `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **IP statico**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Crea il file di configurazione dell'aggregato privato `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configura poi ogni interfaccia fisica. Modifica `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Crea `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Crea `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Crea `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (solo bond0)
+>>
+>> Per l'aggregato pubblico, utilizza DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> L'aggregato privato (`ifcfg-bond1`) e tutti i file di configurazione delle interfacce fisiche rimangono invariati come sopra.
+>>
+>> ///
+>>
+> Quattro interfacce - Fully Private
+>> Questa configurazione aggrega tutte le interfacce fisiche in un unico aggregato esclusivamente per l'utilizzo con vRack. Non è prevista connettività IP pubblica.
+>>
+>> > [!warning]
+>> >
+>> > In seguito all'implementazione di OLA in modalità Fully Private, l'IP pubblico non è più accessibile. Assicurati di disporre di un mezzo di accesso alternativo (ad esempio tramite un altro server nel vRack o via KVM/IPMI) prima di applicare questa configurazione.
+>> >
+>>
+>> Crea il file di configurazione dell'aggregato `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configura poi ogni interfaccia fisica. Modifica `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Crea `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Crea `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Crea `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > In modalità Fully Private, l'aggregato utilizza l'indirizzo MAC dell'interfaccia **privata principale**. Il campo `IPADDR` deve essere impostato sul tuo indirizzo IP privato vRack.
+>> >
+
+### Applicazione della configurazione
+
+Applica la configurazione ricaricando tutte le interfacce con wicked:
```bash
wicked ifreload all
```
-Per verificare che questa aggregazione funzioni, effettua un ping verso un altro server sulla stessa vRack. Se l'operazione funziona, il processo di configurazione è completato. In caso contrario, verifica la configurazione o prova a riavviare il server.
+Questa operazione potrebbe richiedere alcuni secondi per costruire l'interfaccia di aggregazione. Per verificare che l'aggregato funzioni correttamente, effettua il ping di un altro server nella stessa vRack. Se funziona, la procedura è conclusa. In caso contrario, verifica nuovamente le configurazioni o prova a riavviare il server.
-Per verificare le impostazioni utilizzate dall'interfaccia ifcfg-bond0, utilizza questo comando:
+Puoi anche verificare le impostazioni dell'aggregato con il seguente comando:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Per saperne di più
-[Configurare l'aggregazione dei link OLA nel tuo Spazio Cliente](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurare OVHcloud Link Aggregation nello Spazio Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Come configurare la NIC per OVHcloud Link Aggregation in Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Come configurare il NIC handle per aggregare i link OVHcloud su Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Configurare un NIC per il servizio OVHcloud Link Aggregation in Debian 9 a 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Come configurare il tuo NIC handle per aggregare i link OVHcloud con Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Configurare un NIC per il servizio OVHcloud Link Aggregation in Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Contatta la nostra [Community di utenti](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.pl-pl.md
index b259fd0207b..56ed35bef3e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.pl-pl.md
@@ -1,147 +1,342 @@
---
-title: "Jak skonfigurować identyfikator klienta do celów agregacji linków OVHcloud w SLES 15"
-excerpt: 'Włącz Link Aggregation na serwerze SLES 15'
-updated: 2024-11-26
+title: "Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w SLES 15"
+excerpt: "Aktywuj agregację łączy na serwerze SLES 15, aby zwiększyć dostępność serwera i wydajność połączeń sieciowych"
+updated: 2026-04-20
---
+
+
## Wprowadzenie
-Technologia OVHcloud Link Aggregation (OLA) została zaprojektowana przez nasze zespoły w celu zwiększenia dostępności serwera i wydajności połączeń sieciowych. Za pomocą kilku kliknięć możesz łączyć karty sieciowe i redundantować połączenia sieciowe. Oznacza to, że w przypadku awarii połączenia ruch jest automatycznie przekierowywany do innego dostępnego połączenia.
+Technologia OVHcloud Link Aggregation (OLA) została zaprojektowana przez nasze zespoły w celu zwiększenia dostępności serwera oraz podniesienia wydajności połączeń sieciowych. Za pomocą kilku kliknięć możesz połączyć karty sieciowe i sprawić, że Twoje połączenia sieciowe staną się redundantne. Oznacza to, że jeśli jedno połączenie zostanie zerwane, ruch zostanie automatycznie przekierowany do innego dostępnego łącza. Dostępna przepustowość jest również podwajana dzięki agregacji.
+Agregacja oparta jest na technologii IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Dowiedz się, jak połączyć Twoje identyfikatory klienta (Network Interface Controller) i korzystać z nich w ramach usługi OLA na SLES 15.**
+**Niniejszy przewodnik wyjaśnia, jak skonfigurować interfejsy do agregacji w celu korzystania z OLA w SLES 15.**
## Wymagania początkowe
-- [Skonfigurowanie identyfikatora klienta dla funkcji OVHcloud Link Aggregation w Panelu klienta](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Konfiguracja OVHcloud Link Aggregation w Panelu klienta OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
### Dostęp do Panelu klienta OVHcloud
-- **Bezpośredni link:** [Serwery dedykowane](/links/control-panel/baremetal-dedicated-servers)
-- **Ścieżka nawigacji:** `Bare Metal Cloud`{.action} > `Serwery dedykowane`{.action} > Wybierz swój serwer
+- **Link bezpośredni:** [Serwery dedykowane](/links/control-panel/baremetal-dedicated-servers)
+- **Ścieżka nawigacji:** `Bare Metal Cloud`{.action} > `Serwery dedykowane`{.action} > Wybierz serwer
---
## W praktyce
-Ze względu na prywatną konfigurację OLA dla naszych identyfikatorów klienta nie można połączyć się z serwerem za pomocą SSH. Aby uzyskać dostęp do serwera, użyj narzędzia IPMI.
+Ponieważ konfiguracja kart sieciowych w OLA jest prywatna, nie będziesz mógł połączyć się z serwerem za pomocą SSH. W związku z tym do uzyskania dostępu do serwera użyj narzędzia IPMI.
-Następnie kliknij zakładkę `IPMI`{.action} (1), a następnie przycisk `Z poziomu apletu Java (KVM)`{.action} (2).
+Kliknij zakładkę `IPMI`{.action} (1), a następnie kliknij przycisk `Z apletu Java (KVM)`{.action} (2).
-{.thumbnail}
+{.thumbnail}
-Pobierz program JNLP. Uruchom oprogramowanie, aby uzyskać dostęp do IPMI. Zaloguj się, używając danych identyfikacyjnych przypisanych do serwera.
+Zostanie pobrany plik JNLP. Uruchom oprogramowanie, aby uzyskać dostęp do IPMI. Zaloguj się, używając danych identyfikacyjnych przypisanych do serwera.
-Domyślnie nazwy identyfikatorów klienta będą znane jako *eth* i *eth*. Jeśli nie używasz szablonu OVHcloud, możesz odnaleźć nazwy interfejsów, używając następującej komendy:
+Domyślnie podczas korzystania z szablonu OVHcloud karty sieciowe będą nazywane *eth0* i *eth1*. Jeśli nie używasz szablonu OVHcloud, możesz sprawdzić nazwy interfejsów za pomocą następującego polecenia:
```bash
ip a
```
> [!primary]
->
-> To polecenie zwróci kilka "interfejsów". Jeśli masz trudności z identyfikacją fizycznych identyfikatorów klienta, pierwszy interfejs zawsze będzie miał publiczny adres IP serwera przypisanego domyślnie.
+> Wartości (adresy MAC, adresy IP itp.) podane w poniższych konfiguracjach i przykładach służą wyłącznie jako przykłady. Należy oczywiście zastąpić je własnymi wartościami.
>
-Po zidentyfikowaniu nazw dwóch identyfikatorów klienta należy utworzyć identyfikator klienta lub powiązanie z systemem operacyjnym. W tym celu utwórz plik interfejsów w wybranym przez Ciebie edytorze tekstu za pomocą polecenia:
+### Pobieranie adresów MAC
-```bash
-vi /etc/sysconfig/network/ifcfg-bond0
-```
+Zaloguj się do [Panelu klienta OVHcloud](/links/manager), przejdź do sekcji `Bare Metal Cloud`{.action} i wybierz serwer z listy **Serwery dedykowane**.
-Otworzy to pusty plik tekstowy. Aby skonfigurować interfejs agregacji, wstaw następujące wiersze w pliku tekstowym:
+Przejdź do zakładki `Interfejsy sieciowe`{.action} i zanotuj adresy MAC dla każdego interfejsu (publicznego/prywatnego), które są wyświetlane na dole menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> Należy pamiętać, że adres MAC interfejsu **głównego publicznego** jest tym, który odbiera oferty DHCP, zarówno w systemie operacyjnym serwera, jak i w trybie ratunkowym. Ten interfejs obsługuje łączność publiczną w domyślnej konfiguracji.
>
-> Możesz korzystać z dowolnego adresu IP i prywatnej podsieci.
-> Jeśli Twój serwer ma więcej niż 2 interfejsów sieciowych, możesz je dodać do konfiguracji, dodając numer parametru `BONDING_SLAVE_`, na przykład `BONDING_SLAVE_2='eth2'`.
+> Ponadto adres MAC interfejsu **głównego prywatnego** to ten o najniższej wartości. Na powyższym przykładowym obrazku jest to adres `a1:b2:c3:d4:e5:d6`.
>
-Zapisz i wyjdź z pliku po potwierdzeniu, że informacje są poprawne. Teraz skonfiguruj dwa fizyczne interfejsy. Domyślnie dla serwera OVHcloud tylko *eth* będzie miał plik konfiguracyjny. Otwórz plik za pomocą polecenia:
+Teraz, gdy wiesz, jakie adresy MAC są przypisane do każdego typu interfejsu (publiczny/prywatny), musisz pobrać nazwy interfejsów.
-```bash
-vi /etc/sysconfig/network/ifcfg-eth0
-```
-
-Domyślnie plik będzie wyświetlał następujący tekst:
-
-```bash
-# Created by cloud-init on instance boot automatically, do not edit.
-#
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Pobieranie nazw interfejsów
-> [!warning]
+> [!primary]
>
-> Adresy IP będą różne dla każdego serwera.
+> Jeśli utracisz połączenie sieciowe z serwerem, wykonaj kroki opisane w sekcji "**Otwórz KVM**" z [tego przewodnika](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Musisz zmienić ten plik, aby wyświetlał następujący tekst:
+Aby pobrać nazwy interfejsów, wykonaj następujące polecenie:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> Adres sprzętowy (adres MAC) identyfikatora klienta można odnaleźć za pomocą polecenia `ip a` wcześniej. Będzie to numer obok `link/ether` wyświetlanego wyniku.
+> To polecenie wyświetli wiele interfejsów. Jeśli masz trudności z określeniem, które z nich są Twoimi interfejsami fizycznymi, pierwszemu interfejsowi domyślnie przypisany jest publiczny adres IP serwera.
>
-*#* przed linią wskazuje, że serwer zignoruje tę linię podczas odczytu pliku. Oznacza to, że linie te nie będą brane pod uwagę podczas tworzenia pliku interfejsu dla *eth*.
-
-Utwórz plik konfiguracyjny *eth1* za pomocą polecenia:
-
-```bash
-vi /etc/sysconfig/network/ifcfg-eth1
+Oto przykład wyniku:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-Tym razem plik będzie pusty. Dodaj następującą zawartość:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Na koniec uruchom ponownie usługę sieciową, wprowadzając następujące polecenie:
+Po ustaleniu nazw interfejsów możesz skonfigurować agregację interfejsów w systemie operacyjnym.
+
+### Konfiguracja agregacji interfejsów
+
+Wybierz poniższą zakładkę odpowiadającą konfiguracji serwera:
+
+- **Dwa interfejsy**: serwery Advance z dwoma fizycznymi kartami NIC.
+- **Cztery interfejsy - Double LAG**: serwery Scale i High-Grade z OLA w trybie **Active - Double LAG** (agregaty publiczny + prywatny). Wymaga [włączenia OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) w Panelu klienta OVHcloud.
+- **Cztery interfejsy - Fully Private**: serwery Scale i High-Grade z OLA w trybie **Active - Fully Private** (jeden prywatny agregat dla vRack). Wymaga [włączenia OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) w Panelu klienta OVHcloud.
+
+> [!tabs]
+> Dwa interfejsy
+>> Utwórz plik konfiguracyjny agregatu `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Statyczny IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Następnie skonfiguruj każdy fizyczny interfejs. Edytuj `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Utwórz `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Pliki konfiguracyjne fizycznych interfejsów pozostają takie same jak powyżej.
+>>
+>> ///
+>>
+> Cztery interfejsy - Double LAG
+>> Ta konfiguracja łączy publiczne interfejsy w `bond0` (z publicznym IP) i prywatne interfejsy w `bond1` (dla vRack).
+>>
+>> Utwórz plik konfiguracyjny publicznego agregatu `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **Statyczny IP**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Utwórz plik konfiguracyjny prywatnego agregatu `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Następnie skonfiguruj każdy fizyczny interfejs. Edytuj `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Utwórz `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Utwórz `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Utwórz `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (tylko bond0)
+>>
+>> W przypadku publicznego agregatu użyj DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Prywatny agregat (`ifcfg-bond1`) i wszystkie pliki konfiguracyjne fizycznych interfejsów pozostają takie same jak powyżej.
+>>
+>> ///
+>>
+> Cztery interfejsy - Fully Private
+>> Ta konfiguracja agreguje wszystkie fizyczne interfejsy w jednym agregacie wyłącznie do użytku z vRack. Brak publicznej łączności IP.
+>>
+>> > [!warning]
+>> >
+>> > Po wdrożeniu OLA w trybie Fully Private publiczny adres IP nie jest już dostępny. Upewnij się, że masz alternatywny sposób dostępu (np. przez inny serwer w vRack lub przez KVM/IPMI) przed zastosowaniem tej konfiguracji.
+>> >
+>>
+>> Utwórz plik konfiguracyjny agregatu `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Następnie skonfiguruj każdy fizyczny interfejs. Edytuj `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Utwórz `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Utwórz `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Utwórz `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > W trybie Fully Private agregat używa adresu MAC interfejsu **głównego prywatnego**. Pole `IPADDR` powinno być ustawione na Twój prywatny adres IP vRack.
+>> >
+
+### Zastosowanie konfiguracji
+
+Zastosuj konfigurację, przeładowując wszystkie interfejsy za pomocą wicked:
```bash
wicked ifreload all
```
-Aby sprawdzić, czy agregacja ta działa, wykonaj ping do innego serwera w tej samej sieci vRack. Jeśli to działa, proces konfiguracji został zakończony. Jeśli tak się nie stanie, sprawdź swoje konfiguracje lub spróbuj zrestartować serwer.
+Restart może trwać kilka sekund, ponieważ tworzony jest interfejs agregatu. Aby sprawdzić, czy agregat działa prawidłowo, wyślij polecenie ping do innego serwera w tym samym vRack. Jeśli działa, wszystko jest gotowe. Jeśli nie, sprawdź konfiguracje lub spróbuj zrestartować serwer.
-Możesz również sprawdzić parametry używane w interfejsie ifcfg-bond0 za pomocą polecenia:
+Możesz również sprawdzić ustawienia agregatu za pomocą następującego polecenia:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Sprawdź również
-[Konfiguracja agregacji linków OLA w Panelu klienta](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Konfiguracja OVHcloud Link Aggregation w Panelu klienta OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 12 lub Ubuntu 24.04 z Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Jak skonfigurować identyfikator klienta do agregacji linków OVHcloud z systemem Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 9–11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Jak skonfigurować identyfikator klienta do agregacji linków OVHcloud w systemie Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Dołącz do [grona naszych użytkowników](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.pt-pt.md
index a059e7cd6e5..2528c2530e3 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15/guide.pt-pt.md
@@ -1,25 +1,40 @@
---
-title: "Como configurar o seu NIC para a agregação de ligações OVHcloud no SLES 15"
-excerpt: 'Ativar o OVHcloud Link Aggregation no seu servidor SLES 15'
-updated: 2024-11-26
+title: "Como configurar a NIC para o OVHcloud Link Aggregation no SLES 15"
+excerpt: "Ative a agregação de ligações no seu servidor SLES 15 para aumentar a disponibilidade do seu servidor e melhorar a eficiência das suas ligações de rede"
+updated: 2026-04-20
---
+
+
## Objetivo
-A tecnologia OVHcloud Link Aggregation (OLA) foi concebida pelas nossas equipas para aumentar a disponibilidade do seu servidor e melhorar a eficácia das suas ligações de rede. Em apenas alguns cliques, pode agregar as suas placas de rede e tornar as suas ligações de rede redundantes. Isto significa que, se uma ligação avariar, o tráfego é automaticamente redirecionado para outra ligação disponível.
+A tecnologia OVHcloud Link Aggregation (OLA) foi criada pelas nossas equipas para aumentar a disponibilidade do seu servidor e melhorar a eficiência das suas ligações de rede. Em apenas alguns cliques, pode agregar as suas placas de rede e tornar as suas ligações de rede redundantes. Isto significa que se uma ligação for interrompida, o tráfego é automaticamente redirecionado para outra ligação disponível. A largura de banda disponível é também duplicada graças à agregação.
+A agregação baseia-se na tecnologia IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
-**Saiba como reagrupar os seus NIC (Network Interface Controller) para os utilizar com o serviço OLA no SLES 15.**
+**Este guia explica como configurar as suas interfaces em agregação para as utilizar com OLA no SLES 15.**
## Requisitos
-- [Ter configurado o seu NIC para a funcionalidade OVHcloud Link Aggregation a partir da Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Configurar o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
### Acesso à Área de Cliente OVHcloud
-- **Link direto:** [Servidores dedicados](/links/control-panel/baremetal-dedicated-servers)
+- **Ligação direta:** [Servidores dedicados](/links/control-panel/baremetal-dedicated-servers)
- **Caminho de navegação:** `Bare Metal Cloud`{.action} > `Servidores dedicados`{.action} > Selecione o seu servidor
---
@@ -27,121 +42,301 @@ A tecnologia OVHcloud Link Aggregation (OLA) foi concebida pelas nossas equipas
## Instruções
-Uma vez que temos uma configuração privada para os nossos NIC em OLA, é impossível ligar-se ao servidor através de SSH. Assim, deverá utilizar a ferramenta IPMI para aceder ao servidor.
+A configuração private-private disponível no OLA para as nossas NIC não permite aceder ao servidor em SSH. Para aceder ao servidor, é necessário utilizar a ferramenta IPMI.
-A seguir, clique no separador `IPMI`{.action} (1) e no botão `A partir de applet Java (KVM)`{.action} (2).
+Clique no separador `IPMI`{.action} (1) e, em seguida, no botão `A partir de applet Java (KVM)`{.action} (2).
{.thumbnail}
Um programa JNLP será descarregado. Execute o software para aceder ao IPMI. Ligue-se utilizando as informações de identificação associadas ao servidor.
-Por predefinição, utilizando um modelo OVHcloud, os NIC serão designados por *eth0* e *eth1*. Se não utiliza um modelo OVHcloud, pode encontrar os nomes das suas interfaces utilizando o seguinte comando:
+Por predefinição, ao utilizar um modelo OVHcloud, os NIC serão designados por *eth0* e *eth1*. Se não utilizar um modelo OVHcloud, pode encontrar os nomes das suas interfaces com o seguinte comando:
```bash
ip a
```
> [!primary]
->
-> Este comando irá devolver várias "interfaces". Se tiver dificuldades em identificar os seus NIC físicos, a primeira interface terá sempre o endereço IP público do servidor atribuído por predefinição.
+> Os valores (endereços MAC, endereços IP, etc.) indicados nas configurações e exemplos abaixo são fornecidos a título de exemplo. Naturalmente, deve substituí-los pelos seus próprios valores.
>
-Depois de identificar os nomes dos seus dois NIC, é necessário criar o NIC bonding ou agregação de ligação no sistema operativo. Para isso, crie o ficheiro de interfaces no editor de texto à sua escolha através do seguinte comando:
+### Obtenção dos endereços MAC
-```bash
-vi/etc/sysconfig/network/ifcfg-bond0
-```
+Aceda à [Área de Cliente OVHcloud](/links/manager), vá à secção `Bare Metal Cloud`{.action} e selecione o seu servidor em **Servidores dedicados**.
-Isto abrirá um ficheiro de texto vazio. Para configurar a interface de agregação, insira as seguintes linhas no ficheiro de texto:
+Vá ao separador `Interfaces de rede`{.action} e tome nota dos endereços MAC de cada interface (pública/privada) que são apresentados na parte inferior do menu.
-```bash
-STARTMODE='onboot'
-BOOTPROTO='static'
-IPADDR='10.0.0.1/24'
-BONDING_MASTER='yes'
-BONDING_SLAVE_0='eth0'
-BONDING_SLAVE_1='eth1'
-BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4'
-```
+{.thumbnail}
> [!primary]
+> O endereço MAC da interface **pública principal** é o que recebe as ofertas DHCP, tanto no sistema operativo do servidor como no modo de recuperação. Esta interface gere a conectividade pública na configuração predefinida.
>
-> Pode utilizar qualquer endereço IP e sub-rede privada que deseje.
-> Se o seu servidor possuir mais do que 2 interfaces de rede, pode adicioná-las na configuração aumentando o número do parâmetro `BONDING_SLAVE_`, por exemplo, `BONDING_SLAVE_2='eth2'`.
+> Além disso, o endereço MAC da interface **privada principal** é o de valor mais baixo. Na imagem de exemplo acima, este é o endereço `a1:b2:c3:d4:e5:d6`.
>
-Guarde e saia o ficheiro assim que confirmar que a informação está correta. Agora tem de configurar as duas interfaces físicas. Por predefinição, para um servidor OVHcloud, só a *eth0* terá um ficheiro de configuração. Abra-o através do seguinte comando:
+Agora que sabe quais os endereços MAC associados a cada tipo de interface (pública/privada), deve obter os nomes das interfaces.
-```bash
-vi/etc/sysconfig/network/ifcfg-eth1
-```
-
-Por predefinição, o ficheiro exibirá o seguinte texto:
-
-```bash
-# Created by cloud-init on instance boot automatically, do not edit.
-#
-BOOTPROTO=dhcp4
-IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE=auto
-```
+### Obtenção dos nomes das interfaces
-> [!warning]
+> [!primary]
>
-> Os endereços IP serão diferentes para cada servidor.
+> Se perder a ligação de rede ao servidor, siga os passos "**Abrir KVM**" de [este guia](/pages/bare_metal_cloud/dedicated_servers/using_ipmi_on_dedicated_servers).
>
-Deve alterar este ficheiro para que este apresente o seguinte texto:
+Para obter os nomes das interfaces, execute o seguinte comando:
```bash
-BOOTPROTO='none'
-#IPADDR6=2001:41d0:408:dd00::/56
-LLADDR=10:70:fd:c5:14:00
-STARTMODE='hotplug'
+ip a
```
> [!primary]
>
-> O endereço de hardware (endereço MAC) do NIC pode ser encontrado através da encomenda `ip que` utilizou anteriormente. Será o número ao lado do `link/ether` do resultado apresentado.
+> Este comando irá produzir várias interfaces. Se tiver dificuldade em determinar quais são as suas interfaces físicas, a primeira interface ainda terá o endereço IP público do servidor associado por predefinição.
>
-O *#* à frente de uma linha indica que o servidor ignorará esta linha ao ler o ficheiro. Isto significa que estas linhas não serão tidas em conta ao criar o ficheiro de interface para *eth0*.
-
-Deverá criar o ficheiro de configuração *eth1* através do seguinte comando:
-
-```bash
-vi/etc/sysconfig/network/ifcfg-eth2
+Aqui tem um exemplo de saída:
+
+```text
+1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+ valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host noprefixroute
+ valid_lft forever preferred_lft forever
+2: ens22f0np0: mtu 1500 qdisc mq state UP group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c6 brd ff:ff:ff:ff:ff:ff
+ inet 203.0.113.1/32 metric 100 scope global dynamic ens22f0np0
+ valid_lft 71613sec preferred_lft 71613sec
+ inet6 2001:db8:1:1b00:203:0:112:0/56 scope global
+ valid_lft forever preferred_lft forever
+ inet6 fe80::a6b2:c3ff:fed4:e5c6/64 scope link
+ valid_lft forever preferred_lft forever
+3: ens22f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:c7 brd ff:ff:ff:ff:ff:ff
+4: ens33f0np0: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d6 brd ff:ff:ff:ff:ff:ff
+5: ens33f1np1: mtu 1500 qdisc noop state DOWN group default qlen 1000
+ link/ether a1:b2:c3:d4:e5:d7 brd ff:ff:ff:ff:ff:ff
```
-Desta vez, o ficheiro estará vazio. Deverá adicionar o seguinte conteúdo:
-
-```bash
-BOOTPROTO='none'
-STARTMODE='hotplug'
-LLADDR=0c:42:a1:a7:29:c2
-```
-
-Por fim, é necessário reiniciar o serviço de rede com o seguinte comando:
+Após determinar os nomes das suas interfaces, pode configurar a agregação de interfaces no sistema operativo.
+
+### Configuração da agregação de interfaces
+
+Selecione o separador seguinte que corresponde à configuração do seu servidor:
+
+- **Duas interfaces**: servidores Advance com duas NIC físicas.
+- **Quatro interfaces - Double LAG**: servidores Scale e High-Grade com OLA no modo **Active - Double LAG** (agregados público + privado). Requer a [ativação do OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) na Área de Cliente OVHcloud.
+- **Quatro interfaces - Fully Private**: servidores Scale e High-Grade com OLA no modo **Active - Fully Private** (único agregado privado para vRack). Requer a [ativação do OLA](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager) na Área de Cliente OVHcloud.
+
+> [!tabs]
+> Duas interfaces
+>> Crie o ficheiro de configuração do agregado `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **IP estático**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure cada interface física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Crie `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> /// details | DHCP
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Os ficheiros de configuração das interfaces físicas permanecem iguais ao descrito acima.
+>>
+>> ///
+>>
+> Quatro interfaces - Double LAG
+>> Esta configuração agrupa as interfaces públicas em `bond0` (com IP público) e as interfaces privadas em `bond1` (para vRack).
+>>
+>> Crie o ficheiro de configuração do agregado público `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> **IP estático**
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='203.0.113.1/32'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Crie o ficheiro de configuração do agregado privado `/etc/sysconfig/network/ifcfg-bond1`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens33f0np0'
+>> BONDING_SLAVE_1='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure cada interface física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Crie `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Crie `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Crie `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> /// details | DHCP (apenas bond0)
+>>
+>> Para o agregado público, utilize DHCP:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='dhcp4'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> O agregado privado (`ifcfg-bond1`) e todos os ficheiros de configuração das interfaces físicas permanecem iguais ao descrito acima.
+>>
+>> ///
+>>
+> Quatro interfaces - Fully Private
+>> Esta configuração agrega todas as interfaces físicas num único agregado exclusivamente para utilização com vRack. Não há conectividade IP pública.
+>>
+>> > [!warning]
+>> >
+>> > Após a implementação do OLA em modo Fully Private, o IP público deixa de estar acessível. Certifique-se de que dispõe de um meio alternativo de acesso (por exemplo, através de outro servidor no vRack ou via KVM/IPMI) antes de aplicar esta configuração.
+>> >
+>>
+>> Crie o ficheiro de configuração do agregado `/etc/sysconfig/network/ifcfg-bond0`:
+>>
+>> ```bash
+>> STARTMODE='onboot'
+>> BOOTPROTO='static'
+>> IPADDR='10.0.0.1/24'
+>> BONDING_MASTER='yes'
+>> BONDING_SLAVE_0='ens22f0np0'
+>> BONDING_SLAVE_1='ens22f1np1'
+>> BONDING_SLAVE_2='ens33f0np0'
+>> BONDING_SLAVE_3='ens33f1np1'
+>> BONDING_MODULE_OPTS='mode=802.3ad xmit_hash_policy=layer3+4 lacp_rate=fast'
+>> ```
+>>
+>> Configure cada interface física. Edite `/etc/sysconfig/network/ifcfg-ens22f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c6
+>> ```
+>>
+>> Crie `/etc/sysconfig/network/ifcfg-ens22f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:c7
+>> ```
+>>
+>> Crie `/etc/sysconfig/network/ifcfg-ens33f0np0`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d6
+>> ```
+>>
+>> Crie `/etc/sysconfig/network/ifcfg-ens33f1np1`:
+>>
+>> ```bash
+>> BOOTPROTO='none'
+>> STARTMODE='hotplug'
+>> LLADDR=a1:b2:c3:d4:e5:d7
+>> ```
+>>
+>> > [!primary]
+>> >
+>> > No modo Fully Private, o agregado utiliza o endereço MAC da interface **privada principal**. O campo `IPADDR` deve ser definido com o seu endereço IP privado de vRack.
+>> >
+
+### Aplicação da configuração
+
+Aplique a configuração recarregando todas as interfaces com wicked:
```bash
wicked ifreload all
```
-Para verificar que este agregado funciona, faça ping para outro servidor no mesmo vRack. Se isto funcionar, o processo de configuração estará concluído. Se não for o caso, verifique as suas configurações ou tente reiniciar o servidor.
+Este reinício pode levar vários segundos, uma vez que está a construir a interface de agregação. Para testar se o agregado está a funcionar, faça um ping noutro servidor da mesma rede vRack. Se funcionar, está tudo pronto. Caso contrário, volte a verificar as suas configurações ou tente reiniciar o servidor.
-Também pode verificar os parâmetros utilizados pela sua interface ifcfg-bond0 através do seguinte comando:
+Pode também verificar as definições do agregado com o seguinte comando:
```bash
-/proc/net/bonding/bond0
+cat /proc/net/bonding/bond0
```
## Saiba mais
-[Configurar a agregação das ligações OLA na sua Área de Cliente](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurar o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Como configurar a NIC para o OVHcloud Link Aggregation em Debian 12 ou Ubuntu 24.04 com Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Como configurar o seu NIC para a agregação de ligações OVHcloud em Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Como configurar a NIC para o OVHcloud Link Aggregation em Debian 9 a 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Como configurar o seu NIC para a agregação de ligações OVHcloud em Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19).
+[Como configurar a NIC para o OVHcloud Link Aggregation em Windows Server 2019](/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19)
Fale com nossa [comunidade de utilizadores](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.de-de.md
index 6ddf32b2b40..e806a1a347d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.de-de.md
@@ -1,21 +1,24 @@
---
-title: 'Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Windows Server 2019'
-excerpt: 'Erfahren Sie hier, wie Sie OLA auf Ihrem Windows Server 2019 Server aktivieren'
-updated: 2021-03-25
+title: "Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Link Aggregation auf Ihrem Windows-Server-2019-Server aktivieren, um die Verfügbarkeit Ihres Servers zu erhöhen und die Effizienz Ihrer Netzwerkverbindungen zu steigern"
+updated: 2026-04-20
---
## Ziel
-Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die Verfügbarkeit Ihres Servers zu erhöhen und die Effizienz Ihrer Netzwerkverbindungen zu steigern. Mit nur wenigen Klicks können Sie Ihre Netzwerkkarten aggregieren und Ihre Netzwerkverbindungen redundant machen. Wenn also eine Verbindung ausfällt, wird der Datenverkehr automatisch auf eine andere verfügbare Verbindung umgeleitet.
+Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die Verfügbarkeit Ihres Servers zu erhöhen und die Effizienz Ihrer Netzwerkverbindungen zu steigern. Mit nur wenigen Klicks können Sie Ihre Netzwerkkarten aggregieren und Ihre Netzwerkverbindungen redundant machen. Wenn also eine Verbindung ausfällt, wird der Datenverkehr automatisch auf eine andere verfügbare Verbindung umgeleitet. Die verfügbare Bandbreite wird durch Aggregation ebenfalls verdoppelt.
+Die Aggregation basiert auf dem Standard IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Diese Anleitung erklärt, wie Sie NIC Teaming für OLA in Windows Server 2019 konfigurieren.**
## Voraussetzungen
-- [Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation im OVHcloud Kundencenter](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [OVHcloud Link Aggregation im OVHcloud Kundencenter konfigurieren](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
-### Zugang zum OVHcloud Kundencenter
+### Zugriff auf das OVHcloud Kundencenter
- **Direktlink:** [Dedicated Server](/links/control-panel/baremetal-dedicated-servers)
- **Navigationspfad:** `Bare Metal Cloud`{.action} > `Dedicated Server`{.action} > Wählen Sie Ihren Server aus
@@ -26,26 +29,27 @@ Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die V
## In der praktischen Anwendung
Da wir für unsere NICs in OLA eine privat-private Konfiguration haben, können wir keine SSH-Verbindung zum Server herstellen. Daher müssen wir das IPMI-Tool nutzen, um auf den Server zuzugreifen.
+
Klicken Sie dazu auf den Tab `IPMI`{.action} (1).
-Klicken Sie auf den Tab `IPMI`{.action} (1) und dann auf die Schaltfläche `Mit einem Java-Applet (KVM)`{.action} (2).
+Klicken Sie anschließend auf den Button `Mit einem Java-Applet (KVM)`{.action} (2).
-{.thumbnail}
+{.thumbnail}
Ein JNLP-Applet wird heruntergeladen. Öffnen Sie es, um IPMI aufzurufen. Melden Sie sich mit gültigen Anmeldeinformationen für den Server an.
Sobald Sie auf dem Server sind, öffnen Sie den Server-Manager. Wenn er nicht bereits standardmäßig geöffnet wird, wird er an das Start-Menü angeheftet.
-{.thumbnail}
+{.thumbnail}
-Klicken Sie nach dem Öffnen des Server-Managers in der linken Seitenleiste auf **Lokaler Server**. Klicken Sie anschließend neben “NIC Teaming” auf die Schaltfläche **Deaktiviert**.
+Klicken Sie nach dem Öffnen des Server-Managers in der linken Seitenleiste auf **Lokaler Server**. Klicken Sie anschließend neben "NIC Teaming" auf die Schaltfläche **Deaktiviert**.
{.thumbnail}
-Klicken Sie im NIC-Teaming-Popup im Dropdown-Menü **AUFGABEN** im Abschnitt “TEAMS” auf die Schaltfläche **Neues Team**.
+Klicken Sie im NIC-Teaming-Popup im Dropdown-Menü **AUFGABEN** im Abschnitt "TEAMS" auf die Schaltfläche **Neues Team**.
{.thumbnail}
-Geben Sie Ihrem Team einen Namen und überprüfen Sie die NICs, die Sie mit OLA verwenden möchten. Klicken Sie auf den Dropdown-Pfeil neben “Weitere Eigenschaften” und ändern Sie den “Teaming-Modus” zu LACP. Klicken Sie auf **OK**, sobald Sie die Richtigkeit der Informationen bestätigt haben.
+Geben Sie Ihrem Team einen Namen und überprüfen Sie die NICs, die Sie mit OLA verwenden möchten. Klicken Sie auf den Dropdown-Pfeil neben "Weitere Eigenschaften" und ändern Sie den "Teaming-Modus" zu LACP. Klicken Sie auf **OK**, sobald Sie die Richtigkeit der Informationen bestätigt haben.
{.thumbnail}
@@ -69,14 +73,16 @@ Klicken Sie auf "Diese IP-Adresse verwenden" und fügen Sie Ihre gewählte priva
{.thumbnail}
-Um zu testen, ob unser NIC Team funktioniert, senden Sie einen Ping-Befehl an einen anderen Server im selben vRack. Wenn es funktioniert, sind Sie bereit. Ist dies nicht der Fall, überprüfen Sie Ihre Einstellungen oder starten Sie den Server neu.
+Um zu testen, ob das NIC-Team funktioniert, senden Sie einen Ping an einen anderen Server im selben vRack. Wenn es funktioniert, sind Sie fertig. Wenn nicht, überprüfen Sie Ihre Konfigurationen oder versuchen Sie, den Server neu zu starten.
## Weiterführende Informationen
-[Konfigurieren der OVHcloud Link Aggregation im OVHcloud Kundencenter](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[OVHcloud Link Aggregation im OVHcloud Kundencenter konfigurieren](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 12 oder Ubuntu 24.04 mit Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 9 bis 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Konfigurieren der OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
+[Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Treten Sie unserer [User Community](/links/community) bei.
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-asia.md
index c1bd6d6c1b2..944151e784d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-asia.md
@@ -1,12 +1,15 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019
-excerpt: Enable OVHcloud Link Aggregation in your "Windows Server 2019" server
-updated: 2021-03-25
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Enable OVHcloud Link Aggregation in your Windows Server 2019 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
+
+**This guide explains how to configure NIC Teaming for OLA in Windows Server 2019.**
## Requirements
@@ -26,8 +29,9 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+
To do so, click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -73,10 +77,12 @@ To test that your NIC team is working, ping another server on the same vRack. I
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-au.md
index c1bd6d6c1b2..944151e784d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-au.md
@@ -1,12 +1,15 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019
-excerpt: Enable OVHcloud Link Aggregation in your "Windows Server 2019" server
-updated: 2021-03-25
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Enable OVHcloud Link Aggregation in your Windows Server 2019 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
+
+**This guide explains how to configure NIC Teaming for OLA in Windows Server 2019.**
## Requirements
@@ -26,8 +29,9 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+
To do so, click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -73,10 +77,12 @@ To test that your NIC team is working, ping another server on the same vRack. I
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-ca.md
index c1bd6d6c1b2..944151e784d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-ca.md
@@ -1,12 +1,15 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019
-excerpt: Enable OVHcloud Link Aggregation in your "Windows Server 2019" server
-updated: 2021-03-25
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Enable OVHcloud Link Aggregation in your Windows Server 2019 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
+
+**This guide explains how to configure NIC Teaming for OLA in Windows Server 2019.**
## Requirements
@@ -26,8 +29,9 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+
To do so, click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -73,10 +77,12 @@ To test that your NIC team is working, ping another server on the same vRack. I
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-gb.md
index dc748d71a56..944151e784d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-gb.md
@@ -1,12 +1,15 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019
-excerpt: Enable OVHcloud Link Aggregation in your "Windows Server 2019" server
-updated: 2021-03-25
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Enable OVHcloud Link Aggregation in your Windows Server 2019 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
+
+**This guide explains how to configure NIC Teaming for OLA in Windows Server 2019.**
## Requirements
@@ -74,10 +77,12 @@ To test that your NIC team is working, ping another server on the same vRack. I
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-ie.md
index c1bd6d6c1b2..944151e784d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-ie.md
@@ -1,12 +1,15 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019
-excerpt: Enable OVHcloud Link Aggregation in your "Windows Server 2019" server
-updated: 2021-03-25
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Enable OVHcloud Link Aggregation in your Windows Server 2019 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
+
+**This guide explains how to configure NIC Teaming for OLA in Windows Server 2019.**
## Requirements
@@ -26,8 +29,9 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+
To do so, click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -73,10 +77,12 @@ To test that your NIC team is working, ping another server on the same vRack. I
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-sg.md
index c1bd6d6c1b2..944151e784d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-sg.md
@@ -1,12 +1,15 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019
-excerpt: Enable OVHcloud Link Aggregation in your "Windows Server 2019" server
-updated: 2021-03-25
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Enable OVHcloud Link Aggregation in your Windows Server 2019 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
+
+**This guide explains how to configure NIC Teaming for OLA in Windows Server 2019.**
## Requirements
@@ -26,8 +29,9 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+
To do so, click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -73,10 +77,12 @@ To test that your NIC team is working, ping another server on the same vRack. I
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-us.md
index c1bd6d6c1b2..944151e784d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.en-us.md
@@ -1,12 +1,15 @@
---
-title: How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019
-excerpt: Enable OVHcloud Link Aggregation in your "Windows Server 2019" server
-updated: 2021-03-25
+title: "How to Configure Your NIC for OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Enable OVHcloud Link Aggregation in your Windows Server 2019 server to increase your server's availability and boost the efficiency of your network connections"
+updated: 2026-04-20
---
## Objective
-OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server’s availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link.
+OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase your server's availability, and boost the efficiency of your network connections. In just a few clicks, you can aggregate your network cards and make your network links redundant. This means that if one link goes down, traffic is automatically redirected to another available link. The available bandwidth is also doubled thanks to aggregation.
+Aggregation is based on IEEE 802.3ad, Link Aggregation Control Protocol (LACP) technology.
+
+**This guide explains how to configure NIC Teaming for OLA in Windows Server 2019.**
## Requirements
@@ -26,8 +29,9 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
## Instructions
Because you have a private-private configuration for your NICs in OLA, you will be unable to SSH into the server. Thus, you will need to leverage the IPMI tool to access the server.
+
To do so, click the `IPMI`{.action} tab (1).
-Click the `IPMI`{.action} tab (1) and then click the `From a Java applet (KVM)`{.action} button (2).
+Next, click the `From a Java applet (KVM)`{.action} button (2).
{.thumbnail}
@@ -73,10 +77,12 @@ To test that your NIC team is working, ping another server on the same vRack. I
## Go further
-[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configuring OVHcloud Link Aggregation in the OVHcloud Control Panel](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 12 or Ubuntu 24.04 using Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[How to Configure Your NIC for OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[How to configure your NIC for OVHcloud Link Aggregation in Debian 9 to 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[How to Configure Your NIC for OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.es-es.md
index 8476f313b7d..c5bb35952c2 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.es-es.md
@@ -1,16 +1,19 @@
---
-title: 'Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019'
-excerpt: 'Activar el servicio OVHcloud Link Aggregation en un servidor «Windows Server 2019»'
-updated: 2021-03-25
+title: "Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019"
+excerpt: "Active la agregación de enlaces en su servidor Windows Server 2019 para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red"
+updated: 2026-04-20
---
## Objetivo
-La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible.
+La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible. El ancho de banda disponible también se duplica gracias a la agregación.
+La agregación se basa en la tecnología IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Esta guía explica cómo configurar NIC Teaming para OLA en Windows Server 2019.**
## Requisitos
-- [Configurar un NIC para el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -26,26 +29,27 @@ La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la
## Procedimiento
Nuestros NIC en OLA tienen una configuración privada-privada, por lo que no es posible acceder al servidor por SSH. Así pues, es necesario utilizar la herramienta IPMI para acceder al servidor.
+
Para ello, haga clic en la pestaña `IPMI`{.action} (1).
-Abra la pestaña `IPMI`{.action} (1) y haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
+A continuación, haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
-{.thumbnail}
+{.thumbnail}
-Se descargará un programa JNLP. Abra el programa una vez descargado para acceder a IPMI e introduzca las claves asociadas al servidor.
+Se descargará un programa JNLP. Abra el programa una vez descargado para acceder a IPMI e introduzca las claves asociadas al servidor.
Una vez dentro del servidor, abra el gestor de servidor. Si no aparece abierto por defecto, lo podrá ver anclado al menú Inicio.
{.thumbnail}
-Una vez haya abierto el gestor de servidor, haga clic en la pestaña **Servidor Local** en el menú de la izquierda. Haga clic en el botón **Deshabilitado** junto a «NIC Teaming.»
+Una vez haya abierto el gestor de servidor, haga clic en la pestaña **Servidor Local** en el menú de la izquierda. Haga clic en el botón **Deshabilitado** junto a "NIC Teaming."
{.thumbnail}
-En la ventana emergente de NIC Teaming, haga clic en el botón ««Nuevo Equipo»» del menú desplegable **TAREAS** en la sección «EQUIPOS».
+En la ventana emergente de NIC Teaming, haga clic en el botón **Nuevo Equipo** del menú desplegable **TAREAS** en la sección "EQUIPOS".
{.thumbnail}
-Asigne un nombre a su equipo y compruebe los NIC que quiere usar con el servicio OLA. Haga clic en la flecha desplegable junto a «Propiedades adicionales» y cambie el «Modo Teaming» a LACP. Una vez que haya confirmado que la información es correcta, haga clic en **OK**.
+Asigne un nombre a su equipo y compruebe los NIC que quiere usar con el servicio OLA. Haga clic en la flecha desplegable junto a "Propiedades adicionales" y cambie el "Modo Teaming" a LACP. Una vez que haya confirmado que la información es correcta, haga clic en **OK**.
{.thumbnail}
@@ -65,7 +69,7 @@ En la ventana emergente siguiente, haga doble clic en el botón **Protocolo de I
{.thumbnail}
-Haga clic en el botón junto a «Utilizar la siguiente dirección IP» y añada la IP privada y la subred que haya elegido. Haga clic en **OK** una vez haya confirmado que la configuración es correcta.
+Haga clic en el botón junto a "Utilizar la siguiente dirección IP" y añada la IP privada y la subred que haya elegido. Haga clic en **OK** una vez haya confirmado que la configuración es correcta.
{.thumbnail}
@@ -73,9 +77,11 @@ Para comprobar que el equipo NIC funciona correctamente, haga ping en otro servi
## Más información
-[Configurar el servicio OVHcloud Link Aggregation desde el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 9 a 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
[Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.es-us.md
index 8476f313b7d..c5bb35952c2 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.es-us.md
@@ -1,16 +1,19 @@
---
-title: 'Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019'
-excerpt: 'Activar el servicio OVHcloud Link Aggregation en un servidor «Windows Server 2019»'
-updated: 2021-03-25
+title: "Configurar un NIC para el servicio OVHcloud Link Aggregation en Windows Server 2019"
+excerpt: "Active la agregación de enlaces en su servidor Windows Server 2019 para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red"
+updated: 2026-04-20
---
## Objetivo
-La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible.
+La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la disponibilidad de su servidor y mejorar la eficiencia de sus conexiones de red. En solo unos clics, es posible añadir sus tarjetas de red y hacer que sus enlaces de red sean redundantes. De este modo, si un enlace se cae, el tráfico se redirige automáticamente hacia otro enlace disponible. El ancho de banda disponible también se duplica gracias a la agregación.
+La agregación se basa en la tecnología IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Esta guía explica cómo configurar NIC Teaming para OLA en Windows Server 2019.**
## Requisitos
-- [Configurar un NIC para el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+- [Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -26,26 +29,27 @@ La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la
## Procedimiento
Nuestros NIC en OLA tienen una configuración privada-privada, por lo que no es posible acceder al servidor por SSH. Así pues, es necesario utilizar la herramienta IPMI para acceder al servidor.
+
Para ello, haga clic en la pestaña `IPMI`{.action} (1).
-Abra la pestaña `IPMI`{.action} (1) y haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
+A continuación, haga clic en el botón `Desde un applet Java (KVM)`{.action} (2).
-{.thumbnail}
+{.thumbnail}
-Se descargará un programa JNLP. Abra el programa una vez descargado para acceder a IPMI e introduzca las claves asociadas al servidor.
+Se descargará un programa JNLP. Abra el programa una vez descargado para acceder a IPMI e introduzca las claves asociadas al servidor.
Una vez dentro del servidor, abra el gestor de servidor. Si no aparece abierto por defecto, lo podrá ver anclado al menú Inicio.
{.thumbnail}
-Una vez haya abierto el gestor de servidor, haga clic en la pestaña **Servidor Local** en el menú de la izquierda. Haga clic en el botón **Deshabilitado** junto a «NIC Teaming.»
+Una vez haya abierto el gestor de servidor, haga clic en la pestaña **Servidor Local** en el menú de la izquierda. Haga clic en el botón **Deshabilitado** junto a "NIC Teaming."
{.thumbnail}
-En la ventana emergente de NIC Teaming, haga clic en el botón ««Nuevo Equipo»» del menú desplegable **TAREAS** en la sección «EQUIPOS».
+En la ventana emergente de NIC Teaming, haga clic en el botón **Nuevo Equipo** del menú desplegable **TAREAS** en la sección "EQUIPOS".
{.thumbnail}
-Asigne un nombre a su equipo y compruebe los NIC que quiere usar con el servicio OLA. Haga clic en la flecha desplegable junto a «Propiedades adicionales» y cambie el «Modo Teaming» a LACP. Una vez que haya confirmado que la información es correcta, haga clic en **OK**.
+Asigne un nombre a su equipo y compruebe los NIC que quiere usar con el servicio OLA. Haga clic en la flecha desplegable junto a "Propiedades adicionales" y cambie el "Modo Teaming" a LACP. Una vez que haya confirmado que la información es correcta, haga clic en **OK**.
{.thumbnail}
@@ -65,7 +69,7 @@ En la ventana emergente siguiente, haga doble clic en el botón **Protocolo de I
{.thumbnail}
-Haga clic en el botón junto a «Utilizar la siguiente dirección IP» y añada la IP privada y la subred que haya elegido. Haga clic en **OK** una vez haya confirmado que la configuración es correcta.
+Haga clic en el botón junto a "Utilizar la siguiente dirección IP" y añada la IP privada y la subred que haya elegido. Haga clic en **OK** una vez haya confirmado que la configuración es correcta.
{.thumbnail}
@@ -73,9 +77,11 @@ Para comprobar que el equipo NIC funciona correctamente, haga ping en otro servi
## Más información
-[Configurar el servicio OVHcloud Link Aggregation desde el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[Configurar el servicio OVHcloud Link Aggregation en el área de cliente de OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Configurar un NIC para el servicio OVHcloud Link Aggregation en Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+[Cómo configurar la NIC para OVHcloud Link Aggregation en Debian 9 a 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
[Configurar un NIC para el servicio OVHcloud Link Aggregation en SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.fr-ca.md
index 96ddde7b068..48842372bab 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.fr-ca.md
@@ -1,12 +1,15 @@
---
-title: 'Configurer votre NIC pour la fonctionnalité OVHcloud Link Aggregation sur Windows Server 2019'
-excerpt: 'Activer OVHcloud Link Aggregation sur votre serveur « Windows Server 2019 »'
-updated: 2021-03-25
+title: "Comment configurer votre NIC pour OVHcloud Link Aggregation sous Windows Server 2019"
+excerpt: "Activez l'agrégation de liens OVHcloud sur votre serveur Windows Server 2019 pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau"
+updated: 2026-04-20
---
## Objectif
-La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible.
+La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible. La bande passante disponible est également doublée grâce à l'agrégation.
+L'agrégation est basée sur la technologie IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Ce guide explique comment configurer le NIC Teaming pour OLA sous Windows Server 2019.**
## Prérequis
@@ -26,8 +29,7 @@ La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour
## En pratique
Étant donné que nous avons une configuration privée-privée pour nos NIC sur OLA, il est impossible de se connecter en SSH au serveur. Par conséquent, vous devrez utiliser l’outil IPMI pour accéder au serveur.
-
-Cliquez ensuite sur l’onglet `IPMI`{.action} (1) puis sur le bouton `Depuis un applet Java (KVM)`{.action} (2).
+
Pour cela, cliquez sur l’onglet `IPMI`{.action} (1) puis sur le bouton `Depuis un applet Java (KVM)`{.action} (2).
{.thumbnail}
@@ -73,10 +75,12 @@ Pour vérifier que votre équipe NIC fonctionne, effectuez un ping vers un autre
## Aller plus loin
-[Configurer l’agrégation de liens OLA dans votre espace client](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurer l'agrégation de liens OLA dans votre espace client](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Comment configurer votre NIC pour OVHcloud Link Aggregation sous Debian 12 ou Ubuntu 24.04 avec Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 à 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[Comment configurer votre NIC pour OVHcloud Link Aggregation sous SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.fr-fr.md
index 5bd7cdd5c2e..48842372bab 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.fr-fr.md
@@ -1,12 +1,15 @@
---
-title: 'Configurer votre NIC pour la fonctionnalité OVHcloud Link Aggregation sur Windows Server 2019'
-excerpt: 'Activer OVHcloud Link Aggregation sur votre serveur « Windows Server 2019 »'
-updated: 2021-03-25
+title: "Comment configurer votre NIC pour OVHcloud Link Aggregation sous Windows Server 2019"
+excerpt: "Activez l'agrégation de liens OVHcloud sur votre serveur Windows Server 2019 pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau"
+updated: 2026-04-20
---
## Objectif
-La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible.
+La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour augmenter la disponibilité de votre serveur et améliorer l'efficacité de vos connexions réseau. En quelques clics, vous pouvez agréger vos cartes réseau et rendre vos liaisons réseau redondantes. Cela signifie que si une liaison tombe en panne, le trafic est automatiquement redirigé vers une autre liaison disponible. La bande passante disponible est également doublée grâce à l'agrégation.
+L'agrégation est basée sur la technologie IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Ce guide explique comment configurer le NIC Teaming pour OLA sous Windows Server 2019.**
## Prérequis
@@ -72,10 +75,12 @@ Pour vérifier que votre équipe NIC fonctionne, effectuez un ping vers un autre
## Aller plus loin
-[Configurer l’agrégation de liens OLA dans votre espace client](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurer l'agrégation de liens OLA dans votre espace client](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Comment configurer votre NIC pour OVHcloud Link Aggregation sous Debian 12 ou Ubuntu 24.04 avec Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Comment configurer votre NIC pour l'agrégation de liens OVHcloud sous Debian 9 à 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Comment configurer votre NIC pour l’agrégation de liens OVHcloud dans SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[Comment configurer votre NIC pour OVHcloud Link Aggregation sous SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.it-it.md
index b5e4023c1d3..c3a2e6b5a3a 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.it-it.md
@@ -1,16 +1,19 @@
---
-title: 'Configurare un NIC per il servizio OVHcloud Link Aggregation in Windows Server 2019'
-excerpt: "Attivare l'opzione OVHcloud Link Aggregation sul tuo server Windows Server 2019"
-updated: 2021-03-25
+title: "Configurare un NIC per il servizio OVHcloud Link Aggregation in Windows Server 2019"
+excerpt: "Attiva l'aggregazione di collegamenti sul tuo server Windows Server 2019 per aumentare la disponibilità del tuo server e migliorare l'efficienza delle tue connessioni di rete"
+updated: 2026-04-20
---
## Obiettivo
-La tecnologia OVHcloud Link Aggregation (OLA) è stata progettata dai team OVHcloud per aumentare la disponibilità dei server e potenziare le connessioni di rete. L’attivazione dell’opzione permette di aggregare in pochi click le schede di rete e rendere i collegamenti ridondati in modo che, in caso di malfunzionamenti, il traffico venga reindirizzato automaticamente verso il collegamento disponibile.
+La tecnologia OVHcloud Link Aggregation (OLA) è stata progettata dai team OVHcloud per aumentare la disponibilità dei server e potenziare le connessioni di rete. L'attivazione dell'opzione permette di aggregare in pochi click le schede di rete e rendere i collegamenti ridondati in modo che, in caso di malfunzionamenti, il traffico venga reindirizzato automaticamente verso il collegamento disponibile. La larghezza di banda disponibile viene anche raddoppiata grazie all'aggregazione.
+L'aggregazione si basa sulla tecnologia IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Questa guida spiega come configurare NIC Teaming per OLA in Windows Server 2019.**
## Prerequisiti
-- [Configurare un NIC per il servizio OVHcloud Link Aggregation nello Spazio Cliente](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Configurare OVHcloud Link Aggregation nello Spazio Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
@@ -25,13 +28,14 @@ La tecnologia OVHcloud Link Aggregation (OLA) è stata progettata dai team OVHcl
## Procedura
-Il tipo di configurazione disponibile in OLA per i nostri NIC non permette di accedere al server in SSH. Per stabilire la connessione alla macchina è quindi necessario utilizzare IPMI.
+Poiché la configurazione dei NIC in OLA è di tipo privato-privato, non sarà possibile accedere al server in SSH. Sarà quindi necessario utilizzare lo strumento IPMI per accedere al server.
+
Per farlo, clicca sulla scheda `IPMI`{.action} (1).
-Clicca sulla scheda `IPMI`{.action} (1) e poi sul pulsante `Da una applet Java (KVM)`{.action} (2).
+Clicca poi sul pulsante `Da una applet Java (KVM)`{.action} (2).
-{.thumbnail}
+{.thumbnail}
-Verrà scaricato un programma JNLP: aprilo e utilizza le credenziali associate al server per accedere.
+Verrà scaricato un software JNLP. Avvialo per accedere all'IPMI. Accedi utilizzando le informazioni di identificazione associate al server.
Una volta effettuato il login alla macchina, apri Server Manager (se non si apre di default, è disponibile nel menu **Start**).
@@ -49,7 +53,7 @@ Assegna un nome al team e spunta i NIC da utilizzare con OLA. Clicca sulla frecc
{.thumbnail}
-Potrebbero essere necessari un paio di minuti prima che il team NIC risulti online. Una volta terminato, clicca sull’icona della connessione di rete in basso a destra e poi sul pulsante `Network & Internet settings`{.action}. Seleziona **Ethernet** nella barra laterale sinistra.
+Potrebbero essere necessari un paio di minuti prima che il team NIC risulti online. Una volta terminato, clicca sull'icona della connessione di rete in basso a destra e poi sul pulsante `Network & Internet settings`{.action}. Seleziona **Ethernet** nella barra laterale sinistra.
{.thumbnail}
@@ -65,7 +69,7 @@ Nella nuova finestra, clicca due volte su `Internet Protocol Version 4 (TCP/IPv4
{.thumbnail}
-Seleziona `Use the following IP address`{.action} e aggiungi l’IP privato e la sottorete scelta. Una volta verificata la correttezza delle impostazioni, clicca su `OK`{.action}.
+Seleziona `Use the following IP address`{.action} e aggiungi l'IP privato e la sottorete scelta. Una volta verificata la correttezza delle impostazioni, clicca su `OK`{.action}.
{.thumbnail}
@@ -73,10 +77,12 @@ Per testare il corretto funzionamento del nuovo NIC team creato, effettua il pin
## Per saperne di più
-[Configurare un NIC per il servizio OVHcloud Link Aggregation nello Spazio Cliente](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager).
+[Configurare OVHcloud Link Aggregation nello Spazio Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Come configurare la NIC per OVHcloud Link Aggregation in Debian 12 o Ubuntu 24.04 con Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Configurare un NIC per il servizio OVHcloud Link Aggregation in Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+[Configurare un NIC per il servizio OVHcloud Link Aggregation in Debian 9 a 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Configurare un NIC per il servizio OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15).
+[Configurare un NIC per il servizio OVHcloud Link Aggregation in SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Contatta la nostra [Community di utenti](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.pl-pl.md
index 9ee06efa9d8..195edb5b7fe 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.pl-pl.md
@@ -1,35 +1,39 @@
---
-title: 'Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Windows Server 2019'
-excerpt: 'Dowiedz się, jak włączyć OVHcloud Link Aggregation na serwerze Windows Server 2019'
-updated: 2021-03-25
+title: "Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Windows Server 2019"
+excerpt: "Aktywuj agregację łączy na serwerze Windows Server 2019, aby zwiększyć dostępność serwera i wydajność połączeń sieciowych"
+updated: 2026-04-20
---
## Wprowadzenie
-Technologia OVHcloud Link Aggregation (OLA) została przez nas zaprojektowana w celu zwiększenia dostępności serwera oraz podniesienia wydajności połączeń sieciowych. Możesz w prosty sposób przeprowadzić agregację kart sieciowych, dzięki czemu Twoje połączenia sieciowe staną się redundantne. Jeśli jedno połączenie zostanie zerwane, ruch zostanie automatycznie przekierowany do innego dostępnego łącza.
+Technologia OVHcloud Link Aggregation (OLA) została zaprojektowana przez nasze zespoły w celu zwiększenia dostępności serwera oraz podniesienia wydajności połączeń sieciowych. Za pomocą kilku kliknięć możesz połączyć karty sieciowe i sprawić, że Twoje połączenia sieciowe staną się redundantne. Oznacza to, że jeśli jedno połączenie zostanie zerwane, ruch zostanie automatycznie przekierowany do innego dostępnego łącza. Dostępna przepustowość jest również podwajana dzięki agregacji.
+Agregacja oparta jest na technologii IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Niniejszy przewodnik wyjaśnia, jak skonfigurować NIC Teaming dla OLA w Windows Server 2019.**
## Wymagania początkowe
-- [Konfiguracja karty sieciowej dla OVHcloud Link Aggregation w Panelu klienta](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Konfiguracja OVHcloud Link Aggregation w Panelu klienta OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
### Dostęp do Panelu klienta OVHcloud
-- **Bezpośredni link:** [Serwery dedykowane](/links/control-panel/baremetal-dedicated-servers)
-- **Ścieżka nawigacji:** `Bare Metal Cloud`{.action} > `Serwery dedykowane`{.action} > Wybierz swój serwer
+- **Link bezpośredni:** [Serwery dedykowane](/links/control-panel/baremetal-dedicated-servers)
+- **Ścieżka nawigacji:** `Bare Metal Cloud`{.action} > `Serwery dedykowane`{.action} > Wybierz serwer
---
## W praktyce
-Ponieważ konfiguracja kart sieciowych w OLA jest prywatna, nie będziesz mógł połączyć się z serwerem za pomocą SSH. W związku z tym do uzyskania dostępu do serwera użyj narzędzia IPMI.
+Ponieważ konfiguracja kart sieciowych w OLA jest prywatna, nie będziesz mógł połączyć się z serwerem za pomocą SSH. W związku z tym do uzyskania dostępu do serwera użyj narzędzia IPMI.
+
W tym celu kliknij zakładkę `IPMI`{.action} (1).
-Kliknij zakładkę `IPMI`{.action} (1), a następnie przycisk `Z apletu Java (KVM)`{.action} (2).
+Następnie kliknij przycisk `Z apletu Java (KVM)`{.action} (2).
-{.thumbnail}
+{.thumbnail}
Zostanie pobrany program JNLP. Następnie otwórz program, aby skorzystać z połączenia IPMI. Zaloguj się, używając aktualnych danych do logowania do serwera.
@@ -61,26 +65,24 @@ Następnie kliknij prawym przyciskiem myszy zespół kart sieciowych (NIC) i wyb
{.thumbnail}
-W następnym oknie dialogowym, które się pojawi kliknij dwukrotnie przycisk **Internet Protocol Version 4 (TCP/IPv4)**.
+W następnym oknie dialogowym, które się pojawi kliknij dwukrotnie przycisk **Internet Protocol Version 4 (TCP/IPv4)**.
{.thumbnail}
-Kliknij przycisk obok "Use the following IP address i dodaj wybrany przez Ciebie prywatny adres IP oraz podsieć. Po sprawdzeniu poprawności ustawień kliknij przycisk **OK**.
+Kliknij przycisk obok "Use the following IP address" i dodaj wybrany przez Ciebie prywatny adres IP oraz podsieć. Po sprawdzeniu poprawności ustawień kliknij przycisk **OK**.
{.thumbnail}
-Aby sprawdzić, czy zespół kart sieciowych działa, podłącz inny serwer do tego samego vRacka. Jeśli wszystko działa poprawnie, ustawienie jest prawidłowe. W przeciwnym razie sprawdź dokładnie Twoje konfiguracje lub spróbuj zrestartować serwer.
-
-## Podsumowanie
-
-OVHcloud zapewnia klientom swobodę i elastyczność wykorzystania sprzętu w sposób najlepiej odpowiadający ich potrzebom. Po przeczytaniu tego przewodnika będziesz potrafił skonfigurować OVHcloud Link Aggregation (OLA) w Windows Server 2019 w celu wykorzystania obu kart sieciowych jako powiązanych interfejsów prywatnych.
+Aby sprawdzić, czy zespół kart sieciowych działa, wyślij polecenie ping do innego serwera w tym samym vRack. Jeśli działa, wszystko jest gotowe. W przeciwnym razie sprawdź konfiguracje lub spróbuj zrestartować serwer.
## Sprawdź również
-[Konfiguracja OVHcloud Link Aggregation w Panelu klienta](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[Konfiguracja OVHcloud Link Aggregation w Panelu klienta OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+
+[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 12 lub Ubuntu 24.04 z Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 9–11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
[Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
-Dołącz do [grona naszych użytkowników](/links/community).
\ No newline at end of file
+Dołącz do [grona naszych użytkowników](/links/community).
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.pt-pt.md
index 90d426cf703..aee30e8c682 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-w2k19/guide.pt-pt.md
@@ -1,23 +1,26 @@
---
-title: 'Como configurar a NIC para o OVHcloud Link Aggregation em Windows Server 2019'
-excerpt: 'Ative o OVHcloud Link Aggregation no seu servidor Windows Server 2019'
-updated: 2021-03-25
+title: "Como configurar a NIC para o OVHcloud Link Aggregation em Windows Server 2019"
+excerpt: "Ative a agregação de ligações no seu servidor Windows Server 2019 para aumentar a disponibilidade do seu servidor e melhorar a eficiência das suas ligações de rede"
+updated: 2026-04-20
---
-## Sumário
+## Objetivo
-A tecnologia OVHcloud Link Aggregation (OLA) foi criada pelas nossas equipas para aumentar a disponibilidade do seu servidor e aumentar a eficiência das suas ligações de rede. Em apenas alguns cliques, pode agregar as suas placas de rede e tornar as suas ligações de rede redundantes. Isto significa que se uma ligação for interrompida, o tráfego é automaticamente redirecionado para outra ligação disponível.
+A tecnologia OVHcloud Link Aggregation (OLA) foi criada pelas nossas equipas para aumentar a disponibilidade do seu servidor e melhorar a eficiência das suas ligações de rede. Em apenas alguns cliques, pode agregar as suas placas de rede e tornar as suas ligações de rede redundantes. Isto significa que se uma ligação for interrompida, o tráfego é automaticamente redirecionado para outra ligação disponível. A largura de banda disponível é também duplicada graças à agregação.
+A agregação baseia-se na tecnologia IEEE 802.3ad, Link Aggregation Control Protocol (LACP).
+
+**Este guia explica como configurar o NIC Teaming para OLA em Windows Server 2019.**
## Requisitos
-- [Como configurar a NIC para o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+- [Configurar o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
---
### Acesso à Área de Cliente OVHcloud
-- **Link direto:** [Servidores dedicados](/links/control-panel/baremetal-dedicated-servers)
+- **Ligação direta:** [Servidores dedicados](/links/control-panel/baremetal-dedicated-servers)
- **Caminho de navegação:** `Bare Metal Cloud`{.action} > `Servidores dedicados`{.action} > Selecione o seu servidor
---
@@ -26,26 +29,27 @@ A tecnologia OVHcloud Link Aggregation (OLA) foi criada pelas nossas equipas par
## Instruções
A configuração private-private disponível no OLA para as nossas NIC não permite aceder ao servidor em SSH. Para aceder ao servidor, é necessário utilizar a ferramenta IPMI.
+
Para tal, clique no separador `IPMI`{.action} (1).
-Clique no separador `IPMI`{.action} (1) e depois no botão `A partir de applet java (KVM)`{.action} (2).
+Em seguida, clique no botão `A partir de applet Java (KVM)`{.action} (2).
-{.thumbnail}
+{.thumbnail}
-Um programa JNLP será descarregado: Abra-o e introduza as credenciais associadas ao servidor.
+Um programa JNLP será descarregado. Abra-o e introduza as credenciais associadas ao servidor.
Uma vez efetuado o login, abra o Server Manager (se não abriu por predefinição, está disponível no menu Start).
{.thumbnail}
-A seguir, clique no separador **Local Server** à esquerda e, a seguir, em **Disabled** junto de “NIC Teaming”.
+A seguir, clique no separador **Local Server** à esquerda e, a seguir, em **Disabled** junto de "NIC Teaming".
{.thumbnail}
-Na nova janela, clique em “**TASKS** na secção “TEAMS” e selecione “New Team” no menu pendente.
+Na nova janela, clique em **TASKS** na secção "TEAMS" e selecione **New Team** no menu pendente.
{.thumbnail}
-Dê um nome à equipa e verifique as NIC a utilizar com o OLA. Clique na seta descendente junto de “Additional properties” e modifique o “Teaming mode” em LACP. Clique em **OK** depois de confirmar que a informação está correta.
+Dê um nome à equipa e verifique as NIC a utilizar com o OLA. Clique na seta descendente junto de "Additional properties" e modifique o "Teaming mode" em LACP. Clique em **OK** depois de confirmar que a informação está correta.
{.thumbnail}
@@ -65,18 +69,20 @@ Na nova janela, clique duas vezes em **Internet Protocol Version 4 (TCP/IPv4)**.
{.thumbnail}
-Clique em “Use the following IP address” e adicione o IP privado e a subrede. Clique em **OK** depois de confirmar que as configurações estão corretas.
+Clique em "Use the following IP address" e adicione o IP privado e a subrede. Clique em **OK** depois de confirmar que as configurações estão corretas.
{.thumbnail}
Para testar se a equipa NIC está a funcionar, faça um teste de ping noutro servidor da mesma rede vRack. Se funcionar, está tudo pronto. Caso contrário, volte a verificar as suas configurações ou tente reiniciar o servidor.
-## Quer saber mais?
+## Saiba mais
+
+[Configurar o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
-[Como configurar a NIC para o OVHcloud Link Aggregation na Área de Cliente OVHcloud](/pages/bare_metal_cloud/dedicated_servers/ola-enable-manager)
+[Como configurar a NIC para o OVHcloud Link Aggregation em Debian 12 ou Ubuntu 24.04 com Netplan](/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan)
-[Como configurar a NIC para o OVHcloud Link Aggregation em Debian 9](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
+[Como configurar a NIC para o OVHcloud Link Aggregation em Debian 9 a 11](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9)
-[Como configurar a NIC para o OVHcloud Link Aggregation em SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
+[Como configurar a NIC para o OVHcloud Link Aggregation em SLES 15](/pages/bare_metal_cloud/dedicated_servers/ola-enable-sles15)
Fale com nossa [comunidade de utilizadores](/links/community).