User Guide

60 NetWare 6 Readme
NetWare 6 Readme
103-000171-001
October 25, 2001
Novell Confidential
Manual 99a38 July 17, 2001
NSS volume corruption occurs if all of the following conditions exist on your
system:
 The Prepare a Novell Cluster for Upgrade option in the Deployment
Manager was run and completed.
 At least one of the NetWare 5 servers in the cluster was upgraded to
NetWare 6.
 One of the NetWare 5 servers not yet upgraded was rebooted and an
attempt was made on that server to create a traditional partition using
NWCONFIG.
Unable to Authenticate to a New Node during Installation
When using NetWare Deployment Manager to install a new node into a
cluster, you might not be able to authenticate to the new node. If this happens,
map a drive from the workstation running Novell Client software (right-click
the red N) to each node in the cluster and then repeat the NetWare Deployment
Manager steps to install the node into the cluster.
Directory Tree Not Visible during Installation
When running the Cluster Services installation, you occasionally might be
unable to see the eDirectory
TM
tree you want to install into from the installation
browser. If this happens, type the name of the tree in the browser path:
treename/cluster.context.
Other Issues
Deactivate Shared NSS Pools
After creating shared NSS pools or volumes, you must deactivate them before
you bring the cluster resource online; otherwise, the resource will go comatose
because it is already active on the server where it was created.
Using DELAY.NLM in Cluster Resource Scripts
If you use DELAY.NLM to delay execution of commands in a cluster resource
load or unload script, do not use the load command in the script to load
DELAY.NLM. Instead, add a command to load DELAY.NLM to the
AUTOEXEC.NCF file on each server where the resource will run. Then
specify the amount of time you want to delay command execution by adding
the DELAY command to the load or unload script. For example, if you want
to cause a five-second delay, add DELAY 5 to the script.