118
BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
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.
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
“Adding Trace Levels in iManager”
(http://www.novell.com/documentation/idm36/idm_common_driver/data/b1rc6ea.html)
.
For information about using
ndstrace
, see
“Using ndstrace” (http://www.novell.com/
documentation/edir88/edir88tshoot/data/bq0gvax.html)
in the
Novell eDirectory 8.8
Troubleshooting Guide
(http://www.novell.com/documentation/edir88/edir88tshoot/data/
front.html)
.
The trace messages are written to the
ndstrace.log
file located in the directory where eDirectory
is installed. By default, it is
/var/nds
. You might want to delete this file before starting a trace so
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
Step 1e
and
Step 1f
for the
DirXML-XSLTraceLevel
attribute, also setting the trace
level to 4.
1h
Repeat
Step 1d
through
Step 1g
for the other driver sets you want to trace.
2
At the Linux terminal console, log in as the
root
user, then start the DSTrace utility by entering
/opt/novell/eDirectory/bin/ndstrace
3
Configure DSTrace by entering
Содержание BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION
Страница 4: ...4 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 36: ...36 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 56: ...56 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 64: ...64 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 70: ...70 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 132: ...132 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 146: ...146 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 152: ...152 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 166: ...166 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 174: ...174 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 176: ...176 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...
Страница 184: ...184 BCC 1 2 1 Administration Guide for OES 2 SP2 Linux novdocx en 7 January 2010...