IBM Books

Installation and Migration Guide


|Migrating an HACWS configuration to PSSP 3.4

Follow the steps in this section if you are upgrading an HACWS configuration from PSSP 2.4, |PSSP 3.1.1, or PSSP 3.2 to PSSP |3.4.

Prerequisites

Before following the instructions in this section, you should:

  1. Read Preparing to migrate and follow the instructions which describe how to prepare to migrate your SP system.
  2. Read HACWS migration strategy and plan your HACWS migration strategy.
  3. Read High-level HACWS migration instructions and perform all of the tasks that must be done prior to upgrading the PSSP software level of your HACWS configuration.

Step 1: Verify the authentication value for AIX remote commands

|An authentication method must be set in order for remote commands to |work properly. If your SP system contains nodes at PSSP |3.1.1 or earlier, the Kerberos V4 value must be set. For |SP systems containing nodes at PSSP 3.2 or later, any value is valid |(Kerberos V5, Kerberos V4, or Standard AIX).

|If the value is not set, use the chauthent command to |enable k4. Issue:

chauthent -k4 -std

|Perform this step for both control workstations.

Step 2: Verify network tunable values

The suggested network tunable values for your control workstations are as follows:

sb_max               163840
ipforwarding              1
tcp_sendspace         65536
tcp_recvspace         65536
udp_sendspace         32768
udp_recvspace         65536
tcp_mssdflt            1448
tcp_pmtu_discover         0
udp_pmtu_discover         0

Verify that the network tunable values on both control workstations are correct. Use the no command to display these values. To display all of the network tunable values at once, issue the command:

/usr/sbin/no -a

To change the value of the thewall network tunable to 16384, issue the command:

/usr/sbin/no -o thewall=16384

When you change a network tunable value, the change takes effect immediately. However, the change is not preserved across a reboot. To make the change permanent, add the required no command to the bottom of the /etc/rc.net script. Refer to the no command man page for more information about changing network tunable values.

Step 3: Review space requirements for NIM boot images

Follow the instructions in Step 7: Review space requirements for NIM boot images.

Step 4: Review space requirements for /spdata

Follow the instructions in Step 9: Review space requirements for /spdata.

Step 5: Create the required /spdata directories

Follow the instructions in Step 10: Create the required /spdata directories.

Step 6: Copy the AIX LP images and other required AIX LPs and PTFs

Follow the instructions in Step 11: Copy the AIX 4.3.3 LP images and other required AIX LPs and PTFs.

Step 7: Install the correct level of PAIDE on both control workstations

For both control workstations, follow the instructions in Step 12: Install correct level of PAIDE on the control workstation.

|Step 8: Copy the PSSP images for PSSP 3.4

Follow the instructions in Step 13: Copy the PSSP images for PSSP 3.4.

|Step 9: Install the runtime prerequisites

| |

|Follow the instructions in Step 14: Install the runtime prerequisites. Perform this step for both control |workstations.

Step 10: Install (copy) the basic AIX (mksysb) image

Follow the instructions in Step 15: Install (copy) the basic AIX (mksysb) image.

Step 11: Start control workstation services on the primary control workstation

If you have not already done so, make sure that HACMP is running on both control workstations and the primary control workstation is the active control workstation, or the one that is providing the control workstation services.

Step 12: Stop control workstation services while HACMP is running

While HACMP is still running, you need to stop the control workstation applications on both control workstations. While the primary control workstation is the active control workstation, the backup control workstation will act as a client of the primary control workstation. You need to turn this off by issuing the following command on the backup control workstation:

/usr/sbin/hacws/spcw_apps -d

Next, you need to stop control workstation services on the primary control workstation by issuing the same command on the primary control workstation.

Step 13: Install PSSP on both control workstations

You need to install the |PSSP 3.4 file sets on both control workstations. When the PSSP file sets are installed, files are copied into the /spdata/sys1 directory. This requires special consideration for an HACWS configuration, because both control workstations share the same /spdata file system, which resides in a shared volume group. At this point, the /spdata file system should be mounted on the primary control workstation, so files copied to the /spdata/sys1 directory on the primary control workstation get written to the shared /spdata file system, and files copied to the /spdata/sys1 directory on the backup control workstation get written to the backup control workstation's / (or root) file system. Since both control workstations share the same /spdata file system, the files that are copied to the backup control workstation are not needed, and they will get removed later by the install_hacws command in Step 16: Complete PSSP installation on both control workstations. In the meantime, you need to make sure there is at least 4 MB of free space in the / (or root) file system on the backup control workstation, or installation on the backup control workstation may fail.

You can install the |PSSP 3.4 file sets on the primary control workstation from either the |/spdata/sys1/install/pssplpp/PSSP-3.4 directory, which is in the locally mounted /spdata file system, or you can install directly from the installation media. However, IBM suggests that you install the |PSSP 3.4 file sets on the backup control workstation directly from the installation media. You should not mount the /spdata file system on the backup control workstation to install PSSP. Now you may proceed to install the |PSSP 3.4 file sets on both control workstations. Remember that you must also install the |ssp.hacws 3.4.0.0 file set on both control workstations. You can perform file set installation from the command line by issuing the installp command, or you can use SMIT by issuing the smit install_latest command. Refer to the AIX Installation Guide for more details on how to use these commands.

|Step 14: Authenticate as the Kerberos V4 administrative principal

| |

|To get the Kerberos V4 administrative principal, follow the instructions in |Step 17: Obtain credentials.

Step 15: Set authentication methods for SP Trusted Services

|If your starting PSSP level is earlier than PSSP 3.2, the |authentication method for SP Trusted Services may not have been set. To |determine if the authentication method was previously set, issue the |lsauthts command. |If the response is compat, you can skip this |step. If the authentication method for SP Trusted Services is not set to |compat and you are migrating from a version of PSSP earlier than PSSP |3.2, issue the chauthts command. Issue:

chauthts compat

Step 16: Complete PSSP installation on both control workstations

|Run the install_hacws command. The |install_hacws command runs SDR_init which logs information |in /var/adm/SPlogs/SDR/SDR_config.log.
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

Note:
Do this step from the primary control workstation.

Step 17: Verify the authentication values in the SDR

|Follow the instructions in Step 21: Verify the authentication values in the SDR.

Step 18: Verify the HACWS configuration

Run the hacws_verify command.
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

Note:
The hacws_verify command requires that the primary control workstation must be the active control workstation, or the one which is currently providing the control workstation services. If control workstation services are being provided by the backup control workstation, you cannot run this command.

Step 19: Run SDR and System Monitor verification test

Follow the instructions in Step 22: Run SDR and System Monitor verification test.

Step 20: Configure PSSP services and set up the site environment

Follow the instructions in Step 23: Configure PSSP services and set up the site environment.

Step 21: Update the state of the supervisor microcode

Follow the instructions in Step 24: Update the state of the supervisor microcode.

Step 22: Restart control workstation services

Start control workstation services on the primary control workstation by issuing the following command:

/usr/sbin/hacws/spcw_apps -u

After this command completes on the primary control workstation, get the backup control workstation to synchronize with the primary control workstation by issuing the same command on the backup control workstation.

Step 23: Recycle the Event Manager daemons

|In order to monitor any new PSSP 3.4 hardware and to utilize |the latest configuration database for Perspectives, you should perform the |following steps at this time:

  1. |Stop the Event Manager daemons in the systems partitions that contain the |new hardware.

    |Issue /usr/sbin/rsct/bin/haemctrl -k on the control workstation |and on each of the nodes in the system partition. For PSSP 2.4 |or earlier, issue /usr/lpp/ssp/bin/haemctrl -k on the control |workstation and on each of the nodes in the system partition.

    |You can use the dsh or Sysctl commands to run the command |on multiple nodes from the control workstation. For more information on |using these commands, see the "Parallel Management commands" chapter |in PSSP: Administration Guide.

  2. |Verify that all of the Event Manager daemons in each system partition have |stopped.

    |On the control workstation, issue the lssrc -s |haem.domain_name command. On the nodes, issue the |lssrc -s haem command.

    |You can use the dsh or Sysctl commands to run the command |on multiple nodes from the control workstation. For more information on |using these commands, see the "Parallel Management commands" chapter |in the PSSP: Administration Guide.

    |The status of each daemon should indicate that it is inactive.

  3. |Restart the Event Manager daemons in each system partition.

    |Issue /usr/sbin/rsct/bin/haemctrl -s on the control workstation |and on each of the nodes in the system partition. For PSSP 2.4 |or earlier, issue /usr/lpp/ssp/bin/haemctrl -s on the control |workstation and on each of the nodes in the system partition.

    |You can use the dsh or Sysctl commands to run the command |on multiple nodes from the control workstation. For more information on |using these commands, see the "Parallel Management commands" chapter |in PSSP: Administration Guide.

|Step 24: Refresh the pmand daemons (PSSP 2.4 only)

Follow the instructions in Step Step 26: Refresh the pmand daemons (PSSP 2.4 only).

Step 25: Run verification tests

Follow the instructions in Step 28: Run verification tests.

|Step 26: Validate the network adapters

| |

|Follow the instructions in Step 30: Validate the network adapters.

Step 27: Validate the control workstations

Your migration to |PSSP 3.4 is now complete. You should test your HACWS configuration by performing a control workstation failover from the primary control workstation to the backup control workstation, and then failover from the backup control workstation back to the primary control workstation. Perform additional failover testing as needed. Refer to Step 31: Validate the control workstation for additional instructions.

At this point, refer back to High-level migration steps to determine the next step in your SP system migration process.


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