This section provides the step-by-step procedure for installing the PE software on an SP, or on a pSeries or RS/6000 network cluster. Each step includes one or more tables that guide you through choices about variables as:
Pay close attention to these tables as you proceed through the procedure, because they may direct you to skip certain steps.
Notes:
This step consists of copying the installation images off the distribution
medium and exporting the installation directory, thereby making the
installation images available for mounting.
| If you are installing on the SP: | If you are installing on an IBM pSeries or RS/6000 network cluster: |
|---|---|
| You must always complete this step. | You must complete this step if any of the machines in your cluster do not have the proper installation device to read the distribution medium. |
To copy the PE software off the distribution medium, follow these instructions:
This command invokes SMIT, and takes you to the window for copying software to a hard disk for future installation over the network.
A window opens listing the available INPUT devices and directories for software.
The window listing the available INPUT devices closes and the original SMIT window indicates your selection.
The SMIT window displays the default parameters used for copying software to a hard disk.
| If you are installing on the SP: | If you are installing on an IBM pSeries or RS/6000 network cluster: |
|---|---|
| /spdata/sys1/install/pssplpp | /usr/sys/inst.images |
The system copies the PE software installation images to the directory.
The SMIT window closes.
To export the directory so the machines in your cluster can install the PE
installation images it contains, enter the appropriate command, as shown in
the following table:
| If you are installing on the SP: | If you are installing on an IBM pSeries or RS/6000 network cluster: |
|---|---|
| /usr/sbin/mknfsexp -d /spdata/sys1/install/pssplpp | /usr/sbin/mknfsexp -d /usr/sys/inst.images |
This step consists of initially installing the PE installation image, using either of the following methods:
Either method allows you to specify whether you want to install all of the PE software filesets or just certain individual filesets.
| If you are installing on the SP: | If you are installing on an IBM pSeries or RS/6000 network cluster: |
|---|---|
| Perform this step on the initial SP node or on the control workstation. You must login as root. | Perform this step on any machine in the cluster. You must login as root. |
To initially install the installation image, enter the appropriate command
as shown in the following table:
| To install: | ENTER |
|---|---|
| all software filesets | installp -a -d devicename ppe* |
| just the html fileset | installp -a -I -X -d devicename ppe.html |
| just the man fileset | installp -a -I -X -d devicename ppe.man |
| just the pdf fileset | installp -a -I -X -d devicename ppe.pdf |
| just the POE fileset | installp -a -I -X -d devicename ppe.poe |
| just the Xprofiler fileset | installp -a -I -X -d devicename ppe.xprofiler |
| just the Performance Collection Tool fileset and the required Dynamic Probe Class Library (DPCL) | installp -a -I -X -d devicename
ppe.perf
and installp -a -I -X -d devicename ppe.dpcl |
| just the Profile Visualization Tool fileset | installp -a -I -X -d devicename ppe.pvt |
| |
The system reads and receives the installation image off the distribution medium.
To initially install the installation image using SMIT, follow these instructions:
This command invokes SMIT, and takes you directly to its window for installing software.
A window opens listing the available INPUT devices and directories for software.
The window listing the available INPUT devices and directories closes and the original SMIT window indicates your selection.
The SMIT window displays the default install parameters.
| If you want to install: | Type this in the "SOFTWARE to install" field: |
|---|---|
| all the PE software | ppe* |
| just the html fileset | ppe.html |
| just the man fileset | ppe.man |
| just the pdf fileset | ppe.pdf |
| just the POE fileset | ppe.poe |
| just the Xprofiler fileset | ppe.xprofiler |
| Just the Performance Collection Tool fileset and the required Dynamic Probe Class Library (DPCL) | ppe.perf and ppe.dpcl |
| Just the Profile Visualization Tool fileset | ppe.pvt |
The system installs the installation image.
If the installation is unsuccessful, a software product cleanup procedure is automatically called. The cleanup procedure removes any files that may have been restored from the distribution medium, and backs out of any post-installation procedure that may have been started.
To help ascertain the cause of the unsuccessful installation, refer to the installation status file. This file indicates how far installation had progressed when the errors occurred. IBM AIX 5L Version 5.1 General Programming Concepts: Writing and Debugging Programs describes the status file in more detail. If you cannot ascertain the cause of a failed installation, contact your local IBM representative.
You have completed the initial installation of PE. For a description of the directories, files, and daemon processes created and the links established when the installation image was received, see Chapter 6, Understanding How Installation of PE Alters Your System.
To determine which remaining steps you need to perform, refer to the
following table:
| If there are other nodes in your system on which you need to install PE filesets: | If there are not any other nodes in your system on which you need to install PE filesets: |
|---|---|
| Proceed to | Skip: If appropriate, proceed to: |
This step consists of installing PE on other nodes, using either of the following methods:
On an SP, an alternative installation method is to use the SP system
management software, as described in the chapter on "Performing Software
Maintenance" in IBM Parallel System Support Programs
for AIX: Installation and Migration Guide. However, a
disadvantage of that method is that it causes each node to reboot after
installation. If you do not want each node to reboot after
installation, use one of the two installation methods explained in this
step.
| If you are installing on the SP: | If you are installing on an IBM pSeries or RS/6000 network cluster: |
|---|---|
| Perform this step from the initial SP node or from the control
workstation as root.
Make sure you have the proper access to run the dsh command on your nodes. | Perform this step from a node with PE installed as root. |
This method consists of:
To create a host list file, follow these instructions:
hostname1 hostname2 hostname3 hostname4 hostname5
To run the installation script, enter the command that is appropriate for
your system, as listed in the following table. (For a detailed
explanation of the syntax of each of these commands, see Appendix A, Syntax of Commands for Running Installation and Deinstallation Scripts.)
| If you are installing on the SP: | If you are installing on an IBM pSeries or RS/6000 network cluster: |
|---|---|
| PEinstallSP image_name [host_list_file] [-f fanout_value] [-copy | -mount] | PEinstall image_name [host_list_file] [-copy | -mount] |
|
Notes:
| |
| If you specify the -copy option, you will be prompted for: | If you specify the -mount option, you will be prompted for: |
|---|---|
|
|
When you are prompted for the name of the fileset you want to install,
enter the appropriate file name as shown in the following table:
| If you want to install: | Type this when prompted: |
|---|---|
| all the PE software | all |
| just the html fileset | ppe.html |
| just the man fileset | ppe.man |
| just the pdf fileset | ppe.pdf |
| just the POE fileset | ppe.poe |
| just the Xprofiler fileset | ppe.xprofiler |
| just the Performance Collection Tool fileset and the required Dynamic Probe Class Library (DPCL) | ppe.perf and ppe.dpcl |
| just the Profile Visualization Tool fileset | ppe.pvt |
For each node in the host list, PEinstallSP or PEinstall executes the following installp command:
installp -aFX -d/image_directory/image_name fileset
This command installs both the usr and root portion of the fileset in the image specified.
The following severe installation errors will cause the installation process to terminate completely:
For other errors, a message may appear describing the error, and then processing will continue. The same message will be logged in a file named PEnode.log in the current working directory. If you see error messages, look in this file, as the node on which the error occurred is always displayed and logged. This helps you identify any nodes on which the fileset(s) did not get successfully installed. When you correct the errors, you can then rerun the PEinstallSP or PEinstall script just for those nodes.
As a system administrator, you may want to have more control over the installation of PE, and install it manually to other nodes, using SMIT or installp.
During Step 1: Copying the Software to a Hard Disk for Installation Over a Network, you created an installation image that you can use to replicate the installation of PE filesets on the other nodes of your system. By making this image available to the other nodes, either by copying or mounting the image file, you can use SMIT or installp to install the image.
The installation image of PE filesets does not require any special consideration. You may use SMIT or installp as described in "Method 1: Using the installp Command". You can also set up a host list file, and run installp via dsh (for SP systems only), or rsh, and install the PE filesets on multiple nodes.
You have completed installing PE on the other nodes in your system.
To determine which remaining steps you need to perform, refer to the
following table:
| If you installed POE: | If you did not install POE: |
|---|---|
| Proceed to: | Skip: |
This step consists of testing the installation of POE, using the POE installation verification program (IVP). You can find this program in /usr/lpp/ppe.poe/samples/ivp.
To run the POE IVP, at the control workstation (or other home node):
This runs an installation verification test that checks if the message-passing program successfully executed using two tasks on this node. The output should resemble the following:
Verifying the location of the libraries
Verifying the existence of the Binaries
Partition Manager daemon /etc/pmdv3 is executable
POE files seem to be in order
Compiling the ivp sample program
Output files will be stored in directory /tmp/ivp15480
Creating host.list file for this node
Setting the required environment variables
Executing the parallel program with 2 tasks
POE IVP: running as task 0 on node pe03
POE IVP: running as task 1 on node pe03
POE IVP: there are 2 tasks running
POE IVP: task 1 received <POE IVP Message Passing Text>
POE IVP: all messages sent
Parallel program ivp.out return code was 0
Executing the parallel program with 2 tasks, threaded library
POE IVP_r: running as task 1 on node pe03
POE IVP_r: running as task 0 on node pe03
POE IVP_r: there are 2 tasks running
POE IVP_r: task 1 received <POE IVP Message Passing Text -
Threaded Library>
POE IVP_r: all messages sent
Parallel program ivp_r.out return code was 0
If both tests return a return code of 0, POE IVP
is successful. To test SP system message passing,
run the tests in /usr/lpp/ppe.poe/samples/poetest.bw
and /usr/lpp/ppe.poe/samples/poetest.cast
To test threaded message passing,
run the tests in /usr/lpp/ppe.poe/samples/threads
End of IVP test
If errors are encountered, your output contains messages that describe these errors. You can correct the errors and run the ivp.script again, if desired.
POE also has sample applications for doing the following:
See Appendix C, Using Additional POE Sample Applications for more information.
Once you have installed the PE filesets, refer to the README file provided with each fileset for any additional installation or usage information. You can find the README file in /usr/lpp/fileset/READMES as fileset.README.
For information about other procedures related to PE installation, see Chapter 5, Performing Installation-Related Procedures.