The Ip Address, Virtual Server Dn, Or Pool Name Does Not Appear On The Imanager Cluster Configuration Page; Blank Error String Imanager Error Appears While Bringing A Resource Online; Mapping Drives In Login Scripts - Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

13.19 The IP Address, Virtual Server DN, or Pool
Name Does Not Appear on the iManager Cluster
Configuration Page
You might see a DSML read error if you select properties for a Cluster object and then click the
Business Continuity tab.
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
13.20 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.

13.21 Mapping Drives in Login Scripts

Consider the following when mapping drives in login scripts in a BCC:
Using an FDN (such as map s:=BCCP_Cluster_HOMES.servers.:shared) to a cluster-enabled
volume has been tested and does not work.
When the resource fails over to the secondary cluster, the DN does not resolve to a server/
volume that is online. This causes the
Using the
SLP Server Name/VOL:shared
command to fail.
map
syntax has been tested and works.
Troubleshooting Business Continuity Clustering 121