Clusters Cannot Communicate; Bcc Startup Flags - Novell BUSINESS CONTINUITY CLUSTERING 1.2 - ADMINISTRATION Administration Manual

12.8 Clusters Cannot Communicate

If the clusters in your BCC cannot communicate with each other, it is possible that the User object
you are using to administer your BCC does not have sufficient rights to the Cluster objects for each
cluster. To resolve this problem, ensure that the BCC Administrator user is a trustee of the Cluster
objects and has at least Read and Write rights to the All Attributes Rights property.
1 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.
2 Specify your username and password, specify the tree where you want to log in, then click
Login.
3 In Roles and Tasks, click Rights, then click the Modify Trustees link.
4 Specify the Cluster object name, or browse and select it, then click OK.
5 If the BCC Administrator user is not listed as a trustee, click the Add Trustee button, browse
and select the User object, then click OK.
6 Click Assigned Rights for the BCC Administrator user, then ensure that the Read and Write
check boxes are selected for the All Attributes Rights property.
7 Click Done to save your changes.
8 Repeat

12.9 BCC Startup Flags

There are three optional flags that can be used by BCC during startup.
Table 12-2
Startup Flag
d
v
t
There are two usage options:
To use the v and t flags, edit the
NOVELL_BCCD_ARGS=
combination of v and/or t. This could include v, vt, t, or tv.
Do not use the d flag with this option.
Stop BCC by entering
opt/novell/bcc/sbin/bccd -flags
112 BCC 1.2: Administration Guide for OES 2 SP1 Linux
Step 3 through Step 7 for the other Cluster objects in your BCC.
Optional Startup Flags
Description
Keeps the bccd from forking (keeps the process in foreground). Log messages are
printed to the running terminal screen (
Turns on more verbose logging.
Turns on tracing. With tracing turned on, certain sections of code that fail will report a
message containing the condition that failed along with a file and line number in the code
indicating where the condition failed. This is helpful for reporting problems to Novell
Support.
line to
NOVELL_BCCD_ARGS=-flags
rcnovell-bccd stop
stdout ) along with the normal
/etc/init.d/novell-bcc
at the server console, then restart it by entering
. Replace flags with any combination of v, t, and/or d.
syslog
file and change the
. Replace flags with any
.
/