E.45 May 6, 2009

Updates were made to the following sections. The changes are explained below.

E.45.1 Configuring Cluster Resources for Shared NSS Pools and Volumes

Location

Change

Section 12.8, Adding Advertising Protocols for NSS Pool Cluster Resources

Step 9a was modified to clarify that you can specify a different name for the Novell CIFS Server only when you create the share. Use the CIFS iManager plug-in to manage the name of existing CIFS shares.

E.45.2 Configuring and Managing Cluster Resources

Location

Change

Section 10.2.2, Creating a Resource Template

The following sentence in Step 5 was modified for clarification:

If the script does not complete within the specified time, the resource becomes comatose when migrating to another node.

Section 10.5, Configuring an Unload Script for a Cluster Resource

The following sentence in Step 6 was modified for clarification:

If the script does not complete within the specified time, the resource becomes comatose when migrating to another node.

Section 10.6.4, Monitoring Services That Are Critical to Clustering

This section is new.

Section 10.7, Configuring the Start, Failover, and Failback Modes for Cluster Resources

The following statement was added for clarification. There is no behavior change.

IMPORTANT:Cluster Services works with NCP user connections so that the user data sessions are resumed after failover. However, non-NCP users might experience service interruption and need to reconnect to the server after the failover. Client applications using server based storage must be restarted even with NCP unless the applications are NCP reconnect aware.

E.45.3 Installing Novell Cluster Services on OES 2 Linux

Location

Change

Section 5.2, Extending the eDirectory Schema to Add Cluster Objects

Removed references to ncpserver.ldif. This file is a by-product of the extension and is not part of the setup.

E.45.4 Troubleshooting Novell Cluster Services

E.45.5 Upgrading OES 2 Linux Servers

Location

Change

Section 6.2, Upgrading OES 2 Clusters (Rolling Cluster Upgrade)

You can also add OES 2 SP1 Linux servers (or later versions) to the OES 2 Linux cluster, and remove the old OES 2 Linux servers from the cluster.

Ensure that any services that are available only in OES 2 SP1 (such as Novell CIFS or Novell AFP) are set up with preferred nodes for failover that are running OES 2 SP1.

Several guidelines are provided about the mixed-version cluster.