Configuring resource groups in HACMP

You can perform the steps described in this section from the command line or through the SMIT configuration utility. See your IBM documentation for information about starting and using the SMIT utility. This document explains how to use SMIT to configure resource groups. See the IBM HACMP for AIX documentation for information about configuring resource groups from the command line.

Shut down the cluster services on both nodes in graceful mode, then log in to the start IP addresses of the primary node as “root” and perform these tasks:

Start SMIT.

From the Cluster Resources screen, select Add a Resource Group if you are creating a new resources group, or select Change/Show a Resource Group if you are changing an existing resources group.

Enter “cascading” in the Node Relationship field, as described below:

Define the Resource Group for the Primary Companion:
Resource Group Name                 [<resgrp1>]
Node Relationship                   [cascading]
Participating Node Names            [<primary_node> <secondary_node>]

Define the Resource Group for the Secondary Companion:
(For Asymmetric Failover Configuration)

Resource Group Name                 [<resgrp2>]
Node Relationship                   [cascading]
Participating Node Names            [<secondary_node>]

(For Symmetric Failover Configuration)
Resource Group Name                 [<resgrp2>]
Node Relationship                   [cascading]
Participating Node Names               [<secondary_node> <primary_node>]

Configure each of the resource groups you defined. In the Application Server field, enter the name of the primary companion. Enter information in all the required fields, such as IP Label, Volume Groups, and File systems. Repeat this step for each of the companions.

Define the primary and secondary companions as application servers in HACMP Cluster Resources. Select either Add Application Server or Change Application Server, and enter these values:

For the Start/Stop Scripts, enter the name of the scripts you created.
For primary and symmetric secondary companions, enter monitor and failover as the arguments for the start and stop scripts, respectively.
For an asymmetric secondary companion, use monitor and stop as the arguments for the start and stop script, respectively.

For example:

Define the Primary Companion Server
Server Name   [<primary_ase>]
Start Script  [/usr/sbin/cluster/events/RUN_<primary_ase>_ha monitor]
Stop Script   [/usr/sbin/cluster/events/RUN_<primary_ase>_ha failover]

Define the Secondary Companion Server:
(For Asymmetric Failover Configuration)
Server Name   [<secondary_ase>]
Start Script  [/usr/sbin/cluster/events/RUN_<secondary_ase>_ha monitor]
Stop Script   [/usr/sbin/cluster/events/RUN_<secondary_ase>_ha stop]

(For Symmetric Failover Configuration)
Server Name  [<secondary_ase>]
Start Script [/usr/sbin/cluster/events/RUN_<secondary_ase>_ha monitor]
Stop Script  [/usr/sbin/cluster/events/RUN_<secondary_ase>_ha failover]

Synchronize the cluster resources. Using SMIT on the node on which you have performed steps 1 through 5, go to the Cluster Resources screen and select Synchronize Cluster Resources. This propagates the changes you made to all the other nodes within the same cluster. In some cases, you may need to stop the HACMP services and restart both nodes before performing the synchronization. Make sure the synchronization does not produce any errors.