[pve-devel] [PATCH docs] Revert "Document that active-backup is recommended for corosync"

Aaron Lauterer a.lauterer at proxmox.com
Tue Jan 12 14:20:08 CET 2021

This reverts commit 649098a64ecaffc7215ec0556e76787595b38e88.

This seems to be related to the use of multicast in older corosync
versions. Since corosync v3 is using unicast we can drop this
 pve-network.adoc | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/pve-network.adoc b/pve-network.adoc
index 34cc6c8..1c3a17c 100644
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -336,11 +336,7 @@ traffic.
 If your switch support the LACP (IEEE 802.3ad) protocol then we recommend using
 the corresponding bonding mode (802.3ad). Otherwise you should generally use the
-active-backup mode. +
-// http://lists.linux-ha.org/pipermail/linux-ha/2013-January/046295.html
-If you intend to run your cluster network on the bonding interfaces, then you
-have to use active-passive mode on the bonding interfaces, other modes are
+active-backup mode.
 The following bond configuration can be used as distributed/shared
 storage network. The benefit would be that you get more speed and the

More information about the pve-devel mailing list