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 8ebee06cb1b..f2bf53354d1 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-asia.md
index 895dfbb7d4f..d42b99680de 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: "How to configure Link Aggregation with LACP in Debian 12 or Ubuntu 24.04"
 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-au.md
index 895dfbb7d4f..d42b99680de 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: "How to configure Link Aggregation with LACP in Debian 12 or Ubuntu 24.04"
 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-ca.md
index 895dfbb7d4f..d42b99680de 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "How to configure Link Aggregation with LACP in Debian 12 or Ubuntu 24.04"
 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-gb.md
index 895dfbb7d4f..d42b99680de 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "How to configure Link Aggregation with LACP in Debian 12 or Ubuntu 24.04"
 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-ie.md
index 895dfbb7d4f..d42b99680de 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: "How to configure Link Aggregation with LACP in Debian 12 or Ubuntu 24.04"
 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-sg.md
index 895dfbb7d4f..d42b99680de 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: "How to configure Link Aggregation with LACP in Debian 12 or Ubuntu 24.04"
 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-us.md
index 895dfbb7d4f..d42b99680de 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: "How to configure Link Aggregation with LACP in Debian 12 or Ubuntu 24.04"
 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.es-es.md
index a4806b83244..255362ff26e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Cómo configurar la agregación de enlaces con LACP en Debian 12 o 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.es-us.md
index a4806b83244..255362ff26e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Cómo configurar la agregación de enlaces con LACP en Debian 12 o 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.fr-ca.md
index 9399ed3ee28..e164bce9cd8 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Comment configurer l'agrégation de liens avec LACP dans Debian 12 ou Ubuntu 24.04"
 excerpt: "Activez l'agrégation de liens dans votre serveur Debian 12 ou Ubuntu 24.04 (Netplan) pour augmenter la disponibilité de votre serveur et augmenter l'efficacité de vos connexions réseau"
-updated: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 La technologie LACP (Link Aggregation Control Protocol) est conçue pour augmenter la disponibilité de votre serveur et améliorer l’efficacité de vos connexions réseau. Vous pouvez agréger vos cartes réseau et rendre vos liens réseau redondants. Cela signifie que si un lien tombe en panne, le trafic est automatiquement redirigé vers un autre lien disponible. La bande passante disponible est également doublée grâce à l’agrégation.
 
-**Ce guide explique comment lier vos interfaces pour les utiliser pour l'agrégation de liens dans Debian 12 / Ubuntu 24.04 (configuration Netplan).**
+**Ce guide explique comment lier vos interfaces pour les utiliser pour l'agrégation de liens dans Debian 12 (*ou plus récent*) / Ubuntu 24.04 (configuration Netplan).**
+
+> [!warning]
+> Bien que les images Debian 12 (ou plus récentes) fournies par OVHcloud utilisent `Netplan` par défaut, il existe deux exceptions clés où `ifupdown` (/etc/network/interfaces) est utilisé à la place :
+>
+> - **Mode rescue** : Bien qu'il soit basé sur Debian 12, le mode rescue s'appuie sur l'utilitaire `ifupdown`.
+> - **Images personnalisées** : Il se peut que les installations Debian effectuées à l'aide de votre propre image utilisent toujours `ifupdown` pour leur configuration réseau.
+>
+> Si vous souhaitez configurer l'agrégation de liens en mode rescue, ou sur un OS personnalisé s'appuyant sur `ifupdown`, veuillez vous référer à [ce guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) à la place.
+>
 
 ## Prérequis
 
@@ -43,7 +52,10 @@ Cliquez sur l'onglet `Interfaces réseau`{.action} et prenez note des adresses M
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Veuillez noter que l'adresse MAC de l'interface publique **principale** est 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:c6`.
+> 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.
+>
+> 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`.
+>
 
 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.
 
@@ -225,4 +237,4 @@ Un intervalle de quelques secondes peut être observé avant que les agrégats s
 
 ## Aller plus loin
 
-Rejoignez notre [communauté d'utilisateurs](/links/community).
+Rejoignez notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.fr-fr.md
index 9399ed3ee28..e164bce9cd8 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "Comment configurer l'agrégation de liens avec LACP dans Debian 12 ou Ubuntu 24.04"
 excerpt: "Activez l'agrégation de liens dans votre serveur Debian 12 ou Ubuntu 24.04 (Netplan) pour augmenter la disponibilité de votre serveur et augmenter l'efficacité de vos connexions réseau"
-updated: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 La technologie LACP (Link Aggregation Control Protocol) est conçue pour augmenter la disponibilité de votre serveur et améliorer l’efficacité de vos connexions réseau. Vous pouvez agréger vos cartes réseau et rendre vos liens réseau redondants. Cela signifie que si un lien tombe en panne, le trafic est automatiquement redirigé vers un autre lien disponible. La bande passante disponible est également doublée grâce à l’agrégation.
 
-**Ce guide explique comment lier vos interfaces pour les utiliser pour l'agrégation de liens dans Debian 12 / Ubuntu 24.04 (configuration Netplan).**
+**Ce guide explique comment lier vos interfaces pour les utiliser pour l'agrégation de liens dans Debian 12 (*ou plus récent*) / Ubuntu 24.04 (configuration Netplan).**
+
+> [!warning]
+> Bien que les images Debian 12 (ou plus récentes) fournies par OVHcloud utilisent `Netplan` par défaut, il existe deux exceptions clés où `ifupdown` (/etc/network/interfaces) est utilisé à la place :
+>
+> - **Mode rescue** : Bien qu'il soit basé sur Debian 12, le mode rescue s'appuie sur l'utilitaire `ifupdown`.
+> - **Images personnalisées** : Il se peut que les installations Debian effectuées à l'aide de votre propre image utilisent toujours `ifupdown` pour leur configuration réseau.
+>
+> Si vous souhaitez configurer l'agrégation de liens en mode rescue, ou sur un OS personnalisé s'appuyant sur `ifupdown`, veuillez vous référer à [ce guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) à la place.
+>
 
 ## Prérequis
 
@@ -43,7 +52,10 @@ Cliquez sur l'onglet `Interfaces réseau`{.action} et prenez note des adresses M
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Veuillez noter que l'adresse MAC de l'interface publique **principale** est 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:c6`.
+> 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.
+>
+> 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`.
+>
 
 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.
 
@@ -225,4 +237,4 @@ Un intervalle de quelques secondes peut être observé avant que les agrégats s
 
 ## Aller plus loin
 
-Rejoignez notre [communauté d'utilisateurs](/links/community).
+Rejoignez notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.it-it.md
index 3112d812d61..01cac0aee38 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Come configurare l'aggregazione di link con LACP in Debian 12 o 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.pl-pl.md
index 728350b4b5f..aab9eb47b5d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Jak skonfigurować agregację łączy za pomocą protokołu LACP w Debianie 12 lub 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.pt-pt.md
index dbfb28833e3..aba13a7e4bd 100644
--- a/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/lacp-enable-netplan/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Como configurar a agregação de links com LACP em Debian 12 ou 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: 2025-02-14
+updated: 2026-01-09
 ---
 
 <style>
@@ -22,7 +22,16 @@ details[open]>summary::before {
 
 Link Aggregation Control Protocol (LACP) technology is designed to increase your server’s availability, and boost the efficiency of your network connections. 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.
 
-**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 / Ubuntu 24.04 (Netplan configuration).**
+**This guide explains how to bond your interfaces to use them for link aggregation in Debian 12 (*or newer*) / Ubuntu 24.04 (Netplan configuration).**
+
+> [!warning]
+> While Debian 12 and newer images provided by OVHcloud utilize Netplan by default, there are two key exceptions where `ifupdown` (/etc/network/interfaces) is used instead:
+>
+> - **Rescue mode**: Although based on Debian 12, the rescue environment relies on the `ifupdown` utility.
+> - **Custom images**: Debian installations performed using your own image may still use `ifupdown` for networking.
+>
+> If you wish to configure link aggregation in rescue mode, or on a custom OS relying on `ifupdown`, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9) instead.
+>
 
 ## Requirements
 
@@ -43,7 +52,10 @@ Switch to the tab `Network Interfaces`{.action} and take note of the MAC address
 ![OVHcloud Control Panel](images/ControlPanel.png){.thumbnail}
 
 > [!primary]
-> Please note that the MAC address of the **main** public interface is the one with the lowest value. In the example image above, this is the address `a1:b2:c3:d4:e5:c6`.
+> 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.
+>
+> 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`.
+>
 
 Now that you know which MAC addresses are associated to each type (public/private) of interface, you need to retrieve the interfaces names.
 
@@ -225,4 +237,4 @@ It may take several seconds for the bond interfaces to come up.
 
 ## Go further
 
-Join our [community of users](/links/community).
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.de-de.md
index 6ca9df03f83..3a446b9ed99 100644
--- a/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9/guide.de-de.md
@@ -1,14 +1,14 @@
 ---
 title: 'Konfigurieren Ihrer Netzwerkkarte für die OVHcloud Link Aggregation in Debian 9 bis 11'
-excerpt: 'Erfahren Sie hier, wie Sie OLA auf Ihrem Debian 9 Server aktivieren'
-updated: 2024-11-26
+excerpt: 'Aktivieren Sie OVHcloud Link Aggregation auf Ihrem Debian (Versionen 9 bis 11)'
+updated: 2026-01-09
 ---
 
 ## 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.
 
-**Diese Anleitung erklärt, wie Sie Ihre Netzwerkkarten verbinden, um sie für OLA in Debian (Versionen 9 bis 11) zu verwenden.**
+**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.**
 
 ## Voraussetzungen
 
@@ -24,6 +24,13 @@ Die OVHcloud Link Aggregation (OLA) wurde von unseren Teams entwickelt, um die V
 > ```
 >
 
+> [!primary]
+>
+> 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 Rettungsmodus.
+>
+> Wenn die Netzwerkkonfiguration Ihres Systems stattdessen `Netplan` verwendet, lesen Sie bitte [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.
@@ -58,6 +65,7 @@ Zum Konfigurieren der Bond-Schnittstelle fügen Sie Folgendes am Ende der Datei
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > Sie müssen die letzte Zeile nur dann zur Datei hinzufügen, wenn Sie das private Netzwerk über IPv6 konfigurieren möchten.
@@ -87,4 +100,4 @@ Dieser Neustart kann einige Sekunden dauern, da die Bond-Schnittstelle erstellt
 
 [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.
+Treten Sie unserer [User Community](/links/community) bei.
\ No newline at end of file
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 13191366099..45036f04d10 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,7 +1,7 @@
 ---
-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 Debian11)"
-updated: 2024-11-26
+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
 ---
 
 ## Objective
@@ -24,6 +24,13 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
 > ```
 >
 
+> [!primary]
+>
+> 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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ This will open an empty text file. To configure the bond interface, insert the f
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
@@ -87,4 +100,4 @@ This restart may take several seconds since it is building the bond interface.
 
 [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).
+Join our [community of users](/links/community).
\ No newline at end of file
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 13191366099..45036f04d10 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,7 +1,7 @@
 ---
-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 Debian11)"
-updated: 2024-11-26
+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
 ---
 
 ## Objective
@@ -24,6 +24,13 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
 > ```
 >
 
+> [!primary]
+>
+> 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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ This will open an empty text file. To configure the bond interface, insert the f
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
@@ -87,4 +100,4 @@ This restart may take several seconds since it is building the bond interface.
 
 [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).
+Join our [community of users](/links/community).
\ No newline at end of file
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 13191366099..45036f04d10 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,7 +1,7 @@
 ---
-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 Debian11)"
-updated: 2024-11-26
+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
 ---
 
 ## Objective
@@ -24,6 +24,13 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
 > ```
 >
 
+> [!primary]
+>
+> 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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ This will open an empty text file. To configure the bond interface, insert the f
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
@@ -87,4 +100,4 @@ This restart may take several seconds since it is building the bond interface.
 
 [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).
+Join our [community of users](/links/community).
\ No newline at end of file
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 da3e3f143ec..45036f04d10 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,7 +1,7 @@
 ---
-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 Debian11)"
-updated: 2024-11-26
+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
 ---
 
 ## Objective
@@ -24,6 +24,13 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
 > ```
 >
 
+> [!primary]
+>
+> 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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ This will open an empty text file. To configure the bond interface, insert the f
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
@@ -85,6 +98,6 @@ This restart may take several seconds since it is building the bond interface.
 
 [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).
+Join our [community of users](/links/community).
\ No newline at end of file
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 13191366099..45036f04d10 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,7 +1,7 @@
 ---
-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 Debian11)"
-updated: 2024-11-26
+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
 ---
 
 ## Objective
@@ -24,6 +24,13 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
 > ```
 >
 
+> [!primary]
+>
+> 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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ This will open an empty text file. To configure the bond interface, insert the f
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
@@ -87,4 +100,4 @@ This restart may take several seconds since it is building the bond interface.
 
 [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).
+Join our [community of users](/links/community).
\ No newline at end of file
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 13191366099..45036f04d10 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,7 +1,7 @@
 ---
-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 Debian11)"
-updated: 2024-11-26
+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
 ---
 
 ## Objective
@@ -24,6 +24,13 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
 > ```
 >
 
+> [!primary]
+>
+> 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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ This will open an empty text file. To configure the bond interface, insert the f
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
@@ -87,4 +100,4 @@ This restart may take several seconds since it is building the bond interface.
 
 [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).
+Join our [community of users](/links/community).
\ No newline at end of file
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 13191366099..45036f04d10 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,7 +1,7 @@
 ---
-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 Debian11)"
-updated: 2024-11-26
+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
 ---
 
 ## Objective
@@ -24,6 +24,13 @@ OVHcloud Link Aggregation (OLA) technology is designed by our teams to increase
 > ```
 >
 
+> [!primary]
+>
+> 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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ This will open an empty text file. To configure the bond interface, insert the f
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > You only need to add the last line to this file if you are planning on configuring private networking via IPv6.
@@ -87,4 +100,4 @@ This restart may take several seconds since it is building the bond interface.
 
 [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).
+Join our [community of users](/links/community).
\ No newline at end of file
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 1ded2b65669..35caa09390f 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,14 +1,14 @@
 ---
 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: 2024-11-26
+updated: 2026-01-09
 ---
 
 ## 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.
 
-**Esta guía explica cómo conectar sus NIC (Network Interface Controller) para utilizarlos con el servicio OLA en Debian 9 a 11.**
+**Descubra cómo agrupar sus NIC (controladores de interfaz de red) para utilizarlos con el servicio OLA en Debian (versiones 9 a 11).**
 
 ## Requisitos
 
@@ -24,6 +24,13 @@ La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la
 > ```
 >
 
+> [!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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ Se abrirá un archivo de texto vacío. Para configurar la interfaz de enlace, in
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > Añada la última línea de comando si piensa configurar una red privada a través de IPv6.
@@ -85,6 +98,6 @@ Este reinicio puede tardar unos segundos ya que se está creando la interfaz de
 
 [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).
+[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).
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
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 1ded2b65669..35caa09390f 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,14 +1,14 @@
 ---
 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: 2024-11-26
+updated: 2026-01-09
 ---
 
 ## 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.
 
-**Esta guía explica cómo conectar sus NIC (Network Interface Controller) para utilizarlos con el servicio OLA en Debian 9 a 11.**
+**Descubra cómo agrupar sus NIC (controladores de interfaz de red) para utilizarlos con el servicio OLA en Debian (versiones 9 a 11).**
 
 ## Requisitos
 
@@ -24,6 +24,13 @@ La tecnología OVHcloud Link Aggregation (OLA) está diseñada para aumentar la
 > ```
 >
 
+> [!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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ Se abrirá un archivo de texto vacío. Para configurar la interfaz de enlace, in
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > Añada la última línea de comando si piensa configurar una red privada a través de IPv6.
@@ -85,6 +98,6 @@ Este reinicio puede tardar unos segundos ya que se está creando la interfaz de
 
 [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).
+[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).
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
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 d47675dd43c..71fb71f4808 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,14 @@
 ---
 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: 2024-11-26
+updated: 2026-01-09
 ---
 
 ## 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.
 
-**Découvrez comment regrouper vos NIC (Network Interface Controller) pour les utiliser avec le service OLA sur Debian (versions de 9 à 11).**  
+**Découvrez comment regrouper vos NIC (Network Interface Controller) pour les utiliser avec le service OLA sur Debian (versions de 9 à 11).**
 
 ## Prérequis
 
@@ -24,6 +24,13 @@ La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour
 > ```
 >
 
+> [!primary]
+>
+> 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.
+>
+> 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.
@@ -58,6 +65,7 @@ Ceci ouvrira un fichier texte vide. Pour configurer l’interface d’agrégatio
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > Il vous suffit d’ajouter la dernière ligne à ce fichier si vous envisagez de configurer un réseau privé via IPv6.
@@ -87,4 +100,4 @@ Ce redémarrage peut prendre quelques secondes puisqu’il permet de mettre en p
 
 [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).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
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 d47675dd43c..71fb71f4808 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,14 @@
 ---
 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: 2024-11-26
+updated: 2026-01-09
 ---
 
 ## 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.
 
-**Découvrez comment regrouper vos NIC (Network Interface Controller) pour les utiliser avec le service OLA sur Debian (versions de 9 à 11).**  
+**Découvrez comment regrouper vos NIC (Network Interface Controller) pour les utiliser avec le service OLA sur Debian (versions de 9 à 11).**
 
 ## Prérequis
 
@@ -24,6 +24,13 @@ La technologie OVHcloud Link Aggregation (OLA) est conçue par nos équipes pour
 > ```
 >
 
+> [!primary]
+>
+> 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.
+>
+> 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.
@@ -58,6 +65,7 @@ Ceci ouvrira un fichier texte vide. Pour configurer l’interface d’agrégatio
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > Il vous suffit d’ajouter la dernière ligne à ce fichier si vous envisagez de configurer un réseau privé via IPv6.
@@ -87,4 +100,4 @@ Ce redémarrage peut prendre quelques secondes puisqu’il permet de mettre en p
 
 [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).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
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 dfa5e497490..fc7630a110f 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,14 +1,14 @@
 ---
 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: 2024-11-26
+updated: 2026-01-09
 ---
 
 ## 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.
 
-**Questa guida ti mostra come associare i Network Interface Controller (NIC) per utilizzarli con il servizio OLA su un sistema Debian 9 a 11.**
+**Scopri come raggruppare le tue NIC (Network Interface Controller) per utilizzarle con il servizio OLA su Debian (versioni da 9 a 11).**
 
 ## Prerequisiti
 
@@ -24,6 +24,13 @@ La tecnologia OVHcloud Link Aggregation (OLA) è stata progettata dai team OVHcl
 > ```
 >
 
+> [!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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ Si aprirà un file di testo vuoto. Per configurare l’interfaccia bond, inseris
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > Per configurare una rete privata via IPv6 è sufficiente aggiungere al file solo l’ultima riga.
@@ -87,4 +100,4 @@ Questa operazione potrebbe richiedere alcuni secondi per costruire l’interfacc
 
 [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).
+Contatta la nostra [Community di utenti](/links/community).
\ No newline at end of file
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 d6bf512d949..0bd9d4889ea 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,14 +1,14 @@
 ---
-title: 'Konfiguracja karty sieciowej (NIC) dla OVHcloud Link Aggregation w Debianie 9-11'
+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: 2024-11-26
+updated: 2026-01-09
 ---
 
 ## 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. 
 
-**Ten przewodnik wyjaśnia, jak powiązać interfejsy sieciowe i wykorzystać je do OLA w Debianie 9-11.**
+**Dowiedz się, jak połączyć swoje karty sieciowe (NIC) w celu korzystania z usługi OLA w systemie Debian (wersje od 9 do 11).**
 
 ## Wymagania początkowe
 
@@ -24,6 +24,13 @@ Technologia OVHcloud Link Aggregation (OLA) została przez nas zaprojektowana w
 > ```
 >
 
+> [!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).
+>
+
 ## 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.
@@ -58,6 +65,7 @@ Spowoduje to otwarcie pustego pliku tekstowego. Aby skonfigurować powiązanie,
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > Dodaj ostatnią linię do tego pliku, jeśli zamierzasz skonfigurować sieć prywatną za pośrednictwem IPv6. 
@@ -91,4 +104,4 @@ OVHcloud zapewnia klientom swobodę i elastyczność wykorzystania sprzętu w sp
 
 [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).
+Dołącz do [grona naszych użytkowników](/links/community).
\ No newline at end of file
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 f2206f6cb7c..9ad0fe841eb 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,14 +1,14 @@
 ---
 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: 2024-11-26
+updated: 2026-01-09
 ---
 
 ## 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.
 
-**Neste manual, explicaremos como ligar as suas NIC para as utilizar para o OLA em Debian 9 a 11.**
+**Descubra como agrupar as suas NIC (Network Interface Controller) para utilizá-las com o serviço OLA no Debian (versões 9 a 11).**
 
 ## Requisitos
 
@@ -24,6 +24,13 @@ A tecnologia OVHcloud Link Aggregation (OLA) foi criada pelas nossas equipas par
 > ```
 >
 
+> [!primary]
+>
+> 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.
+>
+> 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.
@@ -58,6 +65,7 @@ Um ficheiro de texto vazio aparecerá. Para configurar a interface de ligação,
 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
@@ -66,6 +74,11 @@ iface bond0 inet static
   up ip -6 addr add fc10:0000:0000:0001::/64 dev bond0
 ```
 
+> [!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.
+>
+
 > [!primary]
 >
 > Para configurar uma rede privada através do IPv6, só precisará de adicionar a última linha a este ficheiro. 
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.de-de.md
index b659fe3b736..ec367afea56 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: "OVHcloud Rescue-Modus aktivieren und verwenden"
 excerpt: "Erfahren Sie hier, wie Sie das <i>Customer Rescue System</i> zur Fehlerbehebung bei einem Dedicated Server einsetzen"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -351,6 +351,14 @@ chroot /mnt/
 
 Jetzt sollten Sie in der Lage sein, alle erforderlichen Änderungen am System vorzunehmen, z.B. um den [Zugriff auf den Server wiederherzustellen](#gofurther).
 
+### Konfiguration der Link-Aggregation im Rescue-Modus
+
+Die Link-Aggregation (LACP) ist sehr vorteilhaft, da sie die Gesamtbandbreite Ihres Servers erhöht und gleichzeitig Netzwerkredundanz für den Fall eines Ausfalls einer Netzwerkschnittstelle bietet.
+
+Obwohl der Rescue-Modus auf dem Betriebssystem Debian 12 basiert, basiert seine Netzwerkkonfiguration auf dem Dienstprogramm `ifupdown` und nicht auf `Netplan`.
+
+Wenn Sie über einen Server verfügen, der Link Aggregation unterstützt, und diese im Rettungsmodus konfigurieren möchten, lesen Sie bitte [diese Anleitung](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Rescue-Modus verlassen
 
 Falls notwendig, kehren Sie zur Login-Shell des Rescue-Modus zurück, indem Sie Folgendes eingeben:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-asia.md
index 0dd6d19d29c..06bd0b86820 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: "How to activate and use rescue mode"
 excerpt: "Find out how to use the OVHcloud customer rescue system to troubleshoot your dedicated server"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 You should now be able now apply all necessary changes to your system, for example to [regain server access](#gofurther).
 
+### Link Aggregation configuration in rescue mode
+
+Link Aggregation (LACP) is highly beneficial, as it increases your server's total bandwidth while providing network redundancy in case a network interface fails.
+
+Although rescue mode is based on the Debian 12 operating system, its network configuration relies on the `ifupdown` utility, instead of `Netplan`.
+
+If you have a server that supports link aggregation and you wish to configure it in rescue mode, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Exiting rescue mode
 
 If relevant, return to the rescue mode login shell by entering:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-au.md
index 0dd6d19d29c..06bd0b86820 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: "How to activate and use rescue mode"
 excerpt: "Find out how to use the OVHcloud customer rescue system to troubleshoot your dedicated server"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 You should now be able now apply all necessary changes to your system, for example to [regain server access](#gofurther).
 
+### Link Aggregation configuration in rescue mode
+
+Link Aggregation (LACP) is highly beneficial, as it increases your server's total bandwidth while providing network redundancy in case a network interface fails.
+
+Although rescue mode is based on the Debian 12 operating system, its network configuration relies on the `ifupdown` utility, instead of `Netplan`.
+
+If you have a server that supports link aggregation and you wish to configure it in rescue mode, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Exiting rescue mode
 
 If relevant, return to the rescue mode login shell by entering:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-ca.md
index 0dd6d19d29c..06bd0b86820 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "How to activate and use rescue mode"
 excerpt: "Find out how to use the OVHcloud customer rescue system to troubleshoot your dedicated server"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 You should now be able now apply all necessary changes to your system, for example to [regain server access](#gofurther).
 
+### Link Aggregation configuration in rescue mode
+
+Link Aggregation (LACP) is highly beneficial, as it increases your server's total bandwidth while providing network redundancy in case a network interface fails.
+
+Although rescue mode is based on the Debian 12 operating system, its network configuration relies on the `ifupdown` utility, instead of `Netplan`.
+
+If you have a server that supports link aggregation and you wish to configure it in rescue mode, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Exiting rescue mode
 
 If relevant, return to the rescue mode login shell by entering:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-gb.md
index 0dd6d19d29c..06bd0b86820 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: "How to activate and use rescue mode"
 excerpt: "Find out how to use the OVHcloud customer rescue system to troubleshoot your dedicated server"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 You should now be able now apply all necessary changes to your system, for example to [regain server access](#gofurther).
 
+### Link Aggregation configuration in rescue mode
+
+Link Aggregation (LACP) is highly beneficial, as it increases your server's total bandwidth while providing network redundancy in case a network interface fails.
+
+Although rescue mode is based on the Debian 12 operating system, its network configuration relies on the `ifupdown` utility, instead of `Netplan`.
+
+If you have a server that supports link aggregation and you wish to configure it in rescue mode, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Exiting rescue mode
 
 If relevant, return to the rescue mode login shell by entering:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-ie.md
index 0dd6d19d29c..06bd0b86820 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: "How to activate and use rescue mode"
 excerpt: "Find out how to use the OVHcloud customer rescue system to troubleshoot your dedicated server"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 You should now be able now apply all necessary changes to your system, for example to [regain server access](#gofurther).
 
+### Link Aggregation configuration in rescue mode
+
+Link Aggregation (LACP) is highly beneficial, as it increases your server's total bandwidth while providing network redundancy in case a network interface fails.
+
+Although rescue mode is based on the Debian 12 operating system, its network configuration relies on the `ifupdown` utility, instead of `Netplan`.
+
+If you have a server that supports link aggregation and you wish to configure it in rescue mode, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Exiting rescue mode
 
 If relevant, return to the rescue mode login shell by entering:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-sg.md
index 0dd6d19d29c..06bd0b86820 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: "How to activate and use rescue mode"
 excerpt: "Find out how to use the OVHcloud customer rescue system to troubleshoot your dedicated server"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 You should now be able now apply all necessary changes to your system, for example to [regain server access](#gofurther).
 
+### Link Aggregation configuration in rescue mode
+
+Link Aggregation (LACP) is highly beneficial, as it increases your server's total bandwidth while providing network redundancy in case a network interface fails.
+
+Although rescue mode is based on the Debian 12 operating system, its network configuration relies on the `ifupdown` utility, instead of `Netplan`.
+
+If you have a server that supports link aggregation and you wish to configure it in rescue mode, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Exiting rescue mode
 
 If relevant, return to the rescue mode login shell by entering:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-us.md
index 0dd6d19d29c..06bd0b86820 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: "How to activate and use rescue mode"
 excerpt: "Find out how to use the OVHcloud customer rescue system to troubleshoot your dedicated server"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 You should now be able now apply all necessary changes to your system, for example to [regain server access](#gofurther).
 
+### Link Aggregation configuration in rescue mode
+
+Link Aggregation (LACP) is highly beneficial, as it increases your server's total bandwidth while providing network redundancy in case a network interface fails.
+
+Although rescue mode is based on the Debian 12 operating system, its network configuration relies on the `ifupdown` utility, instead of `Netplan`.
+
+If you have a server that supports link aggregation and you wish to configure it in rescue mode, please refer to [this guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Exiting rescue mode
 
 If relevant, return to the rescue mode login shell by entering:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.es-es.md
index 945cc7494fa..23bc65f9877 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Activar y utilizar el modo de rescate"
 excerpt: "Cómo utilizar el modo customer rescue de OVHcloud para solucionar los problemas de un servidor dedicado"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 Ahora debería poder aplicar todos los cambios necesarios al sistema, por ejemplo, para [recuperar el acceso al servidor](#gofurther).
 
+### Configuración de la agregación de enlaces en modo de rescate
+
+La agregación de enlaces (LACP) es muy ventajosa, ya que permite aumentar el ancho de banda total de su servidor y, al mismo tiempo, ofrece redundancia de red en caso de fallo de una interfaz de red.
+
+Aunque el modo de rescate se basa en el sistema operativo Debian 12, su configuración de red se basa en la utilidad `ifupdown`, en lugar de `Netplan`.
+
+Si dispone de un servidor que admite la agregación de enlaces y desea configurarla en modo de rescate, consulte [esta guía](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Salida del modo de rescate
 
 Si es necesario, vuelva al shell de conexión del modo de rescate introduciendo:
@@ -459,4 +467,4 @@ Para servicios especializados (posicionamiento web, desarrollo...), póngase en
 
 Si quiere disfrutar de ayuda para utilizar y configurar sus soluciones de OVHcloud, puede consultar nuestras distintas soluciones [pestañas de soporte](/links/support).
 
-Interactúe con nuestra [comunidad de usuarios](/links/community).
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.es-us.md
index 945cc7494fa..23bc65f9877 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Activar y utilizar el modo de rescate"
 excerpt: "Cómo utilizar el modo customer rescue de OVHcloud para solucionar los problemas de un servidor dedicado"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 Ahora debería poder aplicar todos los cambios necesarios al sistema, por ejemplo, para [recuperar el acceso al servidor](#gofurther).
 
+### Configuración de la agregación de enlaces en modo de rescate
+
+La agregación de enlaces (LACP) es muy ventajosa, ya que permite aumentar el ancho de banda total de su servidor y, al mismo tiempo, ofrece redundancia de red en caso de fallo de una interfaz de red.
+
+Aunque el modo de rescate se basa en el sistema operativo Debian 12, su configuración de red se basa en la utilidad `ifupdown`, en lugar de `Netplan`.
+
+Si dispone de un servidor que admite la agregación de enlaces y desea configurarla en modo de rescate, consulte [esta guía](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Salida del modo de rescate
 
 Si es necesario, vuelva al shell de conexión del modo de rescate introduciendo:
@@ -459,4 +467,4 @@ Para servicios especializados (posicionamiento web, desarrollo...), póngase en
 
 Si quiere disfrutar de ayuda para utilizar y configurar sus soluciones de OVHcloud, puede consultar nuestras distintas soluciones [pestañas de soporte](/links/support).
 
-Interactúe con nuestra [comunidad de usuarios](/links/community).
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.fr-ca.md
index 28490fb15ff..fc3b1b1989e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Activer et utiliser le mode rescue"
 excerpt: "Découvrez comment utiliser le mode customer rescue OVHcloud pour dépanner votre serveur dédié"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 Vous devriez maintenant pouvoir appliquer toutes les modifications nécessaires à votre système, par exemple pour [retrouver l'accès au serveur](#gofurther).
 
+### Configuration de l'agrégation de liens en mode rescue
+
+L'agrégation de liens (LACP) est très avantageuse, car elle permet d'augmenter la bande passante totale de votre serveur tout en offrant une redondance réseau en cas de défaillance d'une interface réseau.
+
+Bien que le mode rescue soit basé sur le système d'exploitation Debian 12, sa configuration réseau repose sur l'utilitaire `ifupdown`, plutôt que `Netplan`.
+
+Si vous disposez d'un serveur supportant l'agrégation de liens, et que vous souhaitez configurer celle-ci en mode rescue, veuillez vous référer à [ce guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Sortie du mode rescue
 
 Le cas échéant, revenez au shell de connexion du mode rescue en entrant :
@@ -459,4 +467,4 @@ Pour des prestations spécialisées (référencement, développement, etc), cont
 
 Si vous souhaitez bénéficier d'une assistance à l'usage et à la configuration de vos solutions OVHcloud, nous vous proposons de consulter nos différentes [offres de support](/links/support).
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.fr-fr.md
index 28490fb15ff..fc3b1b1989e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "Activer et utiliser le mode rescue"
 excerpt: "Découvrez comment utiliser le mode customer rescue OVHcloud pour dépanner votre serveur dédié"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 Vous devriez maintenant pouvoir appliquer toutes les modifications nécessaires à votre système, par exemple pour [retrouver l'accès au serveur](#gofurther).
 
+### Configuration de l'agrégation de liens en mode rescue
+
+L'agrégation de liens (LACP) est très avantageuse, car elle permet d'augmenter la bande passante totale de votre serveur tout en offrant une redondance réseau en cas de défaillance d'une interface réseau.
+
+Bien que le mode rescue soit basé sur le système d'exploitation Debian 12, sa configuration réseau repose sur l'utilitaire `ifupdown`, plutôt que `Netplan`.
+
+Si vous disposez d'un serveur supportant l'agrégation de liens, et que vous souhaitez configurer celle-ci en mode rescue, veuillez vous référer à [ce guide](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Sortie du mode rescue
 
 Le cas échéant, revenez au shell de connexion du mode rescue en entrant :
@@ -459,4 +467,4 @@ Pour des prestations spécialisées (référencement, développement, etc), cont
 
 Si vous souhaitez bénéficier d'une assistance à l'usage et à la configuration de vos solutions OVHcloud, nous vous proposons de consulter nos différentes [offres de support](/links/support).
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.it-it.md
index 40706ce9590..343048daccd 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Attivare e utilizzare il Rescue mode"
 excerpt: "Scopri come utilizzare la modalità customer rescue OVHcloud per risolvere i problemi del tuo server dedicato"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 A questo punto dovresti essere in grado di applicare tutte le modifiche necessarie al tuo sistema, ad esempio per [ritrovare l'accesso al server](#gofurther).
 
+### Configurazione dell'aggregazione dei collegamenti in modalità Rescue
+
+L'aggregazione dei collegamenti (LACP) è molto vantaggiosa, poiché consente di aumentare la larghezza di banda totale del server offrendo al contempo ridondanza di rete in caso di guasto di un'interfaccia di rete.
+
+Sebbene la modalità Rescue sia basata sul sistema operativo Debian 12, la sua configurazione di rete si basa sull'utilità `ifupdown`, piuttosto che su `Netplan`.
+
+Se disponi di un server che supporta l'aggregazione di collegamenti e desideri configurarla in modalità rescue, fai riferimento a [questa guida](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Uscita dalla modalità Rescue
 
 Se necessario, torna alla shell di connessione della modalità Rescue digitando:
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.pl-pl.md
index eb10313f871..42f858dd266 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Aktywacja i korzystanie z trybu Rescue"
 excerpt: "Dowiedz się, jak używać trybu customer rescue OVHcloud do rozwiązywania problemów z serwerem dedykowanym"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 Teraz należy móc zastosować wszystkie niezbędne zmiany w systemie, na przykład aby [odzyskać dostęp do serwera](#gofurther).
 
+### Konfiguracja agregacji łączy w trybu rescue
+
+Agregacja łączy (LACP) jest bardzo korzystna, ponieważ pozwala zwiększyć całkowitą przepustowość serwera, zapewniając jednocześnie redundancję sieci w przypadku awarii interfejsu sieciowego.
+
+Chociaż trybu rescue jest oparty na systemie operacyjnym Debian 12, jego konfiguracja sieciowa opiera się na narzędziu `ifupdown`, a nie `Netplan`.
+
+Jeśli posiadasz serwer obsługujący agregację łączy i chcesz skonfigurować ją w trybu rescue, zapoznaj się z [tym przewodnikiem](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Wyjście z trybu rescue
 
 W razie potrzeby powróć do powłoki połączenia trybu ratunkowego, wprowadzając:
@@ -459,4 +467,4 @@ W przypadku wyspecjalizowanych usług (pozycjonowanie, rozwój, etc.) skontaktuj
 
 Jeśli chcesz otrzymywać wsparcie w zakresie konfiguracji i użytkowania Twoich rozwiązań OVHcloud, zapoznaj się z naszymi [ofertami pomocy](/links/support).
 
-Dołącz do [grona naszych użytkowników](/links/community).
+Dołącz do [grona naszych użytkowników](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.pt-pt.md
index 9b8fdcf02d6..fc144b37b45 100644
--- a/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/rescue_mode/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Ativar e utilizar o modo rescue"
 excerpt: "Descubra como utilizar o modo customer rescue OVHcloud para solucionar problemas com o seu servidor dedicado"
-updated: 2025-01-20
+updated: 2026-01-09
 ---
 
 <style>
@@ -352,6 +352,14 @@ chroot /mnt/
 
 Agora já poderá aplicar todas as modificações necessárias no seu sistema, por exemplo, para [recuperar o acesso ao servidor](#gofurther).
 
+### Configuração da agregação de ligações no modo rescue
+
+A agregação de ligações (LACP) é muito vantajosa, pois permite aumentar a largura de banda total do seu servidor, ao mesmo tempo que oferece redundância de rede em caso de falha de uma interface de rede.
+
+Embora o modo rescue seja baseado no sistema operativo Debian 12, a sua configuração de rede baseia-se no utilitário `ifupdown`, em vez do `Netplan`.
+
+Se tiver um servidor que suporta agregação de links e deseja configurá-la no modo rescue, consulte [este guia](/pages/bare_metal_cloud/dedicated_servers/ola-enable-debian9).
+
 ### Saída do modo rescue
 
 Se aplicável, volte à shell de ligação do modo rescue introduzindo: