Clusters Cannot Communicate; Bcc Startup Flags; Section 4.6, "Clusters Cannot Communicate; Section 4.7, "Bcc Startup Flags - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - 9-21-2010 ADMINISTRATION GUIDE FOR OPEN ENTERPRISE SERVER 1 SP2 LINUX Administration Manual

4.6 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 the left column, 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

4.7 BCC Startup Flags

There are three optional flags that can be used by BCC during startup.
provides a description of each flag.
Table 4-2 Optional Startup Flags
Startup Flag
d
v
t

Section 4.7.1, "Using BCC Startup Flags on NetWare," on page 69

Section 4.7.2, "Using BCC Startup Flags on Linux," on page 69
68 Novell Business Continuity Clustering 1.1 Administration Guide for Linux
Step 3 through Step 7 for the other Cluster objects in your BCC.
Description
On Linux, this flag keeps the bccd from forking (keeps the process in foreground) and log
messages are printed to the running terminal screen (stdout) along with the normal
syslog.
This flag is not used on NetWare.
On both Linux and NetWare, this flag turns on more verbose logging.
On both Linux and NetWare, this flag 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.
Table 4-2 lists the flags and