2021-04-22 00:19:26 UTC
a node to a cluster with a quorum disk with more than a single vote.
If you are using a quorum disk, and QDSKVOTES is greater than 1,
CLUSTER_CONFIG_LAN.COM will not preserve the value when it creates its
initial IA64VMSSYS.PAR file for the new system. Instead it will use the
This will result in the new node not being allowed into the cluster, and
you will be forced to crash the node attempting to boot.
The easiest solution is to use a conversational boot for the first boot
and change QDSKVOTES to the correct value, and do not set WRITESYSPARAMS
to 0 after the change, so the new value will be written back to the
In case there are questions about why use a quorum disk or why use
QDSKVOTES greater than 1, the short answer is so you can have the
cluster survive with a single node up, without the need to manually
So, if you have x active boot nodes, you set VOTES to 1 on all active
nodes, QDSKVOTES to x-1, and EXPECTED_VOTES to 2x-1. Then the cluster
will maintain quorum and not hang, while the quorum disk is available
and at least one active boot node is running.