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

Страница: 117 / 184

Troubleshooting Business Continuity Clustering 117
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
13.10 Identity Manager Drivers for Cluster
Synchronization Do Not Start
If the Identity Manager drivers for cluster synchronization do not start, the problem might be caused
by one of the following conditions:
Š
A certificate has not been created. For information, see “Creating SSL Certificates” on page 80 .
Š The ports used by the driver are not unique and available.
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
Chapter 9, “Configuring the Identity Manager Drivers for BCC,” on page 71
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 13.12, “Tracing Identity Manager Communications,” on page 118 .
13.11 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 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:
rcndsd restart
Š
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).