test

Sun Cluster Geographic Edition System Administration Guide

Creating and Modifying a Partnership

A partnership establishes heartbeat monitoring between two clusters that are running Sun Cluster Geographic Edition software. Clusters in a partnership exchange heartbeats to monitor each other's presence.

You create a partnership with the geops(1m) command. After you have created a partnership, you can use this command to modify the properties of this partnership.

The names of the application resource groups that are managed by the Sun Cluster Geographic Edition software must be the same on both partner clusters. You can configure the names of these resource groups manually or by using the scsnapshot command.

The scsnapshot command replicates configuration data on a cluster that does not have configured resource groups, resource types, and resources. The scsnapshot command retrieves the configuration data from the cluster on which it is launched and generates a script called scriptfile. Edit the script to adapt it to the specific features of the cluster where you want to replicate the configuration data. For example, if you change the IP address and host names in the script, you can launch the script from any node in the cluster where you want to replicate the configuration data. For more information about using this command, see the scsnapshot(1M) man page.

You can configure a partnership between only two clusters, and only one partnership can be defined between a given pair of clusters. A single cluster can participate in multiple partnerships.

ProcedureHow to Create a Partnership

Before You Begin

Before you can create a partnership between two clusters, ensure that the following conditions are met:

Note –

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 a cluster node.

    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. If the default port is being used by another application or if you are creating multiple partnerships on a cluster, change the port number as follows:

    1. If a partnership exists, leave the partnership.


      # geops leave-partnership paris-newyork-ps

    2. On all the nodes of the cluster, change the value of the tcp_udp.port in the /etc/opt/SUNWcacao/modules/com.sun.cluster.agent.geocontrol.xml file to the port you want the partnership to use.

      Only one heartbeat can use the default port. If a partnership's heartbeat is using the default port, the other partnership's heartbeat must be created with a specific port. The port you specify in the file must be a port that is not used by any application other than the Sun Cluster Geographic Edition software.

      If the cluster participates in more than one partnership, ensure that the port number is different from the other partners.

    3. Restart the common agent container on all the nodes of the cluster.


      # /opt/SUNWcacao/bin/cacaoadm restart

  3. Create the partnership.


    # geops create -c remote-partner-cluster-name [-h heartbeat-name] \
[-p property-setting [-p...]] partnership-name
    -c remote-cluster-name

    Specifies the name of the remote cluster that will participate in the partnership

    This name matches the logical hostname used by the Sun Cluster Geographic Edition infrastructure on the remote cluster.

    -h heartbeat-name

    Specifies a custom heartbeat to be used in the partnership to monitor the partner cluster's availability

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

    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.

    The custom heartbeat that is specified by this option must already be configured before running the geops command.

    Note –

    The presence of a custom heartbeat prevents the default heartbeat from being used during partnership creation. If you want to use the default heartbeat for your partnership, you must delete the custom heartbeat before running the geops create command.

    -p property-setting

    Sets the value of partnership properties with a string of property=value pair statements

    Specify a description of the partnership with the Description property.

    You can configure heartbeat-loss notification with the Notification_emailaddrs and Notification_actioncmd properties. For more information about configuring heartbeat-loss notification, see Configuring Loss of Heartbeat Notification.

    For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.

    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 partnership was created and the status of the partnership.


    # geoadm status
Example 5–1 Creating a Partnership

The following example illustrates the creation of the partnership, paris-newyork-ps, on cluster-paris:


# geops create -c cluster-newyork -p Description=Transatlantic \
-p Notification_emailaddrs=sysadmin@companyX.com paris-newyork-ps 
# geoadm status

ProcedureHow to Modify Partnership Properties

Steps

  1. Log in to one of the cluster nodes.

    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. Modify partnership properties.


    # geops set-prop -p property-setting [-p...] partnership-name
    -p property-setting

    Sets the value of partnership properties with a string of property=value pair statements

    Specify a description of the partnership with the Description property.

    You can configure heartbeat-loss notification with the Notification_emailaddrs and Notification_actioncmd properties. For more information about configuring heartbeat-loss notification, see Configuring Loss of Heartbeat Notification.

    For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties.

    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.

  3. Verify that your modification was made correctly.


    # geops list
Example 5–2 Modifying the Properties of a Partnership

The following example illustrates how to modify the notification email address for cluster-paris:


# geops set-prop -p Notification_emailaddrs=operations@companyX.com \
paris-newyork-ps
# geops list