Identity Manager Drivers For Cluster Synchronization Do Not Start; Identity Manager Drivers Do Not Synchronize Objects From One Cluster To Another - Novell BUSINESS CONTINUITY CLUSTERING 1.2 - ADMINISTRATION Administration Manual

12.10 Identity Manager Drivers for Cluster
Synchronization Do Not Start
If the Identity Manager drivers for cluster synchronization do not start, the problem might be caused
by one of the following conditions:
A certificate has not been created. For information, see
The ports used by the driver are not unique and available.
Each eDirectory driver must listen on a different port number. To specify the port number,
access the driver properties in iManager and specify the appropriate port number in the IP
address field. See Chapter 8, "Configuring the Identity Manager Drivers for BCC," on page 67
for more information.
The format for specifying the port number in the IP address field is remote IP:remote
port:local port. For example, you could specify something similar to 10.1.1.1:2001:2001. If it
is not being used for other drivers, port 2001 can be used for the User object driver and port
2002 for the Cluster object driver.
The driver has been disabled.
Click the red icon for the driver on the Identity Manager Driver Overview page. You can enable
the driver by using the radio buttons in the Driver Startup section of the page that displays.
Selecting the Auto Start option is recommended.
Unknown communications problems.
See Section 12.12, "Tracing Identity Manager Communications," on page
12.11 Identity Manager Drivers Do Not
Synchronize Objects from One Cluster to
Another
If objects are not synchronizing between clusters, the problem might be caused by one of the
following conditions:
The eDirectory daemon (
replica in the tree. To restart
its terminal console prompt as the
rcndsd restart
The drivers are not running.
A driver is not security equivalent to an object with the necessary rights in the tree.
You have underscores and spaces in object names.
eDirectory interprets underscores and spaces as the same character. For example, if you have a
cluster template named iFolder Server and you try to synchronize a resource named
iFolder_Server, the synchronization fails. This is because the underscore character is mapped to
a space. eDirectory returns an error that the entry already exists.
The eDirectory partition on the Identity Manager node is incorrect.
This partition must contain the cluster container, the DriverSet, the Landing Zone OU, and the
server containers (Virtual NCP
) is not running on the server that contains the eDirectory master
ndsd
on the master replica server, enter the following command at
ndsd
user:
root
Servers, Volumes, and Pools).
TM
"Creating SSL Certificates" on page
114.
Troubleshooting Business Continuity Clustering 113
76.