Joining an Existing Partnership

Language:

When you define and configure a partnership, the partnership specifies a second cluster to be a member of that partnership. Then, you must configure this second cluster to join the partnership.

How to Join a Partnership

Note - You can also accomplish this procedure by using the Oracle Solaris Cluster Manager browser interface. Click Partnerships, then click Join Partnership. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager in Oracle Solaris Cluster 4.3 System Administration Guide.

Before You Begin

Ensure that the following conditions are met:

The local cluster is enabled to run the Geographic Edition software.
The partnership you want the cluster to join is defined and configured on another cluster (cluster-paris) and the local cluster (cluster-newyork) is specified as a member of this partnership. See Creating a Partnership.
If a partner cluster is a zone cluster, either application-based replication, such as Oracle Data Guard, or EMC Symmetrix Remote Data Facility storage-based replication is configured, or no data replication is used.
Security has been configured on the clusters by installing the appropriate certificates.

See Security Certificates in Oracle Solaris Cluster 4.3 Geographic Edition Installation and Configuration Guide for more information.

Log in to a node of the cluster that is joining the partnership.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Planning Security.
Confirm that the remote cluster that originally created the partnership, cluster-paris, can be reached at its logical hostname.
```
local-partner-cluster# ping lh-paris-1
```
For information about the logical hostname of the cluster, see How to Enable the Geographic Edition Framework.
Join the partnership.
```
local-partner-cluster# geops join-partnership [-h heartbeat] remote-partner-cluster partnership
```
–h heartbeat

Specifies a custom heartbeat to use in the partnership to monitor the availability of the partner cluster.

If you omit this option, the default Geographic Edition heartbeat is used.

Custom heartbeats are provided for special circumstances and require careful configuration. Consult your Oracle specialist for assistance if your system requires the use of custom heartbeats. For more information about configuring custom heartbeats, see Chapter 5, Administering Heartbeats and Heartbeat Plug-Ins in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.

If you create a custom heartbeat, you must add at least one plug-in to prevent the partnership from remaining in degraded mode.

You must configure the custom heartbeat that you provide in this option before you run the geops command.

remote-partner-cluster

Specifies the name of a cluster that is currently a member of the partnership that is being joined. This cluster is used to retrieve the partnership configuration information.

partnership

Specifies the name of the partnership.

For information about the names and values that are supported by Geographic Edition software, see Legal Names and Values of Geographic Edition Entities in Oracle Solaris Cluster 4.3 Geographic Edition System Administration Guide.

For more information about the geops command, refer to the geops (1M) man page.
Verify that the cluster was added to the partnership and that the partnership properties were defined correctly.
```
local-partner-cluster# geops list
local-partner-cluster# geoadm status
```

Example 4 Joining a Partnership

This example joins the cluster-newyork cluster to the paris-newyork-pspartnership.

phys-newyork-1# geops join-partnership cluster-paris paris-newyork-ps
phys-newyork-1# geops list
phys-newyork-1# geoadm status

Example 5 Creating and Joining a Partnership With a Remote Cluster in a Different Domain

This example creates and configures the paris-newyork-ps partnership between clusters cluster-paris.france.example.com and cluster-newyork.usa.example.com.

On one node of cluster-paris.france.example.com, configure trust for the partnership.
```
phys-paris-1# geops add-trust -c cluster-newyork.usa.example.com
```
On one node of cluster-newyork.usa, configure trust for the partnership.
```
phys-newyork-1# geops add-trust -c cluster-paris.france.example.com
```

On each node of both clusters, verify that trust has been set up properly, both between the local cluster and partner cluster and among nodes of the local cluster.

phys-newyork-1# geops verify-trust -c cluster-paris.france.example.com
phys-newyork-2# geops verify-trust -c cluster-paris.france.example.com
phys-newyork-1# geops verify-trust
phys-newyork-2# geops verify-trust

phys-paris-1# geops verify-trust -c cluster-newyork.usa.example.com
phys-paris-2# geops verify-trust -c cluster-newyork.usa.example.com
phys-paris-1# geops verify-trust
phys-paris-2# geops verify-trust

On cluster-paris.france.example.com, create the partnership paris-newyork-ps.

cluster-paris# geops create -c cluster-newyork.usa.example.com \
-p Description=Transatlantic \
-p Notification_emailaddrs=sysadmin@example.com 
paris-newyork-ps

On cluster-newyork.usa, join the partnership paris-newyork-ps.

cluster-newyork# geops join-partnership cluster-paris.france.example.com
paris-newyork-ps

Verify that the partnership has been created successfully.
```
# geops list
# geoadm status
```

Next Steps

Configure protection groups. See Configuring Protection Groups and the Geographic Edition manual for the data replication product you will use.