Do Not Mix Idm Versions; Known Issues; Existing Clusters Could Have Conflicting Volids; Refresh Of Imanager Views Delayed - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP1 - README 9-21-2010 Installation Manual

The same restrictions that apply to migrating or failing over resources between nodes within a single
cluster also apply to migrating or failing over resources between clusters in a mixed BCC. You can
only migrate or fail over NSS pool/volume resources between clusters in a mixed BCC. See
Converting a NetWare Cluster to Linux (http://www.novell.com/documentation/oes/
cluster_admin_lx/data/bu1b1x8.html)
Guide for Linux

3.7 Do Not Mix IDM Versions

Do not install IDM 3.x management utilities with the IDM 2.x engine. If you do, the IDM Driver for
eDirectory will be converted to version 3.x, and the IDM 2.x engine will no longer be able to get the
driver information.

4 Known Issues


Section 4.1, "Existing Clusters Could Have Conflicting VOLIDs," on page 5

Section 4.2, "Refresh of iManager Views Delayed," on page 5

Section 4.3, "NSS Pool Failover Times," on page 6

Section 4.4, "Migrating Volume Trustee Assignments," on page 6

Section 4.5, "Renamed BCC Volume Names Don't Replicate to Other Trees," on page 6

Section 4.6, "Using iManager to Set Credentials on Linux Not Functional," on page 6

Section 4.7, "Problems Saving SAN Management Scripts," on page 7

Section 4.8, "Resource Goes Offline After Migration," on page 7

Section 4.9, "Cluster and Peer Clusters Don't Appear in Connections List After Upgrade," on
page 7

Section 4.10, "Creating a New Cluster Resource Requires IDM Cluster Node to Be Up," on
page 7

Section 4.11, "Disabling BCC for a Cluster Disables BCC for Cluster Resources," on page 7

Section 4.12, "Cluster Restart Command Not Functional on NetWare," on page 7

4.1 Existing Clusters Could Have Conflicting VOLIDs

When existing clusters are configured and enabled within the same business continuity cluster, the
volume IDs (VOLIDs) for the existing shared volumes might also share the same VOLIDs. To
correct this problem, manually edit the load script for each volume that has been enabled for
business continuity and change the VOLIDs to unique values for each volume in the business
continuity cluster.

4.2 Refresh of iManager Views Delayed

When you enable a cluster resource for business continuity, that resource might take up to 30
seconds to appear as enabled for business continuity in iManager. After Business Continuity
Clustering refreshes its status information, the resource will appear as enabled.
in the OES Novell Cluster Services 1.8.2 Administration
Novell Business Continuity Clustering 1.1 SP1 Readme 5