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

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

112 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
13.1 NSS Takes Up to 10 Minutes to Load When
the Server Is Rebooted
In some environments, a timing problem prevents the NDP user space application (
ndpapp
) from
loading, and in turn, NSS cannot be loaded until the problem resolves itself. You can increase the
UDEV event handling limits to 1024 to circumvent this problem. For instructions, see “
NSS Takes
Up to 10 Minutes to Load When the Server Is Rebooted (Linux) ” in the OES 2 SP2: NSS File System
Administration Guide .
13.2 Identity Manager Plug-Ins Do Not Appear in
iManager
After you properly install Identity Manager plug-ins in iManager, the plug-ins sometime disappear
from iManager for the tree you want to manage.
Identity Manager plug-ins for iManager require that eDirectory
TM
is running and working properly in
the tree you are trying to manage. If the plug-in does not appear in iManager, make sure that the
eDirectory daemon (
ndsd
) is running on the server that contains the eDirectory master replica for
that tree.
To restart
ndsd
on the master replica server, enter the following command at its terminal console
prompt as the
root
user:
rcndsd restart
13.3 Cluster Connection States
The connection state numbers are recorded in a log file that you can use to view connection and
status changes for BCC.
The default path to the log file on Linux is
/var/log/messages
. The administrator might have
changed this path from the default. Search for BCCD to view BCC-related messages and entries in
the log file.
There are several different cluster connection states:
Table 13-1
BCC Connection States
BCC Connection State Number Description Possible Actions
Normal 0 The connections between
clusters are functioning
normally. None required.
Authenticating 1 BCC is in the process of
authenticating to a peer
cluster. Wait until the authentication process
is finished.
Invalid Credentials 2 You entered the wrong
username or password for
the selected peer cluster. Enter the correct username and
password that this cluster will use to
connect to the selected peer cluster.