Installation

PE Installation Overview

Installation on an IBM RS/6000 SP is different from installation on an IBM pSeries or RS/6000 network cluster. The main difference is that an SP installation allows you to use the SP system management functions to manage and maintain the system software. These functions, however, are not available on an IBM pSeries or RS/6000 network cluster.

In both environments, you first install the desired PE filesets on a single node. When that installation is complete, you can then replicate the installation image throughout the remaining nodes, using one of the suggested methods described in this chapter.

About Installing PE on an SP System

You can install the desired PE filesets on an SP in one of three ways:

• Use the SP system management software; this allows you to control and automate much of the software maintenance throughout your system.

  To use this method, refer to the chapter on "Performing Software Maintenance" in IBM Parallel System Support Programs for AIX: Installation and Migration Guide.

• Use the PEinstallSP script.
• Install the software on each node individually using SMIT or installp.

In any event, you must first install the PE filesets on at least one node of your system. Preferably, install them on the control workstation to allow use of the system management software functions.

When You Install PE on the SP Control Workstation

If you install PE on the SP Control Workstation (using one of the methods explained later in this chapter), you will need to do the following in order to use the User Space libraries:

1. Login as root and create the link to the User Space library:

   ln -s /usr/lpp/ssp/css/libtb3/libmpci.a  /etc/ssp/css/libus/libmpci.a
    
   ln -s /usr/lpp/ssp/css/libtb3/libmpci_r.a  /etc/ssp/css/libus/libmpci_r.a
   

   Note:

   Establish this link before installing POE. The installation steps depend on the correct adapter libraries being properly linked. It is normally created by /usr/lpp/ssp/css/rc.switch when called from /etc/inittab running on an SP node. The link does not get created on the SP control workstation since it cannot determine what type of switch adapter should be used. Failure to set up this link may prevent you from using POE.

2. Verify the POE installation by running the installation verification program (IVP).

If You Receive sysck Warning Messages

During the course of installing PE filesets on an SP, you may encounter sysck warning messages. These messages may indicate that a particular file is also owned by another fileset. If the message indicates the file is also owned by one of the PSSP filesets, such as ssp.css, you can ignore these messages. Also, if sysck is run after installing ppe.poe on a node where ssp.css has also been installed, you may see messages about files being the wrong type, which you can also ignore. However, if the warning messages are for older PE related filesets, such as PE Version 2 ppe.poe or ppe.vt, this may indicate an older version is installed.

You can ignore these warning messages and the system will function properly. However, if you later choose to remove the old fileset after installing PE, you will need to repeat the installation of the new fileset.

About Installing PE on an IBM pSeries or RS/6000 Cluster

Installation on an IBM pSeries or RS/6000 network cluster is similar to installation on the SP, with the exception that there are no system management functions. This leaves you with the following two options:

• Use the PEinstall script.
• Install the software on each system individually using SMIT or installp.

In either case, first install the PE filesets on at least one system in your cluster. When this is complete, you can replicate the installation image to your other nodes.

During the course of installing PE filesets on a cluster, you may encounter sysck warning messages. These messages may indicate that a particular file is also owned by another fileset. If the file is also owned by one of the older PE filesets, such as PE Version 2 ppe.poe, this may indicate that an older version is installed.

You can ignore these warning messages and the system will function properly. However, if you later choose to remove the old fileset after installing PE 3.2, you need to reinstall the new fileset.