Installation Guide

3. Execute HP_Cluster_Test_Software_Vx.x_Clusterx64_rpm_vx.x_XXXX.bin. You
will be presented with the HP End User License Agreement. Use the space bar to scroll through
the agreement. At the end, the following prompt is displayed:
To accept the license please type accept:
After typing accept, the Clusterx64_rpm-vx.x-XXXX.noarch.rpm file is extracted
into the current directory.
Procedure for installing CT RPM
The Cluster Test RPM installation is a two step process. The first step is to install the RPM package
on each node in the cluster; the second step is to run a script to either install the prebuilt Cluster
Test executables or build the executables from the Cluster Test sources.
Repeat the following steps on each node in the cluster.
1. Install the Cluster Test sources on the node.
# rpm -ivh Clusterx64_rpm-vx.x-XXXX.noarch.rpm
Preparing... #################################### [100%]
1:clustertest #################################### [100%]
Run '/opt/clustertest/setup/ct_setup.sh -i' to complete the install
2. Cluster Test RPM kits for external download and use are available for RHEL 6.4, RHEL 6.3,
RHEL 6.2, RHEL 6.1, SLES 11.2, and SLES 11.1. You do not need to rebuild the RPMs if you
downloaded the correct Cluster Test RPM kit for your OS and compatible MPI. The prebuilt
binaries can be installed directly. Skip to Step 3.
• To rebuild the RPMs for RedHat, SLES, or CentOS:
# /opt/clustertest/setup/ct_setup.sh -r
NOTE: The normal rebuild command will not rebuild the ct_altas RPM. The atlas rebuild
can take several hours and the included binaries have been shown to work across operating
systems. Should you need to rebuild ct_atlas, you can do so by using the -ra option to
ct_setup in place of the -r option shown above.
TIP: The rebuild process takes some time to complete. If you have multiple nodes of the same
configuration, you can run the rebuild command on one node and then copy the built packages
located in /opt/clustertest/setup/build/RPMS/x86_64/ to /opt/clustertest/
setup/ on the other nodes, then run /opt/clustertest/setup/ct_setup.sh –i on
those nodes.
3. Install the Cluster Test executables and scripts on the node.
# /opt/clustertest/setup/ct_setup.sh -i
Monitor the installation and note any errors that are reported. Errors indicate an installation
problem. Two types of errors may be seen.
• An RPM is already installed. It is possible that an RPM being installed as part of the Cluster
Test executable kit is already present.
For Red Hat or CentOS: Move the offending RPM from /opt/clustertest/setup to
another directory. For example:
# mv /opt/clustertest/setup/perl-DateTime-0.47-1* /home/not-needed
For SLES: The list of Cluster Test Executable RPMs is contained in the text file /opt/
clustertest/setup/rpmlist.sles. Make a backup copy of the file, then edit it
removing the offending RPM.
16 Requirements and installation of CT RPM