Configuring Trust Between Partner Clusters

Before you create a partnership between two clusters, you must configure the Geographic Edition software for secure communication between the two clusters. The configuration must be reciprocal. For example, you must configure the cluster cluster-paris to trust the cluster cluster-newyork, and you must also configure the cluster cluster-newyork to trust the cluster cluster-paris.

How to Configure Trust Between Two Clusters

Before You Begin

Ensure that the following conditions are met:

The cluster on which you want to create the partnership is running.
The geoadm start command must have already been run on this cluster and the partner cluster. For more information about using the geoadm start command, see Enabling the Geographic Edition Software.
The cluster name of the partner cluster is known.
The host information of the partner cluster must defined in the local host file. The local cluster needs to know how to reach the partner cluster by name.

If the clusters are in different domains, include the domain name in the entry, as logicalhostname.domainname. However, the cluster name itself must not include the domain.

Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.
For more information about RBAC, see Geographic Edition Software and RBAC.
Note - If you use a role with Geo Management RBAC rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.
```
# chmod A+user:username:rwx:allow /var/cluster/geo
```
The /var/cluster/geo directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.
Import the public keys from the remote cluster to the local cluster.
Running this command on one node of the local cluster imports the keys from the remote cluster to one node of the cluster.
```
# geops add-trust -c remotepartnerclustername
```
-c remotepartnerclustername[.domainname]
Specifies the logical hostname of the cluster with which to form a partnership. The logical hostname is used by the Geographic Edition software and maps to the name of the remote partner cluster. For example, a remote partner cluster name might resemble the following:
cluster-paris
If the clusters are on different domains, also specify the fully qualified domain name. For example, two clusters in a partnership that have different domains might resemble the following:
```
cluster-paris.france
cluster-newyork.usa
```
When you use this option with the add-trust or remote-trust subcommand, the option specifies the alias where the public keys on the remote cluster are stored. An alias for certificates on the remote cluster has the following pattern:
remotepartnercluster.certificate[0-9]*
Keys and only keys that belong to the remote cluster should have their alias match this pattern.
For more information about the geops command, refer to the geops(1M) man page.
Repeat the preceding steps on a node of the remote partner cluster.
If you choose to use Oracle Solaris Cluster Manager, skip this step. Oracle Solaris Cluster Manager handles all nodes in a single operation.
Verify trust from one node of each cluster.
```
# geops verify-trust -c remotepartnerclustername[.domainname]
```
This command verifies the trust from the node on which you run the command to all nodes of the partner cluster. If you choose to use Oracle Solaris Cluster Manager, it verifies the trust from all nodes of the local cluster to all nodes of the partner cluster

How to Remove Trust Between Two Clusters

Before You Begin

Ensure that the following conditions are met:

The cluster on which you want to remove trust is running.
The cluster name of the partner cluster is known.
The host information of the partner cluster must defined in the local host file. The local cluster needs to know how to reach the partner cluster by name.

Become superuser or assume a role that is assigned the Geo Management RBAC rights profile.
For more information about RBAC, see Geographic Edition Software and RBAC.
Note - If you use a role with Geo Management RBAC rights, ensure that the /var/cluster/geo ACLs are correct on each node of both partner clusters. If necessary, become superuser on the cluster node and set the correct ACLs.
```
# chmod A+user:username:rwx:allow /var/cluster/geo
```
The /var/cluster/geo directory must have the correct access control lists (ACL) applied for compatibility between the Geo Management RBAC rights profile and Oracle Data Guard.
If there is a partnership configured between the two clusters, dissolve that partnership.
Run the following command on both clusters:
```
# geops leave
```
On all nodes of both clusters, remove all keys for the remote cluster from the truststore file on the local node.
```
# geops remove-trust -c remotepartnerclustername
```
Perform this step on all the nodes of the local cluster, and then repeat this step on all nodes of the partner cluster.
-c remotepartnerclustername

Specifies the logical hostname of the cluster from which you want to remove the keys. The name for the remote cluster must be identical to the cluster name you specified when adding trust with the geops add-trust command. You do not need to specify the fully qualified name if the remote cluster is reachable by partial name.
When you use this option with the add-trust or remote-trust subcommand, the option specifies the alias where the public keys on the remote cluster are stored. An alias for certificates on the remote cluster has the following pattern:
remotepartnercluster.certificate[0-9]*
Keys and only keys that belong to the remote cluster should have their alias match this pattern.

For more information about the geops command, refer to the geops(1M) man page.
If you choose to use Oracle Solaris Cluster Manager, it handles all nodes of a cluster in a single operation.
Repeat the preceding steps on a node of the remote partner cluster.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Geographic Edition System Administration Guide