If objects are not synchronizing between clusters, the problem might be caused by one of the following conditions:
The eDirectory daemon (ndsd) is not running on the server that contains the eDirectory master replica in the tree. To restart ndsd on the master replica server, enter the following command at its terminal console prompt as the root user:
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 Servers, Volumes, and Pools).
The drivers are not communicating on the same port.
For example, if the driver on Cluster A is listening on port 2002, the driver on Cluster B must bind to port 2002 on Cluster A in order for the driver communication to work properly.
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.
See Tracing Identity Manager Communications below.