X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=pvecm.adoc;h=3d62c0b6be5dafce2c3d8e27a352bb2ea62243d9;hp=813fe8d93b90212a83372562f61863809bd82370;hb=94958b8b9230d5b9b5e2e70c481f115b18a5fa0b;hpb=c15cdfba0d7f51bf6700fc0fc16b168d555ac121

diff --git a/pvecm.adoc b/pvecm.adoc
index 813fe8d..3d62c0b 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -77,8 +77,12 @@ manually enabled first.
 
 * Root password of a cluster node is required for adding nodes.
 
-NOTE: It is not possible to mix Proxmox VE 3.x and earlier with
-Proxmox VE 4.0 cluster nodes.
+NOTE: It is not possible to mix {pve} 3.x and earlier with {pve} 4.X cluster
+nodes.
+
+NOTE: While it's possible for {pve} 4.4 and {pve} 5.0 this is not supported as
+production configuration and should only used temporarily during upgrading the
+whole cluster from one to another major version.
 
 
 Preparing Nodes
@@ -92,20 +96,27 @@ Currently the cluster creation can either be done on the console (login via
 `ssh`) or the API, which we have a GUI implementation for (__Datacenter ->
 Cluster__).
 
+While it's often common use to reference all other nodenames in `/etc/hosts`
+with their IP this is not strictly necessary for a cluster, which normally uses
+multicast, to work. It maybe useful as you then can connect from one node to
+the other with SSH through the easier to remember node name.
+
 [[pvecm_create_cluster]]
 Create the Cluster
 ------------------
 
 Login via `ssh` to the first {pve} node. Use a unique name for your cluster.
-This name cannot be changed later. The cluster name follows the same rules as node names.
+This name cannot be changed later. The cluster name follows the same rules as
+node names.
 
 ----
  hp1# pvecm create CLUSTERNAME
 ----
 
-CAUTION: The cluster name is used to compute the default multicast
-address. Please use unique cluster names if you run more than one
-cluster inside your network.
+CAUTION: The cluster name is used to compute the default multicast address.
+Please use unique cluster names if you run more than one cluster inside your
+network. To avoid human confusion, it is also recommended to choose different
+names even if clusters do not share the cluster network.
 
 To check the state of your cluster use: