Quorum Triggers (Number Of Nodes); Quorum Triggers (Timeout); Configuring Cluster Protocol Properties - Novell OPEN ENTERPRISE SERVER 2 SP 2 - CLUSTER SERVICES 1.8.7 FOR LINUX Manual

5 Under Quorum Triggers, specify the number of nodes that are required to form a quorum for
the specified cluster.
For information, see
6 Under Quorum Triggers, specify the amount of time in seconds to wait for the quorum to form
before beginning to load the cluster resources without a quorum being formed.
For information, see
7 Click Apply or OK to save your changes.

7.2.1 Quorum Triggers (Number of Nodes)

The number of nodes required to form a cluster quorum is the number of nodes that must be running
in the cluster before resources start to load. When you first bring up servers in your cluster, Novell
Cluster Services reads the number specified in this field and waits until that number of servers is up
and running in the cluster before it starts loading resources.
Set this value to a number greater than 1 so that all resources don't automatically load on the first
server that is brought up in the cluster. For example, if you set the Number of Nodes value to 4, there
must be four servers up in the cluster before any resource loads and starts.

7.2.2 Quorum Triggers (Timeout)

Timeout specifies the amount of time to wait for the number of servers defined in the Number of
Nodes field to be up and running. If the timeout period elapses before the quorum membership
reaches its specified number, resources automatically start loading on the servers that are currently
up and running in the cluster. For example, if you specify a Number of Nodes value of 4 and a
timeout value equal to 30 seconds, and after 30 seconds only two servers are up and running in the
cluster, resources begin to load on the two servers that are up and running in the cluster.

7.3 Configuring Cluster Protocol Properties

You can use the Cluster Protocol property pages to view or edit the transmit frequency and tolerance
settings for all nodes in the cluster, including the master node. The master node is generally the first
node brought online in the cluster, but if that node fails, any of the other nodes in the cluster can
become the master.
IMPORTANT: If you change any protocol properties, you should restart all servers in the cluster to
ensure that the changes take effect.
1 In iManager, select Clusters, then select Cluster Options.
2 Specify the cluster name, or browse and select the Cluster object.
3 Click the Properties button under the cluster name.
4 Click the Protocols tab.
The Protocols page also lets you view the script used to configure the cluster protocol settings,
but not to change it. Changes made to the protocols setting automatically update the scripts.
5 Specify values for the cluster protocols properties.
For information, see the following:
Heartbeat
Section 7.2.1, "Quorum Triggers (Number of Nodes)," on page
Section 7.2.2, "Quorum Triggers (Timeout)," on page 93.
Configuring Cluster Policies and Priorities
93.
93