nfsclust load statement causes NCS to put volume in comatose state

(Last modified: 09Oct2002)

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

fact

Novell NetWare 5.1 Support Pack 3 (NW51SP3.EXE)

Novell NFS Services 3.0 Support Pack 2 (NFS30SP2.EXE)

Novell NetWare Cluster Services

symptom

nfsclust load statement causes NCS to put volume in comatose state

"Error: secondary IP address <volume> is not associated with any local binding"

"Error: deactivating volume"

NSS volume inaccessible after nfsclust load statement is issued

cause

This failure is due to a more general cluster problem with statements invoked out of cluster load scripts. It has to do with spurious error codes being returned. At the server console, when the nfsclust command is executed no error code is seen but an error code is returned, and when it is returned to the load script it causes NCS to deactivate the volume.

fix

Adding the 'load' command (not normally necessary in NetWare 5.1) before nfsclust is the workaround. A five second delay before the nfsclust line also is a workaround but simply adding 'load' to the syntax is more efficient.

Example: LOAD NFSCLUST 

This is resolved in Support Pack 4 for NetWare 5.1

document

Document Title:	nfsclust load statement causes NCS to put volume in comatose state
Document ID:	10067252
Solution ID:	NOVL67556
Creation Date:	04Jan2002
Modified Date:	09Oct2002
Novell Product Class:	Connectivity Products

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.