Tracing Identity Manager Communications - Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

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

13.12 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).
For information about setting trace levels for driver sets, see
(http://www.novell.com/documentation/idm36/idm_common_driver/data/b1rc6ea.html).
For information about using
documentation/edir88/edir88tshoot/data/bq0gvax.html)
Troubleshooting Guide (http://www.novell.com/documentation/edir88/edir88tshoot/data/
front.html).
The trace messages are written to the
is installed. By default, it is
the events logged in the file are specific to the actions you are tracing.
To trace the communications for the BCC-specific Identity Manager drivers on a Linux 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.
1b Specify your username and password, specify the tree where you want to log in, then click
Login.
1c Click the View Objects button at the top of the iManager page.
1d In tree view, browse to and right-click the desired DriverSet object, then select Modify
Object.
1e Click the General tab, and in the list of valued attributes, click DirXML-DriverTraceLevel,
then click Edit.
1f Ensure that the Trace Level is set to 4, then click OK.
1g Repeat
level to 4.
1h Repeat
2 At the Linux terminal console, log in as the
/opt/novell/eDirectory/bin/ndstrace
3 Configure DSTrace by entering
118 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
, see
ndstrace
ndstrace.log
. You might want to delete this file before starting a trace so
/var/nds
Step 1e and Step 1f for the DirXML-XSLTraceLevel attribute, also setting the trace
Step 1d through Step 1g for the other driver sets you want to trace.
below.
"Adding Trace Levels in iManager"
"Using ndstrace" (http://www.novell.com/
in the Novell eDirectory 8.8
file located in the directory where eDirectory
user, then start the DSTrace utility by entering
root