Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION, Руководство администратора

Страница: 107 / 142

Troubleshooting Business Continuity Clustering 1.1 107
no
vd
ocx
(e
n)
13
Ma
y 20
09
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
Section 6.1, “Configuring Identity Manager Drivers for the Business
Continuity Cluster,” 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 9.11, “Tracing Identity Manager Communications,” on page 108 .
Š
-670 errors in the DSTrace logs. See TID # 10090395 (http://support.novell.com/docs/Tids/
Solutions/10090395.html)
This is commonly caused by
rconag6.nlm
loading before SAS, which causes problems when
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
autoexec.ncf
file.
9.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
TM
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.