vrf : remove net.ipv4.tcp_l3mdev_accept=1 sysctl tuning

[pve-docs.git] / pvecm.adoc

diff --git a/pvecm.adoc b/pvecm.adoc
index 0cf044d823f7f7bccf8b3ee109d420acdeb83f5f..7c786bc99f7f158f442c05becf10458623be6ab6 100644 (file)
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -75,6 +75,8 @@ manually enabled first.
 * We recommend a dedicated NIC for the cluster traffic, especially if
   you use shared storage.
 
+* 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.
 
@@ -86,14 +88,14 @@ First, install {PVE} on all nodes. Make sure that each node is
 installed with the final hostname and IP configuration. Changing the
 hostname and IP is not possible after cluster creation.
 
-Currently the cluster creation has to be done on the console, so you
-need to login via `ssh`.
+Currently the cluster creation can either be done on the console(login via `ssh`) or the GUI.
 
+[[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.
+This name cannot be changed later. The cluster name follows the same rules as node names.
 
  hp1# pvecm create YOUR-CLUSTER-NAME
 
@@ -120,6 +122,7 @@ load of the network significantly because multicast packets are only delivered
 to endpoints of the respective member nodes.
 
 
+[[pvecm_join_node_to_cluster]]
 Adding Nodes to the Cluster
 ---------------------------
 
@@ -626,6 +629,7 @@ systemctl status corosync
 If corosync runs again correct restart corosync also on all other nodes.
 They will then join the cluster membership one by one on the new network.
 
+[[pvecm_rrp]]
 Redundant Ring Protocol
 ~~~~~~~~~~~~~~~~~~~~~~~
 To avoid a single point of failure you should implement counter measurements.