Depending on your needs and cluster setup, some additional configuration may 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.
You can edit Quorum Membership and Timeout properties using either ConsoleOne or NetWare Remote Manager.
Right-click the Cluster object.
Click Properties.
Select the Quorum tab on the Cluster Object Property page.
On the left column under the Clustering section, click Cluster Config.
Select the Cluster object name.
Click Quorum.
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.
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.
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.
Right-click the Cluster object.
Click Properties.
On the Cluster Object property page, select the Protocol tab.
This tab has two pages: Settings and Internals. The Internals page lets you view the script used to configure the cluster protocol settings, but not change it. Use the Settings page to make changes to cluster protocol properties.
On the left column under the Clustering section, click Cluster Config.
Select the Cluster object name.
Click Protocol.
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 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 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 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.
This option is not currently used with Novell Cluster Services but will be used for future versions.
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.
Right-click the cluster object.
Click Properties.
On the Cluster Object property page, select the Management tab.
On the left column under the Clustering section, click Cluster Config.
Select the Cluster object name.
Click IP Address.
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.
Right-click the cluster object.
Click Properties.
On the Cluster Object property page, select the Resource Priority tab.
To change the priority for a resource, select the resource in the list and then click the Increase or Decrease button 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.
You can also select a resource and then click the Selected button to reset the resource back to its default load order.
Click the Apply button to save changes made to resource priorities.
On the left column under the Clustering section, click Cluster Config.
Select the Cluster object name.
Click Resource Priorities.
To change the priority for a resource, assign it a number between 0 and 65535.
65535 is the maximum value and 0 is the minimum value. Setting a resource priority to 65535 ensures the resource loads before other resources with lower priority settings. Setting the resource priority to 0 ensures the resource loads last after all other resources have loaded. The default resource priority setting is 0.
If you assign multiple resources the same priority, the start order of those resources is random.
Click the Apply button to save changes made to resource priorities.
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.
In order for cluster e-mail notification to work, you must first configure e-mail notification for server health status using NetWare Remote Manager. For instructions on how to do this go to Diagnosing Server Problems and find the section on Configuring E-mail Notification for Server Health Status.
You can enable or disable e-mail notification for the cluster and specify up to eight administrator e-mail addresses for cluster notification.
IMPORTANT: If you add or delete an administrator e-mail address or change the type of cluster events you want administrators to receive messages for (verbose to XML, etc.), you must reload CMA.NLM (the Cluster Management Agent) on all servers in the cluster for the changes to take effect.
Right-click the cluster object
Click Properties.
On the Cluster Object property page, select the Notification tab.
Check or uncheck the Enable Cluster Notification Events check box to enable or disable e-mail notification.
If you enable e-mail notification, add the desired e-mail address in the field provided and click the button next to the field to add the address to the list. Repeat this process for each address you want on the notification list.
It is not necessary to add quotes to e-mail address names.
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, check the Receive Only Critical Events check box .
To receive notification of all cluster state changes including critical events, resource state changes, and nodes joining and leaving the cluster, check the Verbose Messages check box.
To receive notification of all cluster state changes in XML format, check 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.
Click the Apply button to save changes made.
On the left column under the Clustering section, click Cluster Config.
Select the Cluster object name and click Email Reporting.
Add the desired email addresses in the fields provided.
It is not necessary to add quotes to e-mail address names.
Specify the type of cluster events you want administrators to receive messages for.
Specify a 1 or a 0 to disable email notification.
Specify a 2 (Critical) to only receive notification of critical events like a node failure or a resource going comatose.
Specify a 4 (Verbose) to receive notification of all cluster state changes including critical events, resource state changes, and nodes joining and leaving the cluster.
Specify an 8 to receive notification of all cluster state changes in XML format. XML format messages can be interpreted and formated with a parser that lets you customize the message information for your specific needs.
Click the Apply button to save your changes.
You can view or edit the cluster node number or IP address of the selected node or view the context for the NetWare Server object.
Select the Cluster object and right-click the desired cluster node on the right side of the ConsoleOne display screen.
Click Properties.
On the Cluster Node property page, select the Node tab.
On the left column under the Clustering section, click Cluster Config.
Select the Cluster node name.
Click IP Address or Node Number.
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.
The NCP Server field is used to view the context for the NetWare Server object. This field cannot be edited.