6.2 Configuring Quorum Membership and Timeout Properties

You can edit Quorum Membership and Timeout properties using iManager, ConsoleOne, or Novell Remote Manager.

Using iManager

  1. In Roles and Tasks, select Clusters, then click the Cluster Options link.

  2. Type the cluster name or browse and select it, then click the Properties button under the cluster name.

  3. Click the General tab.

    In iManager, the same page used to edit quorum membership and timeout is also used for the cluster IP address and port properties and for cluster e-mail notification.

Using ConsoleOne

  1. Right-click the Cluster object.

  2. Click Properties.

  3. Select the Quorum tab on the Cluster Object Property page.

Using Novell Remote Manager

  1. In the left column, select Clustering, then select Cluster Config.

  2. Select the Cluster object name.

  3. Click Quorum.

6.2.1 Membership (Number of Nodes)

The Quorum Membership is the number of nodes that must be running in the cluster before resources will start to load. When you first bring up servers in your cluster, Novell Cluster Services reads the number specified in the Membership field and waits until that number of servers is up and running in the cluster before it starts loading resources.

Set the Membership 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 Membership value to 4, there must be four servers up in the cluster before any resource will load and start.

6.2.2 Timeout

Timeout specifies the amount of time to wait for the number of servers defined in the Membership field to be up and running. If the timeout period elapses before the quorum membership reaches its specified number, resources will automatically start loading on the servers that are currently up and running in the cluster. For example, if you specify a Membership 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 will begin to load on the two servers that are up and running in the cluster.