* [pve-devel] [PATCH docs] Revert "Document that active-backup is recommended for corosync"
@ 2021-01-12 13:20 Aaron Lauterer
0 siblings, 0 replies; only message in thread
From: Aaron Lauterer @ 2021-01-12 13:20 UTC (permalink / raw)
To: pve-devel
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
-unsupported.
+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
--
2.20.1
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-01-12 13:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-12 13:20 [pve-devel] [PATCH docs] Revert "Document that active-backup is recommended for corosync" Aaron Lauterer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox