Chapter 3 Enabling and Configuring the Sun Cluster Geographic Edition Software

This chapter describes the steps for enabling and configuring the Sun Cluster Geographic Edition infrastructure. This chapter contains the following sections:

• Enabling the Sun Cluster Geographic Edition Infrastructure

• Configuring Trust Between Partner Clusters

Enabling the Sun Cluster Geographic Edition Infrastructure

When Sun Cluster Geographic Edition software is enabled, the cluster is ready to enter a partnership with another enabled cluster. You can use the CLI or the GUI to create a cluster partnership.

For more information about setting up and installing Sun Cluster Geographic Edition, see Chapter 3, Administering the Sun Cluster Geographic Edition Infrastructure, in Sun Cluster Geographic Edition System Administration Guide.

To use the geoadm command to enable the local cluster for partnership membership, you must have superuser access.

How to Enable Sun Cluster Geographic Edition Software

This procedure enables the Sun Cluster Geographic Edition infrastructure on the local cluster only. Repeat this procedure on all the clusters of your geographically separated cluster.

Before You Begin

Ensure that the following conditions are met:

• The cluster is running the Solaris Operating System and Sun Cluster software.

• The Sun Cluster management-agent container for Sun Cluster Manager is running.

• Sun Cluster Geographic Edition software is installed.

• The cluster has been configured for secure cluster communication by using security certificates, that is, nodes within the same cluster must share the same security certificates. This is configured during Sun Cluster installation.

  However, when you upgrade to Sun Cluster 3.2 11/09 software, you must copy the security certificates manually from one node of the cluster to the other nodes of the cluster. This action restores identical security certificates on all nodes. For more information about copying the security files for the common agent container, see the procedures in How to Finish Upgrade to Sun Cluster 3.2 11/09 Software in Sun Cluster Upgrade Guide for Solaris OS.

1. Become superuser on a cluster node.

2. Ensure that the logical hostname, which is the same as the cluster name, is available and defined.

   # cluster list

   If the cluster name is not the name that you want to use, change the cluster name with the following command:

   # cluster rename -c newclustername clustername

   -c newclustername

   Specifies the new cluster name.

   clustername

   The cluster whose name you are changing.

   For more information, see the cluster(1CL) man page.

   ---

   Note –

   After you have enabled the Sun Cluster Geographic Edition infrastructure, you must not change the cluster name while the infrastructure is enabled.

   ---

3. Confirm that the naming service and the local hosts files contain a host entry that matches the cluster name.

   The local hosts file, hosts, is located in the /etc/inet directory.

4. On a node of the cluster, start the Sun Cluster Geographic Edition infrastructure.

   # geoadm start

   The geoadm start command enables the Sun Cluster Geographic Edition infrastructure on the local cluster only. For more information, see the geoadm(1M) man page.

5. Verify that you have enabled the infrastructure and that the Sun Cluster Geographic Edition resource groups are online.

   # geoadm show # clresourcegroup status geo-clusterstate geo-infrastructure # clresource status -g geo-clusterstate,geo-infrastructure

   The output for the geoadm show command displays that the Sun Cluster Geographic Edition infrastructure is active from a particular node in the cluster.

   The output for the clresourcegroup status and clresource status commands display that the geo-failovercontrol, geo-hbmonitor, and geo-clustername resources and the geo-infrastructure resource group is online on one node of the cluster. The geo-clusterstate resource group is online on both nodes.

   For more information, see the clresourcegroup(1CL) and clresource(1CL) man pages.

Example 3–1 Enabling the Sun Cluster Geographic Edition Infrastructure on a Cluster

This example enables Sun Cluster Geographic Edition software on the cluster-paris cluster.

1. Start the Sun Cluster Geographic Edition infrastructure on cluster-paris.

   phys-paris-1# geoadm start

2. Ensure that the Sun Cluster Geographic Edition infrastructure was successfully enabled.

   phys-paris-1# geoadm show --- CLUSTER LEVEL INFORMATION --- Sun Cluster Geographic Edition is active on cluster-paris from node phys-paris-1 Command execution successful phys-paris-1#

3. Verify the status of the Sun Cluster Geographic Edition resource groups and resources.

   phys-paris-1# clresourcegroup status geo-clusterstate geo-infrastructure === Cluster Resource Groups === Group Name Node Name Suspended Status ---------- --------- --------- ------ geo-clusterstate phys-paris-1 No Online phys-paris-2 No Online geo-infrastructure phys-paris-1 No Online phys-paris-2 No Offline phys-paris-1# clresource status -g geo-clusterstate,geo-infrastructure === Cluster Resources === Resource Name Node Name State Status Message ------------- --------- ----- -------------- geo-clustername phys-paris-1 Online Online - LogicalHostname online. phys-paris-2 Offline Offline geo-hbmonitor phys-paris-1 Online Online - Daemon OK phys-paris-2 Offline Offline geo-failovercontrol phys-paris-1 Online Online - Service is online. phys-paris-2 Offline Offline

Next Steps

Configure trust between partner clusters. Go to How to Configure Trust Between Two Clusters.

Configuring Trust Between Partner Clusters

Before you create a partnership between two clusters, you must configure Sun Cluster 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 has already been run on this cluster and the partner cluster. For more information about using the geoadm start command, see Enabling the Sun Cluster Geographic Edition Infrastructure.

• The cluster name of the partner cluster is known.

• The host information of the partner cluster is defined in the local hosts file. The local cluster needs to know how to reach the partner cluster by name.

1. Become superuser on a cluster node.

2. Import the public keys from the remote cluster to the local cluster.

   Run the following command on one node of the local cluster to import the keys from the remote cluster to one node of the cluster.

   # geops add-trust -c remotecluster

   -c remotecluster

   Specifies the logical hostname of the cluster with which to form a partnership. The logical hostname is used by Sun Cluster 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

   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:

   remotecluster.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.

3. Repeat the preceding steps on a node of the remote partner cluster.

4. Verify trust from one node of each cluster.

   # geops verify-trust -c remotecluster

Next Steps

Configure and join the partnership. See Chapter 5, Administering Cluster Partnerships, in Sun Cluster Geographic Edition System Administration Guide.

See Also

To remove a partnership between two clusters, see How to Remove Trust Between Two Clusters in Sun Cluster Geographic Edition System Administration Guide.