Blank Error String Imanager Error Appears While Bringing A Resource Online; Best Practices; Section 4.21, "Blank Error String Imanager Error Appears While Bringing A Resource Online; Section 4.22, "Best Practices - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - 9-21-2010 ADMINISTRATION GUIDE FOR OPEN ENTERPRISE SERVER 1 SP2 LINUX Administration Manual

The eDirectory pointers for the cluster resource are either missing or are invalid. The following list
shows the required attributes. The format for the list is:
Object in the directory (Object Class Name)
Attribute Name -->The object in the directory the attribute points to
Attribute Name -->The object in the directory the attribute points to
Clustered Volume (Object Class "NCS:Volume Resource")
NCS:NCP Server -->Virtual NCP Servers
NCS:Volumes-->All Volumes
Virtual NCP Server (Object Class "NCP Server")
Resource-->Cluster Resource
NCS:NetWare Cluster-->Cluster Object
NCS:Volumes-->All Volumes
Volume (Object Class "Volume")
nssfsPool-->Pool Object
Host Server-->Virtual NCP Server
Pool (Object Class "nssfsPool")
Host Server-->Virtual NCP Server
4.21 Blank Error String iManager Error Appears
While Bringing a Resource Online
If you get an error in iManager with a blank error string (no text appears with the error message)
while attempting to bring a resource online, it is possible that Novell Cluster Services views the
resource as secondary even though BCC has changed the resource to primary and iManager shows
the resource as primary.
To resolve this problem, make a change to the cluster properties to cause the NCS:Revision attribute
to increment. You could add a comment to the resource load script to cause this to happen.

4.22 Best Practices

The following practices help you avoid potential problems with your BCC:

IP address changes should always be made on the Protocols page of the iManager cluster snap-
in, not in load and unload scripts.
This is the only way to change the IP address on the virtual NCP server object in eDirectory.

Ensure that eDirectory and your clusters are stable before implementing BCC.

Engage Novell Consulting.

Engage a consulting group from your SAN vendor.
74 Novell Business Continuity Clustering 1.1 Administration Guide for Linux