How to Join a Partnership

Before You Begin

Before you can configure a cluster to join a partnership, ensure that the following conditions are met:

• The local cluster is enabled to run the Sun Cluster 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.

• Security has been configured on the clusters by installing the appropriate certificates.

  See Configuring Secure Cluster Communication Using Security Certificates for more information.

When you create or join multiple partnerships, do not use port numbers that are being used by other partnerships. All tcp_udp requests go through the RPC server and the tcp_udp_resp is created on the remote cluster with the port number defined for the local cluster. Use an unused port number and ensure that the port number is not registered with the Internet Assigned Numbers Authority (IANA).

The Sun Cluster Geographic Edition software uses the port in the CCR table rather than reading from the XML file, so when you change the port number, you must reset the configuration by deleting the partnership and manually update the XML information.

Steps

1. Log in to one of the nodes of the cluster that is to join the partnership.

   You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC.

2. Confirm that the cluster to be joined, cluster-paris, can be reached at its logical hostname.

   # ping lh-paris-1

   For information about the logical hostname of the cluster, see How to Enable Sun Cluster Geographic Edition Software.

3. Join an existing partnership.

   # geops join-partnership [-h heartbeat-name] remote-cluster-name partnership-name

   -h heartbeat-name

   Specifies an identifier to a custom heartbeat plug-in on a partner cluster that the local cluster can use to monitor the partner cluster's availability

   Custom heartbeats are provided for special circumstances and require careful configuration. Consult your Sun specialist for assistance if your system requires the use of custom heartbeats. For more information about configuring custom heartbeats, see Chapter 12, Administering Heartbeats.

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

   remote-cluster-name

   Specifies the name of a cluster that is currently a member of the partnership being joined, from which the partnership configuration information will be retrieved

   partnership-name

   Specifies the name of the partnership

   For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities.

   For more information about the geops command, refer to the geops(1M) man page.

4. Verify that the cluster was added to the partnership and that the partnership properties were defined correctly.

   # geops list # geoadm status

Example 5–3 Joining a Partnership

The following example illustrates how cluster-newyork joins the partnership that was created on cluster-paris in Example 5–1.

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