HP ProLiant Storage Server Release Notes (January 2006)

Clustering

This section describes issues related to clustering.

Issue: Configuration of cluster service fails in Windows NT 4.0 domain environment

Description Configuring the cluster service on the storage server may fail in a Windows NT

4.0 domain environment.

Workaround Start the remote registry service to resolve this issue.

To start the remote registry service:

1. Select Start > Programs > Administrative Tools > Services.

The Services Manager window should appear.

2. Double-click the Remote Registry service within the right window.

The Remote Registry Properties window should appear.

3. Modify the Startup Type: parameter field from Manual to Automatic.

4. Click Start. Verify that the Remote Registry service has started.

5. Click OK.

6. Close the Services Manager window.

Issue: Extended disk fails mount after cluster failover

Description If you extend a volume of a disk in a clustered configuration, and the group is

moved (or fails over), it fails completely due to an inability to mount the disk. This

happens on any node in the cluster. As a result, the drive letter designation has

been lost.

Workaround Reassign drive letters for volumes on each of the cluster nodes. For additional

information, see the Microsoft article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304736

Issue: Evicting a cluster node removes the services for NFS cluster aware ability

Description If you evict a cluster node and then decide to add it back to the cluster, you see

the message This software update for clustering has already

run on this node when running software updates from the Cluster

Installation Guide found in the WebUI.

Workaround To resolve this issue:

1. Open regedit.

2. Navigate to HKLM\Software\Hewlett-Packard\StorageWorks

Nas

3. Change NASClusterUpdate from 1 to 0.

4. Run the software update in the Cluster Installation Guide.

Issue: Changes to NFS share do not take affect using the Cluster Resource Wizard

Description Changes to NFS share do not take affect using the Cluster Resource Wizard.

Workaround You must highlight NFS share permissions if you are changing the default