Sun Cluster Geographic Edition System Administration Guide

Chapter 3 Administering the Sun Cluster Geographic Edition Infrastructure

This chapter contains information about enabling your cluster for participation in a partnership. It also contains information for disabling the Sun Cluster Geographic Edition software so that your cluster no longer can participate in partnerships.

This chapter contains the following sections:

Sun Cluster Geographic Edition Infrastructure Resource Groups

When you enable the Sun Cluster Geographic Edition infrastructure, the following Sun Cluster resource groups are created:

geo-clusterstate – A scalable resource group that the Sun Cluster Geographic Edition software uses to distinguish between node failover and cluster reboot scenarios. This resource group does not contain any resources.
geo-infrastructure – A failover resource group that encapsulates the Sun Cluster Geographic Edition infrastructure. The resource group contains the following resources:
- geo-clustername – The logical hostname for the Sun Cluster Geographic Edition software. The Sun Cluster Geographic Edition software uses the logical hostname of a cluster for inter-cluster management communication and heartbeat communication. An entry in the naming services must be the same as the name of the cluster and be available on the namespace of each cluster.
- geo-hbmonitor – Encapsulates the heartbeat processes for the Sun Cluster Geographic Edition software.
- geo-failovercontrol – Encapsulates the Sun Cluster Geographic Edition software itself. The Sun Cluster Geographic Edition module uses this resource to load into the common agent container.

These resources are for internal purposes only, so you must not change them.

These internal resources are removed when you disable the Sun Cluster Geographic Edition infrastructure.

You can monitor the status of these resources by using the scstat -g command. For more information about this command, see the scstat(1M) man page.

Enabling the Sun Cluster Geographic Edition Software

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

For more information about setting up and installing the Sun Cluster Geographic Edition software, see the Sun Cluster Geographic Edition Installation Guide.

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 the Sun Cluster software.
The Sun Cluster management-agent container for SunPlex Manager is running.
The 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 done during Sun Cluster installation.

When you upgrade to Sun Cluster 3.1 8/05 software, the security certificates must be identical on all nodes of the cluster. Therefore, you must copy the security certificates manually from one node of the cluster to the other nodes of the cluster. For more information on copying the security files for the common agent container, see the procedures in Chapter 5, Upgrading Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS.

Log in to a cluster node.

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

Ensure that the logical hostname, which is the same as the cluster name, is available and defined.
# scconf -p | grep -i "cluster name"
If the cluster name is not the name you want to use, you can change the cluster name with the following command:
# scconf -c -C cluster=clustername
For more information, see the scconf(1M) 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.

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

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

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.

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

For a list of the Sun Cluster Geographic Edition resource groups, see Sun Cluster Geographic Edition Infrastructure Resource Groups.
# geoadm show # scstat -g
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 scstat -g command displays that the geo-failovercontrol, geo-hbmonitor, and geo-clustername resources and the geo-infrastructure resource groups are online on one node of the cluster.

For more information, see the scstat(1M) man page.

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

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

Start the Sun Cluster Geographic Edition software on cluster-paris.
phys-paris-1# geoadm start

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#

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

phys-paris-1# scstat -g  
-- Resource Groups and Resources --
      Group Name              Resources
      -----------	      --------- 
Resources: geo-clusterstate    - 
Resources: geo-infrastructure geo-clustername geo-hbmonitor geo-failovercontrol
 
-- Resource Groups --
     Group Name            Node Name       State
     -----------           ---------       -----
Group: geo-clusterstate   phys-paris-1    Online
Group: geo-clusterstate   phys-paris-2    Online
Group: geo-infrastructure phys-paris-1    Online
Group:geo-infrastructure  phys-paris-2    Offline

-- Resources --    
Resource Name                 Resources    State   Status Message
-------------                 ---------    -----   --------------
Resource: geo-clustername     phys-paris-1 Online  Online - LogicalHostname online
Resource: geo-clustername     phys-paris-2 Offline Offline
Resource: geo-hbmonitor       phys-paris-1 Online  Online- Daemon OK
Resource: geo-hbmonitor       phys-paris-2 Offline Offline
Resource: geo-failovercontrol phys-paris-1 Online  Online
Resource: geo-failovercontrol phys-paris-2 Offline Offline

Next Steps

For information about creating protection groups, see the Sun Cluster Geographic Edition Data Replication Guide that corresponds to the type of data replication software you are using.

Disabling the Sun Cluster Geographic Edition Software

You can disable the Sun Cluster Geographic Edition infrastructure by using the following procedure.

How to Disable the Sun Cluster Geographic Edition Software

Before You Begin

Ensure that all protection groups on the local cluster are offline.

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.

Confirm that all of the protection groups are offline on the local cluster.
phys-paris-1# geoadm status
For more information about the geoadm status command and its output, see Monitoring the Runtime Status of the Sun Cluster Geographic Edition Software.

Caution –
If you want to keep the application resource groups online while deactivating a protection group, follow the procedure described in the following data replication guides:

Disable the Sun Cluster Geographic Edition software.
phys-paris-1# geoadm stop
This command removes the infrastructure resource groups that were created when you enabled the Sun Cluster Geographic Edition infrastructure.

For more information about this command, see the geoadm(1M) man page.

Note –
Disabling the Sun Cluster Geographic Edition software removes only the infrastructure resource groups. Resource groups that have been created to support data replication are not removed unless you remove the protection group that the resource groups are supporting by using the geopg delete command.

Verify that the software was disabled and that the Sun Cluster Geographic Edition resource groups are no longer displayed.
phys-paris-1# geoadm show phys-paris-1# scstat -g
For more information, see the scstat(1M) man page.

Example 3–2 Disabling a Cluster

This example disables the cluster-paris cluster.

Confirm that all protection groups are offline.

phys-paris-1# geoadm status

Cluster: cluster-paris

Partnership "paris-newyork-ps" :OK
   Partner clusters   :cluster-newyork
   Synchronization    :OK
   ICRM Connection    :OK

   Heartbeat "paris-to-newyork" monitoring "cluster-newyork":OK
       Heartbeat plug-in "ping_plugin"   :Inactive
       Heartbeat plug-in "tcp_udp_plugin":OK

Protection group "tcpg"      :OK
    Partnership              :paris-newyork-ps
    Synchronization          :OK

    Cluster cluster-paris    :OK
        Role                 :Primary
        PG activation state  :Deactivated
        Configuration        :OK
        Data replication     :OK
        Resource groups      :OK


    Cluster cluster-newyork  :OK
        Role                 :Secondary
        PG activation state  :Deactivated
        Configuration        :OK
        Data replication     :OK
        Resource groups      :OK

Disable the Sun Cluster Geographic Edition infrastructure.

phys-paris-1# geoadm stop
... verifying pre conditions and performing pre remove operations ... done
...removing product infrastructure ... please wait ...

Confirm that the Sun Cluster Geographic Edition infrastructure was successfully disabled.

phys-paris-1# geoadm show

--- CLUSTER LEVEL INFORMATION ---
Sun Cluster Geographic Edition is not active on cluster-paris

--- LOCAL NODE INFORMATION ---
Node phys-paris-1 does not host active product module.

Command execution successful
phys-paris-1#

Verify that Sun Cluster Geographic Edition resource groups and resources have been removed.
phys-paris-1# scstat -g phys-paris-1#

Checking the Status of the Sun Cluster Geographic Edition Infrastructure

Use the geoadm show command to determine whether the Sun Cluster Geographic Edition infrastructure is enabled on the local cluster and on which node the infrastructure is active. The Sun Cluster Geographic Edition infrastructure is considered active on the node on which the geo-infrastructure resource group has a state of Online.

Example 3–3 Displaying Whether the Sun Cluster Geographic Edition Infrastructure Has Been Enabled

This example displays information on the phys-paris-1 node of the cluster-paris cluster.

phys-paris-1# geoadm show

--- CLUSTER LEVEL INFORMATION ---
Sun Cluster Geographic Edition is active on:  
node phys-paris-2, cluster cluster-paris

Command execution successful
phys-paris-1#

Booting a Cluster

The following events take place when you boot a cluster:

After the Sun Cluster infrastructure is enabled, the Sun Cluster Geographic Edition software starts automatically. Verify that the software started successfully by using the geoadm show command.
The heartbeat framework checks which partners it can reach.
Check the current status of the cluster by using the geoadm status command. For more information about this command and its output, see Monitoring the Runtime Status of the Sun Cluster Geographic Edition Software.

Applying Patches to a Sun Cluster Geographic Edition System

Complete the following steps when you apply patches to your Sun Cluster Geographic Edition system.

Shut down the Sun Cluster Geographic Edition infrastructure by using the geoadm stop command.

Shutting down the infrastructure ensures that a patch installation on one cluster does not affect the other cluster in the partnership.
Apply the patches by using the patchadd command.

If you are applying Sun Cluster patches, use the Sun Cluster methods on both clusters.

Note –
Apply patches to the secondary cluster first to ensure that errors do not affect the services on the primary cluster. After you have verified the installation, apply the patches to the primary cluster.
Restart the Sun Cluster Geographic Edition infrastructure by using the geoadm start command.