network: rephrase corosync and bonds recommendations

[pve-docs.git] / pve-network.adoc

diff --git a/pve-network.adoc b/pve-network.adoc
index 0c67c62f41e4a59865bb1b8f8e3f9ee4980b73d7..4567ed486a1dfaff2bad570333c24c240cc7a376 100644 (file)
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -337,11 +337,11 @@ 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.
+
+For the cluster network (Corosync) we recommend configuring it with multiple
+networks. Corosync does not need a bond for network reduncancy as it can switch
+between networks by itself, if one becomes unusable.
 
 The following bond configuration can be used as distributed/shared
 storage network. The benefit would be that you get more speed and the