From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] pvecm: redundancy: explicitly mention subnets
Date: Mon, 8 Sep 2025 16:52:24 +0200 [thread overview]
Message-ID: <20250908145305.112814-1-f.weber@proxmox.com> (raw)
The section uses addresses 10.10.10.X and 10.20.20.X in examples and
implicitly assumes they are in disjoint subnets, but does not
explicitly state this.
For better clarity, explicitly mention these are /25 subnets (this
subnet mask is also used in the "Separate Cluster Network" section).
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
---
Notes:
Reported in enterprise support as potentially confusing.
pvecm.adoc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/pvecm.adoc b/pvecm.adoc
index 5258038..10b4b16 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -908,6 +908,9 @@ adding a new node) or by specifying more than one 'ringX_addr' in
NOTE: To provide useful failover, every link should be on its own
physical network connection.
+The following examples assume that each cluster node has one static address in
+10.10.10.0/25 and one static address in 10.20.20.0/25 configured.
+
Links are used according to a priority setting. You can configure this priority
by setting 'knet_link_priority' in the corresponding interface section in
`corosync.conf`, or, preferably, using the 'priority' parameter when creating
--
2.47.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-08 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 14:52 Friedrich Weber [this message]
2025-09-09 13:12 ` Maximiliano Sandoval
2025-09-09 15:38 ` [pve-devel] applied: " Fiona Ebner
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=20250908145305.112814-1-f.weber@proxmox.com \
--to=f.weber@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.