[pve-devel] [PATCH pve-docs 4/6] pvecm: update instructions to add redundant links

Dylan Whyte d.whyte at proxmox.com
Wed Sep 15 15:36:16 CEST 2021

mentions the ability to add up to 8 redundant corosync links and how
it's done in the current GUI

Signed-off-by: Dylan Whyte <d.whyte at proxmox.com>
 pvecm.adoc | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/pvecm.adoc b/pvecm.adoc
index 2908267..af9cf33 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -123,9 +123,11 @@ name and select a network connection from the drop-down list to serve as the
 main cluster network (Link 0). It defaults to the IP resolved via the node's
-To add a second link as fallback, you can select the 'Advanced' checkbox and
-choose an additional network interface (Link 1, see also
-xref:pvecm_redundancy[Corosync Redundancy]).
+As of {pve} 6.2, up to 8 fallback links can be added to a cluster. To add a
+redundant link, click the 'Add' button and select a link number and IP address
+from the respective fields. Prior to {pve} 6.2, to add a second link as
+fallback, you can select the 'Advanced' checkbox and choose an additional
+network interface (Link 1, see also xref:pvecm_redundancy[Corosync Redundancy]).
 NOTE: Ensure that the network selected for cluster communication is not used for
 any high traffic purposes, like network storage or live-migration.

More information about the pve-devel mailing list