From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id E077F69DF2 for ; Wed, 15 Sep 2021 15:36:29 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D2AC11976B for ; Wed, 15 Sep 2021 15:36:29 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id A8D031973D for ; Wed, 15 Sep 2021 15:36:28 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 7C7EA448B9 for ; Wed, 15 Sep 2021 15:36:28 +0200 (CEST) From: Dylan Whyte To: pve-devel@lists.proxmox.com Date: Wed, 15 Sep 2021 15:36:16 +0200 Message-Id: <20210915133618.143859-4-d.whyte@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20210915133618.143859-1-d.whyte@proxmox.com> References: <20210915133618.143859-1-d.whyte@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.474 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH pve-docs 4/6] pvecm: update instructions to add redundant links X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Sep 2021 13:36:29 -0000 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 --- 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 hostname. -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. -- 2.30.2