Your Novell Cluster Services solution for each of the peer clusters in the business continuity cluster must consider the following configuration guidelines. Make sure your approach is consistent across all peer clusters.
IP address assignments should be consistently applied within each peer cluster and for all cluster resources.
Ensure that IP addresses are unique across all BCC peer clusters.
Volume IDs must be unique across all peer clusters. Each cluster node automatically assigns volume ID 0 to volume SYS and volume ID 1 to volume _ADMIN. Cluster-enabled volumes use high volume IDs, starting from 254 in descending order. Novell Client uses the volume ID to access a volume.
When existing clusters are configured and enabled within the same business continuity cluster, the volume IDs for the existing shared volumes might also share the same volume IDs. To resolve this conflict, manually edit the load script for each volume that has been enabled for business continuity and change the volume IDs to unique values for each volume in the business continuity cluster.
BCC configuration should consider the configuration requirements for each of the services supported across all peer clusters.
Create failover matrixes for each cluster resource so that you know what service is supported and which nodes are the preferred nodes for failover within the same cluster and among the peer clusters.