3.8 Configuration Settings

Depending on your needs and cluster setup, some additional configuration might be required for you to effectively use Novell Cluster Services. This additional configuration might consist of changing the values on some of the properties for the Cluster object and the Cluster Node objects.

3.8.1 Editing Quorum Membership and Timeout Properties

You can edit Quorum Membership and Timeout properties using iManager.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

  2. Enter 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.

Quorum Triggers (Number of Nodes)

This 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 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 will load and start.

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 will 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 will begin to load on the two servers that are up and running in the cluster.

3.8.2 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.

If you change any protocol properties, you should restart all servers in the cluster to ensure the changes take effect.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

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

  3. Click the Protocols tab.

    This page also lets you view the script used to configure the cluster protocol settings, but not change it. Changes made to the protocols setting will automatically update the script.

Heartbeat

Heartbeat specifies the amount of time between transmits for all nodes in the cluster except the master. For example, if you set this value to 1, nonmaster nodes in the cluster send a signal that they are alive to the master node every second.

Tolerance

Tolerance specifies the amount of time the master node gives all other nodes in the cluster to signal that they are alive. For example, setting this value to 4 means that if the master node does not receive an “I'm alive” signal from a node in the cluster within four seconds, that node is removed from the cluster.

Master Watchdog

Master Watchdog specifies the amount of time between transmits for the master node in the cluster. For example, if you set this value to 1, the master node in the cluster transmits an “I'm alive” signal to all the other nodes in the cluster every second.

Slave Watchdog

Slave Watchdog specifies the amount of time the master node has to signal that it is alive. For example, setting this value to 5 means that if the nonmaster nodes in the cluster do not receive an “I'm alive” signal from the master within five seconds, the master node is removed from the cluster and one of the other nodes becomes the master node.

Max Retransmits

This value is set by default, and should not be changed.

3.8.3 Cluster IP Address and Port Properties

The Cluster IP address is assigned when you install Novell Cluster Services. The Cluster IP address normally does need to be changed, but can be if needed.

The default cluster port number is 7023, and is automatically assigned when the cluster is created. The cluster port number does not need to be changed unless a conflict is created by another resource using the same port number. If there is a port number conflict, change the Port number to any other value that doesn't cause a conflict.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

  2. Enter 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 view or edit the cluster IP address and port properties is also used for quorum membership and timeout and for cluster e-mail notification.

3.8.4 Resource Priority

The Resource Priority allows you to control the order in which multiple resources start on a given node when the cluster is brought up or during a failover or failback. For example, if a node fails and two resources fail over to another node, the resource priority determines which resource loads first.

This is useful for ensuring that the most critical resources load first and are available to users before less critical resources.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

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

  3. Click the Priorities tab.

  4. To change the priority for a resource, select the resource in the list by clicking it, then click the up-arrow or down-arrow to move the resource up or down in the list. This lets you change the load order of the resource relative to other cluster resources on the same node.

  5. Click the Apply button to save changes made to resource priorities.

3.8.5 Cluster E-Mail Notification

Novell Cluster Services can automatically send out e-mail messages for certain cluster events like cluster and resource state changes or nodes joining or leaving the cluster.

You can enable or disable e-mail notification for the cluster and specify up to eight administrator e-mail addresses for cluster notification.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

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

  3. Click the General tab.

  4. Check or uncheck the Enable Cluster Notification Events check box to enable or disable e-mail notification.

  5. If you enable e-mail notification, add the desired e-mail addresses in the field provided.

    You can click the buttons next to the field to add, delete, or edit e-mail addresses. Repeat this process for each e-mail address you want on the notification list.

  6. If you enable e-mail notification, specify the type of cluster events you want administrators to receive messages for.

    To only receive notification of critical events like a node failure or a resource going comatose, click the Receive Only Critical Events radio button.

    To receive notification of all cluster state changes including critical events, resource state changes, and nodes joining and leaving the cluster, click the Verbose Messages radio button.

    To receive notification of all cluster state changes in XML format, choose the XML Messages option. XML format messages can be interpreted and formated with a parser that lets you customize the message information for your specific needs.

  7. Click the Apply button to save changes.

IMPORTANT:Novell Cluster Services uses Postfix to send e-mail alerts. If you have a cluster resource that uses SMTP, that resource might not work in the cluster unless you change the Postfix configuration. For example, GroupWise® uses SMTP and will not function as a cluster resource if Postfix uses the same port, which it does by default. In this case, Postfix must be configured to use a different port. You can do this by editing the etc/postfix/main.cf file and changing the values for the inet_interfaces, mydestination, and mynetworks_style lines. You also need to change the listen port for the smtpd process in the etc/postfix/master.cf file. See the Postfix Web site for more information on configuring Postfix.

3.8.6 Cluster Node Properties

You can view or edit the cluster node number or IP address of the selected node or view the context for the Linux Server object.

  1. In the left column of the main iManager page, locate Clusters, then click the Cluster Options link.

  2. Enter the cluster name or browse and select it, check the box next to the cluster node whose properties you want to view or edit, then click the Properties link.

  3. View or edit the IP address, then click Apply to update the information in eDirectory.

    If the IP address changes for this server, the new information is not automatically updated in eDirectory.

(Node) Number+IP Address

Number+IP Address specifies the cluster node number and IP address for the selected node. If the cluster node number or IP address changes for the selected node, the new information is not automatically updated in eDirectory. Edit the information and click Apply to update the information in eDirectory.

Distinguished Name

The Distinguished Name is the eDirectory name and context for the Server object.