From: Dylan Whyte <d.whyte@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 4/6] pvecm: update instructions to add redundant links
Date: Wed, 15 Sep 2021 15:36:16 +0200 [thread overview]
Message-ID: <20210915133618.143859-4-d.whyte@proxmox.com> (raw)
In-Reply-To: <20210915133618.143859-1-d.whyte@proxmox.com>
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@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
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
next prev parent reply other threads:[~2021-09-15 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 13:36 [pve-devel] [PATCH pve-docs 1/6] pvecm: language and format fixup Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 2/6] pvecm: replace {PVE} with {pve} Dylan Whyte
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 3/6] pvecm: fix command output formatting Dylan Whyte
2021-09-15 13:36 ` Dylan Whyte [this message]
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 5/6] pvecm: add note about corosync killnode error Dylan Whyte
2021-09-16 8:04 ` Fabian Ebner
2021-09-15 13:36 ` [pve-devel] [PATCH pve-docs 6/6] fix 3375: warn user to remove replication jobs Dylan Whyte
2021-09-15 15:03 ` [pve-devel] applied-series: [PATCH pve-docs 1/6] pvecm: language and format fixup Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210915133618.143859-4-d.whyte@proxmox.com \
--to=d.whyte@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox