Configuring Cluster Policies and Priorities 93novdocx (en) 7 January 20105 Under Quorum Triggers, specify the number of nodes that are required to form a quorum forthe specified cluster.For information, see Section 7.2.1, “Quorum Triggers (Number of Nodes),” on page 93.6 Under Quorum Triggers, specify the amount of time in seconds to wait for the quorum to formbefore beginning to load the cluster resources without a quorum being formed.For information, see Section 7.2.2, “Quorum Triggers (Timeout),” on page 93.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 runningin the cluster before resources start to load. When you first bring up servers in your cluster, NovellCluster Services reads the number specified in this field and waits until that number of servers is upand 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 firstserver that is brought up in the cluster. For example, if you set the Number of Nodes value to 4, theremust 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 ofNodes field to be up and running. If the timeout period elapses before the quorum membershipreaches its specified number, resources automatically start loading on the servers that are currentlyup and running in the cluster. For example, if you specify a Number of Nodes value of 4 and atimeout value equal to 30 seconds, and after 30 seconds only two servers are up and running in thecluster, resources begin to load on the two servers that are up and running in the cluster.7.3 Configuring Cluster Protocol PropertiesYou can use the Cluster Protocol property pages to view or edit the transmit frequency and tolerancesettings for all nodes in the cluster, including the master node. The master node is generally the firstnode brought online in the cluster, but if that node fails, any of the other nodes in the cluster canbecome the master.IMPORTANT: If you change any protocol properties, you should restart all servers in the cluster toensure 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
