This guide describes the procedures for installing HP Cluster Test RPM. For information on HP Cluster Test Image and CTlite,
see their respective documents.
HP Part Number: 5900-3747
Published: January 2014
Edition: 5
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor’s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products
and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Microsoft®, and Windows® are U.S. registered trademarks of Microsoft Corporation.
Revision history
Publication dateEdition numberManufacturing part number
January 201455900-3747
November 201345900-3311
September 201235900–2458
October 201125900–1968
May 201115070–6697
Contents
1 Cluster Test overview...................................................................................4
2 Requirements and installation of CT RPM.......................................................5
Requirements for Cluster Test RPM...............................................................................................5
Additional requirements for accelerator support..........................................................................15
Getting the CT RPM kit............................................................................................................15
Procedure for installing CT RPM................................................................................................16
•test the functionality of the cluster as a whole, with emphasis on testing interconnect, including
the interconnect switch, cabling, and interface cards.
•provide stress testing on the cluster nodes.
Cluster Test detects failures of hardware and network connections to the node level early, so the
failed components can be replaced or corrected before cluster software (HP Insight Cluster
Management Utility (CMU), XC, Scali, Scyld, etc.) installation is started. This makes cluster software
integration much easier and faster, particularly on a complex solution with several hundred nodes.
Cluster Test is available in the following versions:
•Image
•RPM
•CTlite
NOTE:This installation guide applies only to the Cluster Test RPM version. For information on
the Cluster Test Image and CTlite versions, see their respective documents.
The Cluster Test Image and RPM versions have a common GUI and suite of tests.
CT Image allows you to test and diagnose the hardware on a cluster that does not have an operating
system installed. CT Image contains the Red Hat Enterprise Linux (RHEL) operating system, libraries,
software packages, scripts, and GUIs that allow you to set up an HPC cluster in a very little time
and run tests immediately afterward. The cluster’s compute nodes are set up in a diskless cluster
environment, which allows the tests to be performed on the compute nodes with pre-installed OS
and software. CT Image has two distribution media options:
•DVD ISO image
•USB key
Cluster Test Image can also be set up to do a network installation instead of using physical media.
All versions of Cluster Test Image install nothing on compute nodes; compute nodes are not altered
any way. Cluster Test Image does require installation on the head node’s hard drive.
Cluster Test RPM provides the ability to diagnose and test the hardware and software on a cluster
that is already installed and running. CT RPM contains the software tools, scripts, and GUIs that
allow you to set up an HPC cluster in very little time and run tests immediately afterward. Cluster
Test RPM requires certain software packages on the cluster, such as the operating system, drivers,
etc., but allows the flexibility of testing combinations of these specific components.
Supported servers and component hardware are listed in the HP Cluster Test Release Notes
document, available at http://www.hp.com/go/ct-docs.
4Cluster Test overview
2 Requirements and installation of CT RPM
Cluster Test RPM is installed on an existing cluster as an additional software package. The current
cluster settings are not modified.
Requirements for Cluster Test RPM
•Currently, Cluster Test RPM supports only X86–64 systems.
•Cluster Test RPM does not include an operating system, drivers, or message passing interface
(MPI). These software packages must be installed and configured on each node of the cluster
prior to installing the Cluster Test RPM. If the cluster uses an interconnect, the interconnect
interface must be enabled and present.
•Currently, Cluster Test RPM only supports Platform MPI and Open MPI. Each node being tested
must have the appropriate MPI version installed and configured.
•For Open MPI:
The PATH environment variable must include an entry pointing to the mpirun and mpicc
◦
commands.
◦The LD_LIBRARY_PATH must contain the path to the Open MPI libraries as its first entry.
The mpi-selector command can be used to set the environment appropriately.
•The ssh network protocol must be available and configured to allow ssh between all nodes
without being challenged for a password.
•A common node-naming convention is required for cluster communication. The node-naming
scheme should encompass a common base name followed by a unique number. If the cluster
has an interconnect, its network alias should follow the same naming convention, with a
common prefix added to the base name. As an example, a common base name of “node”
could be used for the administrative network of the cluster and adding a prefix of ”i” would
identify the interconnect network as “inode”.
•Cluster Test RPM requires the installation of some Perl modules to run the user interface. These
Perl modules are included with RPM, but the individual modules have the following specific
package requirements (additional packages might be required when building Cluster Test
executables). These packages should be installed prior to installing the Cluster Test RPM and
are generally available from the Linux installation media.
◦fontconfig-devel
◦gd
◦libpng-devel
◦libXp
◦openmotif22
◦perftest
◦tcl-devel (required for rebuild only)
◦tk-devel (required for rebuild only)
◦gd-devel (required for rebuild only)
◦libaio-devel (required for rebuild only)
◦libjpeg-devel (required for rebuild only)
Requirements for Cluster Test RPM5
•You should have access to the appropriate RPM package. Information on how to download
RPMs is available in the section “Getting the CT RPM kit” (page 15).
•Prerequisite OS RPMs:
xinetd◦
◦openmpi (test binaries are built against openmpi-1.6.4)
◦hphealth (Optional. Required to run Health Check.)
◦hponcfg (Optional. Required to run Hardware and Firmware Summaries.)
•You should install the following RPMs from your OFED distribution if they are not already
installed:
◦infiniband-diags
◦libibmad1
•RHEL 6.1 CT RPM Kit Dependent packages
tk:
◦
–tk-8.5.7-5.el6.x86_64.rpm
◦OpenIPMI, ipmitool, net-snmp-libs, lm_sensors-libs (needed to start ipmi service):