Novell Doc: BCC 1.2: Administration Guide for OES 2 SP1 Linux

D.1 Cluster1 to Cluster2

First, create a driver instance on the Identity Manager node for the first cluster in order to synchronize information from the first cluster to the second cluster.

Clusters for This Driver Instance

Clusters Synchronized by This Driver Instance	Value
Name of the source cluster Example: cluster1
Name of the destination cluster Example: cluster2

Clusters Synchronized by This Driver Instance

Value

Name of the source cluster

Example: cluster1

Name of the destination cluster

Example: cluster2

New Driver Set for the Source Cluster

Driver Set Information	Value
Name of the BCC driver set for the source cluster Example: Cluster1 BCC Driver Set
Context that contains the source cluster Example: cluster1.clusters.siteA.example HINT:Browse to select the context.
Distinguished name of the Identity Manager node in the source cluster Example: cl1svr1.cluster1.clusters.siteA.example HINT:Browse to select the server.
Create a new partition on this driver set	Deselect this option.

Driver Instance for the Connection from Source to Destination

Driver Set Information	Value
Pre-configured driver template to import (pick one): BCCClusterResourceSynchronization.xml UserObjectSynchronization.xml HINT:The User Object Synchronization driver is needed only when creating a driver instance for communications between clusters in different trees. In this case, create one driver instance for resource synchronization and one driver instance for user object synchronization.
Driver name for this driver instance Example: cluster1_to_cluster2 BCCCR Sync Example: cluster1_to_cluster2 BCCUO Sync Default: BCC Cluster Sync
SSL certificate name to use for this driver instance Example: cluster1_to_cluster2 BCCCR Sync Example: cluster1_to_cluster2 BCCUO Sync Default: BCC Cluster Sync (kmo)
IP address or DNS name of the Identity Manager node in the destination cluster for this driver instance Example: 10.10.20.21 Example: cl2svr1.cluster2.clusters.siteB.example
Unique IP port to use for this driver instance Example: 2002 (default for resource sync) Example: 2001 (default for user object sync) HINT:Both clusters must use the same port for this connection.
Distinguished name of the source cluster Example: cluster1.clusters.siteA.example HINT:Browse to select the cluster.
Landing zone for this driver instance Specify the distinguished name of the container where the cluster-enabled pool, NCP™ server, and volume objects for the destination cluster will be placed when they are synchronized to the source cluster for this driver instance. The container must already exist and must be specified using dot format without the tree name. Example: clusters.siteA.example HINT:Browse to select the context.