HP Cluster Test Installation Guide Abstract This guide describes the procedures for installing HP Cluster Test RPM. For information on HP Cluster Test Image and CTlite, see their respective documents.
© Copyright 2011, 2014 Hewlett-Packard Development Company, L.P. 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.
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.....................
1 Cluster Test overview Cluster Test is designed to: • verify the validity of a cluster configuration. • 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.
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.
• 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.
• RHEL 6.2 CT RPM Kit Dependent packages ◦ tk: – ◦ ◦ ◦ OpenIPMI, ipmitool, net-snmp-libs, lm_sensors-libs (needed to start ipmi service): – OpenIPMI-2.0.16-12.el6.x86_64.rpm – OpenIPMI-libs-2.0.16-12.el6.x86_64.rpm – ipmitool-1.8.11-12.el6.x86_64 – net-snmp-libs-5.5-37.el6.x86_64.rpm – lm_sensors-libs-3.1.1-10.el6.x86_64.rpm libxml, libstdc++, zlib (32-Bit [i686]RPMs needed for conrep): – libstdc++-4.4.6-4.el6.i686.rpm – libxml2-2.7.6-4.el6.i686.rpm – zlib-1.2.3-27.el6.i686.
◦ Mesa-libGL-devel required to install nbody after cuda tool kit installation: – ◦ mcelog package to decode kernel machine check log on x86 machines used by CT memory error check: – ◦ • mcelog-1.0pre3_20110718-0.14.el6.x86_64.rpm Install the following two font-related RPM packages from the respective DVD ISO distribution. – urw-fonts-2.4-10.el6.noarch.rpm – ghostscript-fonts-5.50-23.1.el6.noarch.rpm RHEL 6.4 CT RPM Kit Dependent packages ◦ tk: – ◦ ◦ ◦ ◦ ◦ ◦ tk-8.5.7-5.el6.x86_64.
• – nfs-utils-1.2.3-36.el6.x86_64.rpm – nfs-utils-lib-1.1.5-6.el6.x86_64.rpm – make-3.81-20.el6.x86_64.rpm – openssl-devel-1.0.0-27.el6.x86_64rpm – gcc-c++-4.4.7-3.el6.x86_64.rpm – gcc-gfortran-4.4.7-3.el6.x86_64.rpm – gdb-7.2-60.el6.x86_64.rpm – tigervnc-server-1.1.0-5.el6.x86_64.rpm – rpm-build-4.8.0-32.el6.x86_64.rpm – gcc-4.4.7-3.el6.x86_64.rpm – libgcc-4.4.7-3.el6.x86_64.rpm – libgcc-4.4.7-3.el6.i686.rpm – glibc-2.12-1.107.el6.i686.rpm – libXp-1.0.0-15.1.el6.x86_64.
– glib-1.2.10-737.22.x86_64.rpm – glib-devel-1.2.10-737.22.x86_64.rpm – glibc-info-2.9-13.2.x86_64.rpm – libMagickWand1-6.4.3.6-7.18.x86_64.rpm – libboost_date_time1_36_0-1.36.0-11.17.x86_64.rpm – libboost_filesystem1_36_0-1.36.0-11.17.x86_64.rpm – libboost_graph1_36_0-1.36.0-11.17.x86_64.rpm – libboost_iostreams1_36_0-1.36.0-11.17.x86_64.rpm – libboost_math1_36_0-1.36.0-11.17.x86_64.rpm – libboost_mpi1_36_0-1.36.0-11.17.x86_64.rpm – libboost_program_options1_36_0-1.36.0-11.17.
◦ – xorg-x11-libICE-devel-7.4-1.15.x86_64.rpm – xorg-x11-libSM-devel-7.4-1.18.x86_64.rpm – xorg-x11-libX11-devel-7.4-5.5.x86_64.rpm – xorg-x11-libXau-devel-7.4-1.15.x86_64.rpm – xorg-x11-libXdmcp-32bit-7.4-1.15.x86_64.rpm – xorg-x11-libXdmcp-devel-32bit-7.4-1.15.x86_64.rpm – xorg-x11-libXdmcp-devel-7.4-1.15.x86_64.rpm – xorg-x11-libXext-devel-32bit-7.4-1.14.x86_64.rpm – xorg-x11-libXext-devel-7.4-1.14.x86_64.rpm – xorg-x11-libXfixes-devel-7.4-1.14.x86_64.rpm – xorg-x11-libXmu-devel-7.
◦ Mesa-libGL-devel required to install nbody after cuda tool kit installation: – ◦ mcelog package to decode kernel machine check log on x86 machines used by CT memory error check: – • mcelog-1.0.2011.06.08-0.9.12 SLES 11.2 CT RPM Kit Dependent packages ◦ ◦ 12 Mesa-libGL-devel-8.0.4-20.11.1.x86_64.rpm Install first before ofed and mpi installation: – gcc-4.3-62.198.x86_64.rpm – gcc-c++-4.3-62.198.x86_64.rpm – gcc-fortran-4.3-62.198.x86_64.rpm – gcc43-4.3.4_20091019-0.7.35.x86_64.
– libboost_signals1_36_0-1.36.0-11.17.x86_64.rpm – libboost_system1_36_0-1.36.0-11.17.x86_64.rpm – libboost_test1_36_0-1.36.0-11.17.x86_64.rpm – libboost_thread1_36_0-1.36.0-11.17.x86_64.rpm – libboost_wave1_36_0-1.36.0-11.17.x86_64.rpm – libjpeg-devel-6.2.0-879.10.x86_64.rpm – liblcms-devel-1.17-77.14.19.x86_64.rpm – libpciaccess0-devel-7.4-8.24.2.x86_64.rpm – libpixman-1-0-devel-0.16.0-1.2.22.x86_64.rpm – libpng-devel-1.2.31-5.10.x86_64.rpm – libstdc++-devel-4.3-62.198.x86_64.
◦ 14 – xorg-x11-libXpm-devel-32bit-7.4-1.17.x86_64.rpm – xorg-x11-libXpm-devel-7.4-1.17.x86_64.rpm – xorg-x11-libXprintUtil-devel-7.4-1.17.x86_64.rpm – xorg-x11-libXrender-devel-7.4-1.14.x86_64.rpm – xorg-x11-libXt-devel-32bit-7.4-1.17.x86_64.rpm – xorg-x11-libXt-devel-7.4-1.17.x86_64.rpm – xorg-x11-libXv-devel-7.4-1.14.x86_64.rpm – xorg-x11-libfontenc-devel-7.4-1.15.x86_64.rpm – xorg-x11-libxcb-devel-32bit-7.4-1.15.x86_64.rpm – xorg-x11-libxcb-devel-7.4-1.15.x86_64.
◦ Mesa-libGL-devel required to install nbody after cuda tool kit installation: – ◦ Mesa-libGL-devel-8.0.4-20.11.1.x86_64.rpm mcelog package to decode kernel machine check log on x86 machines used by CT memory error check: – mcelog-1.0.2011.06.08-0.9.
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.
TIP: In the event of an installation error, HP recommends you uninstall the Cluster Test executables, correct the reported problem, then repeat the installation. To uninstall the Cluster Test Executable use: For Red Hat, SLES, and CentOS: /opt/clustertest/setup/ct_setup.sh -u • 4. 5. A prerequisite RPM is not installed. Although the installation checks and reports on the most common RPM prerequisites, it is possible that one of more required RPMs is not installed.
node0: ERROR: Could not open input file /opt/clustertest/bin/smartscripts/Get_FW_Version.xml node0: Error processing the XML file: /opt/clustertest/bin/smartscripts/Get_FW_Version.xml To ensure the Linpack test runs successfully, install the hponcfg package and the linux-LOsamplescripts4.11.0.tgz smartscripts on all nodes. 1. Install the hponcfg RPM package on all nodes. # rpm -ivh /home/hponcfg-4.2.0-0.x86_64.rpm 2. Create the directory /opt/clustertest/bin/smartscripts/.
NOTE: The node number range managed by this head node and the node number range of the entire cluster are typically the same. 9. • Node number list of all head nodes – If there is only one head node this entry, its node number, for example “0”. If there are multiple head nodes, this is a comma-delimited list of all head nodes. • Alternate interconnect type – Must be one of the following. Entries are case sensitive. ◦ None ◦ GigE – When the interconnect is GigE.
3 Uninstalling Cluster Test The RPM version of Cluster Test installs bits on the compute nodes, and has an uninstall script to remove those bits. Uninstalling CT RPM Uninstalling Cluster Test RPM is a two step process. The first step involves removing the Cluster Test executables; the second step involves removing the Cluster Test sources. These steps must be executed on each node that has Cluster Test installed. 1. Run the uninstall script to remove the Cluster Test executables.
4 Support and other resources Intended audience It is assumed the reader has the experience in the following areas: • the Linux operating system • HP hardware, including all HP ProLiant models, Integrity servers, and ProCurve switches • configuration of BIOS settings, iLO/IPMI, and ProCurve switches Contacting HP Before you contact HP Be sure to have the following information available before you contact HP: • Technical support registration number (if applicable) • Product serial number (if applica
• Cabling Tables: HP Cluster Platform Cabling Tables • HP SmartStart Scripting Toolkit Software Open source software • Linux Kernels: http://www.kernel.org/ • PDSH Shell: http://www.llnl.gov/linux/pdsh.html • IPMITool: http://ipmitool.sourceforge.net/ • Open MPI: http://www.open-mpi.org/ HP software • HP Cluster Test software download: http://www.hp.com/go/ct-download • HP Message Passing Interface: http://www.hp.
WARNING A warning calls attention to important information that if not understood or followed will result in personal injury or nonrecoverable system problems. CAUTION A caution calls attention to important information that if not understood or followed will result in data loss, data corruption, or damage to hardware or software.
5 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Index accelerator install requirements, 15 website, 22 Perl modules, 5 procedures installing Cluster Test RPM, 16 C R cabling tables documentation, 22 Cluster Test about, 4 documentation, 21 installing, 5 RPM, 5 RPM requirements, 5 uninstalling, 20 websites, 21 compute node what Cluster Test installs, 20 requirements accelerator support, 15 Open MPI, 5 RHEL 6.1 support, 6 RHEL 6.2 support, 7 RHEL 6.3 support, 7 RHEL 6.4 support, 8 RPM version, 5 SLES 11.1 support, 9 SLES 11.2 support, 12 RHEL 6.
