Debugging Cluster Volume Resource NDS Relationship.

(Last modified: 19May2005)

This document (10082122) is provided subject to the disclaimer at the end of this document.

fact

Novell NetWare 6.5

Novell NetWare 6.0

Novell NetWare Cluster Services 1.7

Novell NetWare Cluster Services 1.6

symptom

When cluster enabling multiple volumes that are associated with the same pool, their volume objects don't get renamed.

Backup application does not see Volume Resource.
Read ResVol error -603
Read ResVol error -708
FFFDFFAE

cause

The volume objects aren't linked to the proper NDS objects

fix

The NDS object class for these objects should be "NCS:Volume Resource" . For each one of these objects, Cluster Service CLSTRLIB.NLM library code attempts to enumerate the NSS Pools and Volumes they are managing.  It then uses the "NCS:Volumes" attribute on the cluster volume resource object to read the "nssfsPools" attribute from the NDS volume object.  For every NDS object of type "NCS:Volume Resource" inside the cluster container, the cluster code is trying to get the list of Pools and Volumes.  Some NDS volume objects may have no "nssfsPool" attribute. This can happen if they were recreated via the server utility NWCONFIG (NWCONFIG->Update Mounted Volumes into the directory). 

One way to resolve incorrect NDS linkage is to manually repair / review the NDS relationships between the various objects. Here are the steps to recreate cluster volume resource objects in NDS. These steps only affect the NDS objects and do nothing to physical media - data on disk remains intact throughout this process.

1) Offline all Cluster Volume Resource objects via ConsoleOne Cluster State View or command line.
2) Delete all Cluster Volume Resource objects via ConsoleOne Console View - these are the objects located inside the cluster container (and of type NCS:Volume Resource).
3) Using one of the servers in the cluster, go to ConsoleOne and activate all of the sharable for clustering pools on that server.
4) Use the update NDS button for each Pool to recreate the Pool object in NDS.
5) Mount each volume on each Pool and use the update NDS button for each volume to recreate the Volume object in NDS.
6) There are now new Pool and Volume objects (in NDS) for each of the physical Pools and its Volume(s) on shared disk.
7) Deactivate all the Pools from ConsoleOne.
8) Select the cluster container object.
9) Select the New Cluster Volume button and browse to each of the volumes on each pool.
10) Cluster enable each volume on each pool by entering the IP address and customize the virtual server name as desired.
11) This will create new Cluster Volume Resource objects inside the cluster container.
12) Set the preferred nodes for each of the Cluster Volume Resource objects and other properties. Add any extra commands to the load/unload scripts if there were applications or other commands executing from the load/unload scripts.
13) Online the Cluster Volume Resource objects.

.

document

Document Title: Debugging Cluster Volume Resource NDS Relationship.
Document ID: 10082122
Solution ID: NOVL88535
Creation Date: 14Apr2003
Modified Date: 19May2005
Novell Product Class:NetWare

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.