IBM Books

Installation and Migration Guide


Task F. Set up and test the HACWS

This section describes the steps you take to customize HACWS and verify its function.

Step 28: Make each control workstation addressable by its host name

Step 29: Set up the HACWS configuration requires each control workstation be addressable by its host name. If the name of the primary control workstation is dutchess.xyz.com, the backup control workstation must be able to communicate with the primary control workstation using the name dutchess.xyz.com. If the name of the backup control workstation is ulster.xyz.com, the primary control workstation must be able to communicate with the backup control workstation using the name ulster.xyz.com.

If either control workstation is not addressable by its host name, you need to enter the appropriate ifconfig command to cause the required name to be temporarily configured as a network interface.

Note:
Do not use SMIT for this step. Using SMIT causes the change to be permanent.

An example of an ifconfig command is as follows:

ifconfig en0 dutchess.xyz.com netmask 255.255.255.192 up

The ifconfig options you need to use are specific to your site. Refer to the ifconfig man page for more information.

Step 29: Set up the HACWS configuration

Configure the primary and backup control workstation as an HACWS configuration.

Note:
Do this step from the primary control workstation.

If using: Do this:.
SMIT

TYPE
smit hacws

* The High Availability Control Workstation Management window appears.

SELECT
Install and Configure HACWS.

ENTER
The node names of the primary control workstation and backup control workstation in the HOSTNAME fields.

SELECT
yes for Execute on both primary and backup?.

PRESS
Ok to complete option selection and install HACWS

install_hacws Enter:
/usr/sbin/hacws/install_hacws -p \
primary_hostname -b backup_hostname -s

Step 30: Customize cluster event processing

Identify the HACMP pre- and post-event scripts provided by HACWS to HACMP.
If using: Do this:.
SMIT

TYPE
smit hacws

* The High Availability Control Workstation Management window appears.

SELECT
Identify Event Scripts to HACMP.

PRESS
Enter to continue.

spcw_addevents Enter:
/usr/sbin/hacws/spcw_addevents

If you want to further customize cluster event processing, follow the instructions in the "Managing a high availability control workstation" chapter in PSSP: Administration Guide.

Step 31: Add IP address aliases

In Step 2: Plan network configuration you planned the network configuration for both control workstations. If your configuration requires IP address aliases, you need to provide the appropriate commands to HACWS. If these commands already existed somewhere else before you installed HACWS, remove them from the old location.

If you need to use an IP address alias to configure the host name of the backup control workstation as a network interface, edit the /etc/rc.backup_cw_alias script on the backup control workstation. This script only runs on the backup control workstation. See the comments in the script for more details. If you make any changes to the /etc/rc.backup_cw_alias script, you must also edit the /etc/rc.net script so /etc/rc.backup_cw_alias runs when the backup control workstation boots. Use an editor to add the following line near the end of the /etc/rc.net file:

/etc/rc.backup_cw_alias

If you need to use an IP address alias to configure a network interface for an SP system partition (SP Switch only), or if you need to configure an IP address alias on the active control workstation for some other reason, edit the /spdata/sys1/hacws/rc.syspar_aliases script. This script runs on the active control workstation before it starts the control workstation services. See the comments in the script for more details.

Step 32: Verify the HACWS configuration

Verify the HACWS configuration.
If using: Do this:.
SMIT

TYPE
smit hacws

* The High Availability Control Workstation Management window appears.

SELECT
Verify HACWS Installation and Configuration.

hacws_verify Enter:
/usr/sbin/hacws/hacws_verify

Step 33: Verify the hardware connections

Verify the connections between the backup control workstation and the frames. Run this step from the backup control workstation.
If using: Do this:.
SMIT

TYPE
smit hacws

* The High Availability Control Workstation Management window appears.

SELECT
Verify Frame to Control Workstation Cabling.

spcw_verify_cabling Type:
/usr/sbin/hacws/spcw_verify_cabling

Step 34: Reboot control workstations

Reboot the primary control workstation. After it finishes booting, reboot the backup control workstation.

Step 35: Start cluster services on the primary control workstation

Follow the instructions in the "Starting and stopping cluster services" chapter of the HACMP for AIX: Administration Guide to start cluster services on the primary control workstation.

Using SMIT:

TYPE
smit clstart

* The Start Cluster Services menu is displayed.

SELECT
now for Start now option.

SELECT
true for Startup Cluster Information Daemon? option.

PRESS
Ok to complete option selection.

Step 36: Verify the HACWS installation

To make sure you installed the HACWS correctly, verify that the control workstation services exist and can move between the primary and backup control workstations.

Verify the control workstation services

Make sure the control workstation services come up on the primary control workstation. Use the following procedure to test them:

  1. Service addresses should be configured on the primary control workstation. Try to telnet to a service address.
  2. /spdata should be mounted on the primary control workstation. To verify this, use the following command:
    df /spdata
    
  3. The SDR should be available. To verify this, use the following command:
    /usr/lpp/ssp/bin/SDRGetObjects SP
    

    The test is successful if you receive output. You can tell whether the startup of the control workstation services has completed by issuing the command:

    grep "SPCW_APPS COMPLETE" /tmp/hacmp.out
    

Start cluster services on the backup control workstation

Once control workstation services have completely started on the primary control workstation, start cluster services on the backup control workstation by following the procedure described in Step 35: Start cluster services on the primary control workstation.

Cause a failover

After cluster services have started on the primary control workstation, direct HACMP to move control workstation services to the backup control workstation.

Using SMIT:

TYPE
smit clstop

* The Stop Cluster Services menu is displayed.

SELECT
now for Stop now option.

SELECT
takeover for Shutdown mode option.

PRESS
Ok to complete option selection.

This should stop cluster services on the primary control workstation and move control workstation services to the backup control workstation. Make sure control workstation services move to the backup. On the backup control workstation, follow the procedure described in Verify the control workstation services.

When you are finished testing, restart cluster services on the primary control workstation by following Step 35: Start cluster services on the primary control workstation.

Note:
The first time you start control workstation services on the backup control workstation, the spcw_apps command runs and takes about a half hour to complete. You must wait for it to complete before you move control workstation services back to the primary control workstation. You can tell whether the command completed by issuing the following command:
grep "SPCW_APPS COMPLETE" /tmp/hacmp.out

Once the startup of the control workstation services has completed on the backup control workstation, you can restart cluster services on the primary control workstation and then move control workstation services back to the primary control workstation. When you have completed testing, make sure to restart cluster services on both control workstations.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]