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.we...@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
