In OES 2, a cluster resource can become stuck in an NDS Sync or eDirectory Sync state if the character case for cluster information stored in the /etc/opt/novell/ncs/clstrlib.conf file does not match the case used for information stored in eDirectory. The clstrlib.conf file is automatically populated with information that you enter as you mange a cluster or cluster resource with tools such as iManager, YaST, and commands. If you use the wrong case when typing cluster information, that information is written to the file.
For example, you might enter the wrong case when performing the following cluster management tasks:
In the YaST Software Installer, you type the cluster name and context when adding a node to an existing cluster.
IMPORTANT:In OES 2 SP1 and later releases, the installer has been modified to ensure that the information that is added to the /etc/opt/novell/ncs/clstrlib.conf file matches the information in eDirectory.
You modify the cluster configuration for an existing cluster as described in Section 8.9, Moving a Cluster, or Changing IP Addresses, LDAP Server, or Administrator Credentials for a Cluster.
You modify the case for a container name or object name for an eDirectory object.
For information about how to make corrections in the /etc/opt/novell/ncs/clstrlib.conf file to resolve the NDS Sync or eDirectory Sync state, see Cluster Resource Stuck in "NDS SYNC" or "eDirectory Sync" State (TID 7001394) on the Novell Support Web site.
A patch that helps prevent the occurrence of mismatched cluster information is available in the OES 2 SP1 patch channel and OES 2 SP2 patch channel in their respective March 2010 patch releases.
IMPORTANT:After the patch is applied, the /etc/opt/novell/ncs/clstrlib.conf file is case-insensitive.