Identity Manager Drivers Do Not Synchronize Objects From One Cluster To Another; Tracing Identity Manager Communications; Another; Section 4.11, "Tracing Identity Manager Communications - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - 9-21-2010 ADMINISTRATION GUIDE FOR OPEN ENTERPRISE SERVER 1 SP2 LINUX Administration Manual


Unknown communications problems.
See Section 4.11, "Tracing Identity Manager Communications," on page

-670 errors in the DSTrace logs. See
Solutions/10090395.html)
This is commonly caused by
Identity Manager tries to load. The load order is sometimes changed by the installation of a
product that changes the order of the lines within the
4.10 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 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

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

4.11 Tracing Identity Manager Communications
DSTrace is used to trace Identity Manager communications. In a BCC, it is generally best to trace
both sides of the communication channel (both drivers).
To trace the communications for the BCC-specific Identity Manager drivers on a NetWare BCC:
1 Modify two attributes on both DriverSet objects.
1a Start your Internet browser and enter the URL for iManager.
The URL is http://server_ip_address/nps/iManager.html. Replace server_ip_address with
the IP address or DNS name of the server that has iManager and the Identity Manager
preconfigured templates for iManager installed.
70 Novell Business Continuity Clustering 1.1 Administration Guide for Linux
TID # 10090395 (http://support.novell.com/docs/Tids/
loading before SAS, which causes problems when
rconag6.nlm
autoexec.ncf
TM Servers, Volumes, and Pools).
below.
70.
file.