Troubleshooting BCC 1.1
63
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
To resolve this and similar problems, rename the
c:\program files\common
files\novell
directory on the Windows machine where the installation is being run and restart
the BCC 1.1 installation program.
4.9 IDM Drivers for Cluster Synchronization Do
Not Start
If the IDM drivers for cluster synchronization will not start, the problem may be caused by one of
the following conditions:
A certificate has not been created.
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
Section 2.5.1, “Configuring Business-Continuity-Specific IDM Drivers,” on
page 29
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 DirXML Driver Overview page. You can enable the
driver using the radio buttons in the Driver Startup section of the page that displays.
Selecting the Auto Start option is recommended.
See
Section 4.11, “Tracing IDM,” on page 64
.
-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 IDM 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.
4.10 IDM 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 will fail. This is because the underscore character is
mapped to a space. eDirectory will return an error that the entry already exists.
The eDirectory partition on the IDM node is incorrect.
Содержание BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION
Страница 4: ...novdocx en 11 December 2007...
Страница 10: ...10 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...
Страница 72: ...72 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...
Страница 86: ...86 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...
