Peer Cluster Communication Not Working; Resource Does Not Migrate To Another Cluster; Section 4.12, "Peer Cluster Communication Not Working; Section 4.13, "Resource Does Not Migrate To Another Cluster - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - 9-21-2010 ADMINISTRATION GUIDE FOR OPEN ENTERPRISE SERVER 1 SP2 LINUX Administration Manual

1b Specify your username and password, specify the tree where you want to log in, then click
Login.
1c Click the View Objects button at the top of the iManager page.
1d In the left column, browse to and right-click the desired DriverSet object, then select
Modify Object.
1e Click the General tab, and in the list of valued attributes, click DirXML-DriverTraceLevel,
then click Edit.
1f Ensure that the Trace Level is set to 4, then click OK.
1g Repeat
Step 1e
trace level to 4.
1h Repeat
Step 1d
2 At the NetWare server console, load DSTrace by entering
3 Configure DSTrace by entering
console.
4 Enable DSTrace by again entering
5 Run the desired actions for the information you want traced.
6 Disable DSTrace by entering
The trace file is located at
starting a trace so the events logged in the file are specific to the actions you are tracing.

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 by using iManager in a different tree uses an invalid tree encryption.

LIBC has not been updated. See
support.novell.com/docs/Readmes/InfoDocument/2974185.html).

A firewall is blocking port 5988 or 5989 (CIM).
4.13 Resource Does Not Migrate to Another
Cluster
If you cannot 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
and Step 1f for the DirXML-XSLTraceLevel attribute, also setting the
through Step 1g for the other driver sets you want to trace.
dstrace inline -all +dvrs +dxml
at the NetWare server console.
dstrace
at the NetWare server console.
dstrace off
sys:/system/dstrace.log
OES SP2, NW6.5 SP5 Update 1: TID # 2974185 (http://
.
dstrace
at the NetWare server
. You might want to delete this file before
71.
Troubleshooting Business Continuity Clustering 1.1 71