B.2 Cluster2 to Cluster1

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

Clusters for This Driver Instance

Clusters Synchronized by This Driver Instance

Value for Your Network

Name of the source cluster

Example: cluster2

 

Name of the destination cluster

Example: cluster1

 

New Driver Set for the Source Cluster

Driver Set Information

Value for Your Network

Name of the BCC driver set for the source cluster

Example: Cluster2 BCC Driver Set

 

Context that contains the source cluster

Example: cluster2.clusters.siteB.example

HINT:Browse to select the context.

 

Distinguished name of the Identity Manager node in the source cluster

Example: cl2svr1.cluster2.clusters.siteB.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 for Your Network

Preconfigured driver template to import:

BCCClusterResourceSynchronization.xml

 

Driver name for this driver instance

Example: cluster2_to_cluster1 BCCCR Sync

Default: BCC Cluster Sync

 

SSL Certificate name for this driver instance

Example: cluster2_to_cluster1 BCCCR 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.10.21

Example: cl1svr1.cluster1.clusters.siteA.example

 

Unique IP port to use for this driver instance (same as the value you used for the Cluster1-to-Cluster2 driver instance)

Example: 2002 (default for resource sync)

HINT:Both clusters must use the same port for this connection.

 

Distinguished name of the source cluster for this driver instance

Example: cluster2.clusters.siteB.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.siteB.example

HINT:Browse to select the context.