Troubleshooting BCC 1.1
65
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
4.12 Peer Cluster Communication Not Working
If BCC communication between peer clusters is not functioning, the problem might be caused by
one of the following conditions:
The credentials for the remote cluster have not been set.
You cannot use iManager on a server in one tree to set credentials for a BCC cluster in another
tree. This is because BCC and iManager use the tree key to encrypt the credentials. Setting
credentials using iManager in a different tree uses an invalid tree encryption.
LIBC has not been updated. See
TID # 2974119 (http://support.novell.com/docs/Readmes/
InfoDocument/2974119.html)
.
A firewall is blocking port 5988 or 5989 (CIM).
4.13 Administration of Peer Clusters Not
Functional
This problem is normally caused by the BCC Administrative user not having file system rights to the
cluster administration files. See
“Assigning BCC Administrative User Trustee Rights” on page 39
.
4.14 Resource Does Not Migrate to Another
Cluster
If you can’t migrate a resource from one cluster to another, the problem might be caused by one of
the following conditions:
The resource has not been BCC-enabled.
Remote clusters cannot communicate.
See
Section 4.12, “Peer Cluster Communication Not Working,” on page 65
.
Syslog shows error 1019 (NSMI error).
There could be a partial script in
sys:/tmp
. The scripts are named
NSMIT-######.tmp
.
If there is a partial script, NSMI is experiencing an error and not communicating with the SAN
to make disks visible. One reason for this is that the script might have a single % character in it
that needs to be an escape (%% instead of %). For example, hashes in Perl need to have escape
characters.
4.15 Resource Cannot Be Brought Online
If you cannot bring a BCC-enabled resource online, it is possible the resource might be set as
secondary. If the NCS:BCC State attribute is equal to 1, the resource is set to secondary and cannot
be brought online.
On the resource object, change the NCS:BCC State attribute to 0 to set the resource to the primary
state. Also, increment the NCS:Revision attribute one number so that Novell Cluster Services
recognizes that the resource properties have been updated. See
Step 1 on page 64
for an example of
how to modify object attributes.