This guide describes how to install, configure, and use HP Insight Cluster Management Utility (CMU) v7.2 on HP systems. HP
Insight CMU is software dedicated to the administration of HPC and large Linux clusters. This guide is intended primarily for
administrators who install and manage a large collection of systems. This document assumes you have access to the documentation
that comes with the hardware platform where the HP Insight CMU cluster will be installed, and you are familiar with installing
and administering Linux operating systems.
HP Part Number: 5900-3115
Published: November 2013
Edition: 1
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.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation. Linux™ is a trademark of Linus Torvalds in the U.S. Red Hat™
and RPM™ are trademarks of Red Hat, Inc.Java® is a registered trademark of Oracle and/or its affiliates.
HP Insight Cluster Management Utility (CMU) is a collection of tools that manage and monitor a
large group of computer nodes, specifically HPC and large Linux Clusters. You can use HP Insight
CMU to lower the total cost of ownership (TCO) of this architecture. HP Insight CMU helps manage,
install, and monitor the compute nodes of your cluster from a single interface. You can access this
utility through a GUI or a CLI.
1.1 Features
HP Insight CMU is scalable and can be used for any size cluster.
The HP Insight CMU GUI:
•Monitors all the nodes of your cluster at a glance.
•Configures HP Insight CMU according to your actual cluster.
•Manages your cluster by sending commands to any number of compute nodes.
•Replicates the disk of a compute node on any number of compute nodes.
The HP Insight CMU CLI:
•Manages your cluster by sending commands to any number of compute nodes.
•Replicates the disk of a compute node on any number of compute nodes.
•Saves and restores your HP Insight CMU database.
1.1.1 Compute node monitoring
You can monitor many nodes using a single window. HP Insight CMU provides the connectivity
status of each node as well as sensors. HP Insight CMU provides a default set of sensors such as
CPU load, memory usage, I/O performance, and network performance. You can customize this
list or create your own sensors. You can display sensor values for any number of nodes.
Information provided by HP Insight CMU is used to ensure optimum performance and for
troubleshooting. You can fix thresholds to trigger alerts. All information is transmitted across the
network at time intervals, using a scalable protocol for real-time monitoring.
1.1.2 HP Insight CMU configuration
HP Insight CMU requires a dedicated management server running RHEL or SLES. CentOS and
Scientific Linux are supported on the management node, but require active approval and verification
form HP. The management node can run a different OS from the compute nodes. However, HP
recommends running the same OS on the compute nodes and on the management node.
IMPORTANT:HP Insight CMU does not qualify management nodes. Any server with a supported
operating system can become an HP Insight CMU management node.
For details on specific operating systems supported, see the HP Insight CMU release notes for your
version of the product.
All cluster nodes must be connected to the management node through an Ethernet network. Each
compute node must have a management card. These management cards must be connected to an
Ethernet network. This network must be accessible by the management node.
HP Insight CMU is configured and customized using the HP Insight CMU GUI. Tasks include:
•Manually adding, removing, or modifying nodes in the HP Insight CMU database
•Invoking the scan node procedure to automatically add several nodes
•Adding, deleting, or customizing HP Insight CMU groups
1.1 Features11
•Managing the system images stored by HP Insight CMU
•Configuring actions performed when a node status changes such as display a warning, execute
a command, or send an email
•Exporting the HP Insight CMU node list in a simple text file for reuse by other applications
•Importing nodes from a simple text file into the HP Insight CMU database
1.1.3 Compute node administration
The HP Insight CMU GUI and CLI enable you to perform actions on any number of selected compute
nodes. Tasks include:
•Halting
•Rebooting
•Booting and powering off, using the compute node management card
•Broadcasting a command to selected compute nodes, using a secure shell connection or a
management card connection
•Direct node connection by clicking a node to open a secure shell connection or a management
card connection
1.1.4 System disk replication
The HP Insight CMU GUI and CLI enable you to replicate a system disk image on any number of
selected compute nodes. Tasks include:
•Creating a new image (While backing up a compute node system disk, you can dynamically
choose which partitions to backup.)
•Replicating available images on any number of compute nodes in the cluster
•Managing as many different images as needed for different software stacks, different operating
systems, or different hardware
•Cloning from one to many nodes at a time with a scalable algorithm which is reliable and
does not stop the entire cloning process if any nodes are broken
•Customizing reconfiguration scripts associated with each image to execute specific tasks on
compute nodes after cloning
12Overview
2 Installing and upgrading HP Insight CMU
2.1 Installing HP Insight CMU
A typical HP Insight CMU cluster contains three kinds of nodes. Figure 1 (page 13) shows a typical
HPC cluster.
•The management node is the central point that connects all the compute nodes and the GUI
clients. Installation, management, and monitoring are performed from the management node.
The package cmu-v7.2-1.x86_64.rpm must be installed on the management node. All
HP Insight CMU files are installed under the /opt/cmu directory.
•The compute nodes are dedicated to user applications. A small software application that
provides a monitoring report is installed on the compute nodes.
IMPORTANT:All compute nodes must be connected to an Ethernet network.
•The client workstations are any PC systems running Linux or Windows operating systems that
display the GUI. The administrator can install, manage, and monitor the entire cluster from a
client workstation. Users can monitor the cluster and access compute nodes from their
workstations.
A management card is required on each node to manage the cluster. These management cards
must be connected to an Ethernet network. The management node must have access to this network.
Figure 1 Typical HPC cluster
2.1.1 Management node hardware requirements
The HP Insight CMU management node needs access to the compute nodes, the compute node
management cards (iLOs), and the HP Insight CMU GUI clients. Each of these components is
typically on a separate network, though that is not strictly required. Using independent networks
ensures good network performance and isolates problems if network failures occur. A recommended
NIC/network configuration for the management node is:
•Connect one NIC to a network established for compute node administration.
•Connect a second NIC to the network connecting the HP Insight CMU management node to
the HP Insight CMU GUI clients.
•A third NIC is typically used to provide access to the network connecting all the compute node
management cards (iLOs).
2.1 Installing HP Insight CMU13
NOTE:The IP address of the NIC connected to the compute node administration network is
needed during configuration of the HP Insight CMU management node.
2.1.2 Disk space requirements
A total of 400 MB of free disk space is necessary to install all the subsets or packages required
for HP Insight CMU. Up to 4 Gb of additional space is needed to store each master disk image.
2.1.3 Support for non-HP servers
IMPORTANT:You must obtain a valid license to run HP Insight CMU on non-HP hardware.
The following section describes how HP Insight CMU functions with non-HP servers.
Provisioning
•autoinstall works (assumes PXE-boot support).
•Diskless works (assumes PXE-boot support).
•Backup and cloning must be tested. These processes rely on the HP Insight CMU netboot kernel
which needs the network and disk drivers for non-HP hardware. If these drivers for non-HP
hardware exist in the kernel.org source tree, then backup and cloning should work. If
backup and cloning does not work on your specific hardware, contact HP services.
Monitoring
•All monitoring works, including the GUI.
•If provisioning is not used, monitoring requires password-less ssh to be configured for the root
account on all nodes.
NOTE:Backup and cloning configures this automatically.
Remote management
•All xterm-based features work. For example:
single|multi xterm◦
◦pdsh with cmudiff
◦pdcp
•Power control and console access depend on non-HP hardware. HP Insight CMU supports
IPMI. Otherwise, a new power interface can be configured. HP Insight CMU has an API for
power control.
•BIOS and firmware management are HP-specific.
•Custom menu support works.
2.1.4 Planning for compute node installation
Two IP addresses are required for each compute node.
•Determine the IP address for the management card (iLO) on the management network.
•Determine the IP address for the NIC on the administration network.
HP recommends assigning contiguous ranges of static addresses for nodes located in the same
rack. This method eases the discovery of the nodes and makes the cluster management more
convenient.
14Installing and upgrading HP Insight CMU
The management cards must be configured with a static IP address. All the compute node
management cards must have a single login and password.
NOTE:HP Insight CMU uses DHCP and PXE. Do not run other DHCP or PXE servers on the HP
Insight CMU management network in the range of ProLiant MAC addresses belonging to the HP
Insight CMU cluster.
NOTE:The settings described in this document are based on the assumption that the administration
network on each compute node is connected to, and will PXE boot from, NIC1. While this
configuration enables all supported hardware to be imaged by HP Insight CMU, some operating
systems might not configure eth0 as NIC1. For example, RHEL5.4 on the ProLiant DL385 G6 Server
defaults eth0 to NIC3. To simplify the installation process for your operating system, HP recommends
wiring your administration network to the NIC that defaults to eth0 and set that NIC to PXE boot
rather than NIC1.
2.1.5 Firmware upgrade requirements
Depending on the type of compute nodes in the cluster, you might have to upgrade the firmware
on each compute node.
IMPORTANT:All compute nodes must have the same firmware version.
2.1.6 Configuring the local smart array card
HP Insight CMU does not configure local disks. If you have a hardware RAID controller, configure
a logical drive to be used later by the operating system. The same logical drive must be created
on each compute node.
The Compaq Array must be configured on each node of the cluster. You can choose any RAID
level. If you have only one physical drive, before performing the initial operating system installation,
configure it in a logical RAID0 drive. Otherwise, the disk is not detected during the Linux installation
procedure and during the cloning procedure.
2.1.7 Configuring the management cards
To configure the management cards such as iLO:
1.Power on the server.
2.Access the management card.
3.Assign the same username and password to all management cards.
4.Assign a fixed IP address to each management card.
NOTE:On Blade servers, to configure the IP addresses on the iLO cards, you can use the
EBIPA on the OA. For instructions, see “Configuring iLO cards from the OA: Blades only”
(page 16).
NOTE:Blade servers do not use the Single Sign-On capability. You must configure each
Blade individually and create the same username and password. For instructions, see “Disabling
server automatic power on: Blades only” (page 16).
2.1.8 Configuring the BIOS
Generally, BIOS parameters that affect HP Insight CMU are:
•Boot order parameters. (Network boot must have the highest priority.)
•Parameters that enable the BIOS boot process and the Linux boot process to be visualized at
the iLO serial console. (Those parameters must be set for BIOS startup and Linux boot to be
monitored from a remote connection through the iLO port.)
2.1 Installing HP Insight CMU15
•Parameters that affect the behavior of the local disk controller. Parameter names can differ
from one server to another and cannot be documented exhaustively.
IMPORTANT:If the boot order is not correctly set, then cloning and backup fail on the cluster.
Examples are provided in the following sections.
2.1.8.1 DL3xx, DL5xx, DL7xx, Blades
Parameters:
•Virtual serial port COM1
•Embedded NIC
NIC 1 PXE boot or PXE enabled◦
◦NIC 2 Disabled
◦NIC 3 Disabled (not always present)
◦NIC 4 Disabled (not always present)
•Boot order
PXE1.
2.CD
3.DISK
•BIOS Serial console
BIOS Serial Console Auto◦
◦Speed 9600 Bd
◦EMS Console COM1
◦Interface Mode Auto
2.1.8.1.1 OA IP address: Blades only
Assign the OA IP address in the same subnet as the administration network.
2.1.8.1.2 Configuring iLO cards from the OA: Blades only
Use the EBIPA to assign consecutive addresses to the iLO:
•16 addresses on the c7000 Enclosure
•8 addresses on the c3000 Enclosure
To configure the iLO cards:
1.Open a browser to the OA.
2.In the right window, select Device Bays.
3.Select Bay 1.
4.In the left window, select the Enclosure Setting tab and then Enclosure Bay IP Addressing.
5.Enter the IP address of the first iLO card.
6.Click Auto Fill or the red arrow.
Each iLO is reset and assigned an IP address by the OA.
7.From the HP Insight CMU management node, ping each iLO.
2.1.8.1.3 Disabling server automatic power on: Blades only
On each Blade server:
16Installing and upgrading HP Insight CMU
1.Access the iLO card.
2.Create the username and password. Each server must have the same username and password.
IMPORTANT:The embedded SATA Raid Controller option is not supported. Do not
select this option.
NOTE:These IDE settings only apply to the DL160 G5 Server.
•IPMI
Serial Port assigned to System◦
◦Serial Port Switching Disabled
◦Serial Port Connection Mode Direct
•LAN
Share NIC mode Disabled◦
◦DHCP Disabled
•Remote Access
Remote access Enabled◦
◦Redirection Always
2.1 Installing HP Insight CMU17
◦Terminal VT100
•Boot Configuration
Boot Order◦
1.Embedded NIC
2.Disk or smart array
◦Embedded NIC1 Enabled
2.1.8.3 DL160 G6 Servers
•IPMI
Serial Port assigned to System◦
◦Serial Port Connection Mode Direct
•PCI
NIC1 control Enabled◦
◦NIC1 PXE Enabled
•SATA
SATA#1 Controller Mode AHCI◦
•Boot Configuration
Boot Order◦
1.NIC
2.CD
3.Disk
2.1.8.4 SL2x170z G6 and DL170h G6 Servers BIOS setting
IMPORTANT:To enable BIOS updates, you must restart the server. You can restart the server
with Ctrl+Alt+Delete immediately after leaving the BIOS, or you can physically restart the server
by using the power switch on the server.
Figure 3 NIC2 on the SL2x170z G6 Server
•BIOS settings
Post speedup Enabled◦
18Installing and upgrading HP Insight CMU
◦Numlock Enabled
◦Restore after AC loss Last state
◦Post F1 prompt Delayed
•CPU setup
Proc hyper threading Disabled◦
•IDE configuration
SATA controller mode AHCI◦
◦Drive cache Enabled
◦IDE timeout 35
•Chipset ACPI configuration
High Performance Event timer Enabled◦
•IPMI serial port configuration
Serial port assignment BMC◦
◦Serial port switching Enabled
◦Serial port connection mode Direct
•LAN configuration
If your node is wired with the LO100i management port shared with NIC2:
◦BMC NIC Allocation Shared
◦LAN protocol: HTTP, telnet, ping Enabled
Otherwise, if your node is wired with a dedicated management port for LO100i:
◦BMC NIC Allocation Dedicated
◦LAN protocol: HTTP, telnet, ping Enabled
•Remote Access
BIOS Serial console Enabled◦
◦EMS console support Enabled
◦Flow control Node
◦Redirection after BIOS POST Enabled
◦Serial port 9600 8,n,1
•Boot device priority
Network ( 0500 )◦
◦Removable device
◦Hard Disk
•Enable PXE for the NIC that is connected to the administration network.
2.1 Installing HP Insight CMU19
2.2 Preparing for installation
2.2.1 HP Insight CMU kit delivery
The HP Insight CMU kit is delivered on CD-ROM and is provided in the appropriate format for
your operating system. These features enable HP Insight CMU files to be installed directly from the
CD-ROM to your disk. The Linux versions of HP Insight CMU are in the Red Hat Package Manager
(RPM) format.
2.2.2 Preinstallation limitations
•HP Insight CMU monitors only the compute nodes and not the infrastructure of the cluster.
•For cloning Linux images:
HP Insight CMU requires that each partition of the golden image node is at least 50%
◦
free. Alternatively, if this condition cannot be satisfied, then the largest partition of the
golden node must be less than or equal to the compute node memory size.
◦HP Insight CMU does not support software RAID or LVM on compute nodes.
◦HP Insight CMU only clones one disk or logical drive per compute node.
•Limitations for backup and cloning Windows images:
The Windows backup and cloning feature is supported only on specific Moonshot
◦
cartridges. No other platforms are supported.
◦HP Insight CMU can backup and clone only one disk per compute node.
◦The Windows golden node must be shutdown gracefully before attempting a backup
operation.
◦The golden image size (the total size of compressed part-archi*.tar.bz2 files) must
be less than 85% of RAM size on the nodes to be cloned. For example, on nodes with
8GB RAM, the maximum image size available for cloning is approximately 7GB. A
simple Windows install image is usually approximately 3GB when compressed.
NOTE:Windows unattended autoinstall does not have this limitation.
◦Windows dynamic disks are not supported. Only Windows basic disks are supported.
◦When multiple (>1) primary and (>1) logical partitions are present in a Windows backup
image, drive letters (e.g. D:, E: ) assigned to the partitions on the cloned nodes are not
consistent with the golden node.
◦The local “Administrator” account password and desktop are reset on cloned nodes. Any
content placed in the “Administrator” desktop directory is lost after cloning.
◦Cloned nodes reboot twice after the first disk-boot for host specific customizations.
◦GPT partition table is not supported.
IMPORTANT:HP Insight CMU does not support RAID arrays created by B110i RAID controllers
(e.g. SL4545 G7). Any attempts to backup or clone such RAID arrays will fail.
NOTE:You can partially overcome some of these limitations by using a reconfiguration script
after cloning. For more information about reconfiguration, see “Reconfiguration” (page 63).
20Installing and upgrading HP Insight CMU
2.2.3 Operating system support
HP Insight CMU software is generally supported on Red Hat Enterprise Linux (RHEL) 5 and 6; and
SUSE Linux Enterprise Server (SLES) 11.
The HP Insight CMU diskless environment is supported on RHEL5, RHEL6, and SLES11.
Ubuntu 12.x and 13.x are supported on the compute nodes only, on HP Ubuntu certified servers.
Debian is supported on the compute nodes only, but requires active approval and verification from
HP. Contact HP for support.
CentOS and Scientific Linux are supported on the compute nodes and the management nodes,
but require active approval and verification from HP. Contact HP for support.
For details on specific operating systems supported, see the HP Insight CMU release notes for your
version of the product.
Windows 7 SP1 is supported only on HP ProLiant m700 Server cartridges.
Windows Server 2012 and Windows Server 2012 R2 are supported only on HP ProLiant m300
Server cartridges.
2.2.3.1 RHEL 6 support
HP Insight CMU v7.2 supports RHEL6 on the management node and compute nodes. HP Insight
CMU continues to support a mix of operating systems. For example, RHEL6 is not required on the
management node if RHEL6 is installed on your compute nodes. However, you must use HP Insight
CMU v7.2 when RHEL6 is installed anywhere in your HP Insight CMU cluster. As with all HP Insight
CMU releases, all backup images from previous HP Insight CMU versions can be used with v7.2.
HP Smart Array warning with RHEL6 and future Linux releases
If your compute nodes have P212, P410, P410i, P411, P711, P712, P812, or all newer controllers
proposed by HP after April 1, 2011, then running RHEL6+ (or SLES 11SP1 with the optional driver)
will make them appear as standard /dev/sd* SCSI devices and not as /dev/cciss/c*d*.
Other controllers such as HP Smart Array P400, P800, and P700m will continue to appear as
/dev/cciss/c*d* with RHEL6+.
Having these particular nodes means that HP Insight CMU users might have to create new logical
groups and declare backup devices as /dev/sd* instead of /dev/cciss/c*d*. For example,
you can clone a RHEL5 image on a P410i-based compute node, then clone it with RHEL6 and HP
Insight CMU will switch from /dev/cciss/c*d* to /dev/sd*.
As a result of support for RHEL6, HP Insight CMU v7.2 now supports:
•The ext4 file system
•UUID support in fstabs (replaced at backup by HP Insight CMU)
•dhcpd.conf alternate path support
•SHA512 password support for RHEL6 management nodes
•hpsa/cciss support
2.2.4 HP Insight CMU CD-ROM directory structure
The directory structure of the HP Insight CMU CD-ROM is organized as described in Table 1.
Table 1 Directory structure
Linux
ContentsSubdirectory
HP Insight CMU kit for X86_64. CMU-<version>.x86_64.rpm (HP Insight
CMU v7.2 for X86_64)
Examples of configuration files required for the HP Insight CMU installationConfigFiles
2.2 Preparing for installation21
Table 1 Directory structure (continued)
ContentsSubdirectory
Useful tools that can be used in conjunction with HP Insight CMUTools
Documentation and release notesDocumentation
Licenses
Contains the following licenses: Apache_LICENSE-2_0.txt, gluegen_LICENSE.txt,
jogl_LICENSE.txt. Also contains system-config-netboot-legalnotice.html
2.2.5 HP Insight CMU installation checklist
The following list summarizes the steps needed to install HP Insight CMU on your HPC cluster:
Preparing the management node:
1.For hardware requirements, see “Management node hardware requirements” (page 13).
2.Perform a full installation of your base OS on your management node.
3.Install required rpm files. For details, see “Installation procedures” (page 22)
4.Install Oracle Java version 1.6u33 or later.
5.Install HP Insight CMU rpm.
6.Install HP Insight CMU license.
7.Configure HP Insight CMU.
8.Start HP Insight CMU.
9.Configure HP Insight CMU to start automatically.
Preparing the compute nodes:
For instructions on how to prepare the compute nodes for installation, see “Planning for compute
node installation” (page 14)
Preparing the GUI client workstation:
1.Install Java Runtime Environment version 1.6u33 or later.
2.Install cmugui.jar (optional).
3.Configure X Window server. (Optional)
2.2.6 Login privileges
To install HP Insight CMU, you must be logged in as root and have administrator privileges on the
installation node. If relevant for the cluster, you must know the password of the management cards
on the compute nodes.
2.2.7 SELinux and HP Insight CMU
HP recommends disabling SELinux on the management node and the compute node creating the
image. To disable SELinux in RHEL versions, set SELINUX=disabled in the /etc/sysconfig/selinux file and restart the node. If you must use SELinux with HP Insight CMU, please contact
support.
2.3 Installation procedures
IMPORTANT:All steps in this section must be performed on the node designated as your HP
Insight CMU management node.
1.Install a base operating system on your HP Insight CMU management node and perform any
configuration steps that are necessary for the node to work within your local environment (e.g.
configure DNS, set up ntp time synchronization, etc). For details on which operating systems
22Installing and upgrading HP Insight CMU
are supported on the HP Insight CMU management node see “Operating system support”
(page 21)
The following rpms must be installed on the HP Insight CMU management node. Any missing
rpms are flagged as dependencies when the HP Insight CMU rpm is installed and must be
installed to continue the installation.
a.expect
b.dhcp
c.tftp client
d.tftp server
e.Oracle Java Runtime Environment, update 33 or newer
f.tcl-8
g.OpenSSL
h.NFS
i.xterm
j.libX11
k.libXau
l.libXdmcp
m.perl-IO-Socket-SSL.
n.perl-Net-SSLeay
o.Samba (Required only if you intend to use HP Insight CMU Windows support.)
If you are using firewalls on the HP Insight CMU management node or GUI client workstation,
configure them to enable the following ports:
•On the HP Insight CMU management node:
External network interface◦
–RMI registry traffic (tcp ports 1099, 49150)
–Webserver port (tcp 80)
–ssh server (tcp 22)
◦Internal (Admin/Compute) network interface
––Allow all incoming and outgoing traffic. Admin NIC should be a trusted
interface or “Internal Zone”.
•On the GUI client workstation:
◦–X Window export (tcp ports 6000 to 6063)
2.Download and install a supported version of Oracle Java. HP Insight CMU depends on Oracle
Java version 1.6 update 33 or later. Only the Java Runtime Environment (JRE) is required. To
download a supported JRE, go to: http://www.oracle.com/technetwork/java/index.html.
3.Install HP Insight CMU.
a.Install the HP Insight CMU rpm key:
# rpm --import /mnt/cmuteam-rpm-key.asc
NOTE:If you do not import the cmuteam-rpm-key a warning message similar to the
following is displayed when you install the HP Insight CMU rmp:
warning: REPOSITORY/cmu-v7.2-1.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID b59742b4: NOKEY
detailed log is /opt/cmu/log/cmu_install-Thu_Nov__7_12:21:59_EST_2013
********************************************************************************
* *
* optional next steps: *
* *
* - install additional cmu payload packages (ex: cmu-windows-moonshot-addon) *
* *
* - restore a cluster configuration with /opt/cmu/tools/restoreConfig *
* - complete the cmu management node setup: /opt/cmu/bin/cmu_mgt_config -c *
* - setup CMU HA (more than one mgt node): /opt/cmu/tools/cmu_ha_postinstall *
* *
* after setup is finished, unset audit mode and start cmu : *
* *
* /etc/init.d/cmu unset_audit *
* *
* /etc/init.d/cmu start *
* *
********************************************************************************
NOTE:HP Insight CMU has dependencies on other rpms (for example, dhcp). If any
missing dependencies are reported, install the required rpms and repeat this step.
c.Install the HP Insight CMU Windows Moonshot add-on rpm:
HP Insight CMU v7.2 supports autoinstall, backup, and cloning of select Windows images
for supported HP Moonshot cartridges. For more details see, “Preinstallation limitations”
(page 20). If you intend to use HP Insight CMU Windows support, install
Preparing... ########################################### [100%]
1:cmu-windows-moonshot-ad########################################### [100%]
post-installation microsoft windows payload...
4.Install your HP Insight CMU license.
HP Insight CMU v7.2 requires a valid node license key for each rack/Blade/SL server registered
in the cluster. A separate chassis license key is required for each HP ProLiant Moonshot chassis
regardless of the number of cartridges inside a single chassis.
IMPORTANT:Customers upgrading from previous versions of HP Insight CMU to v7.2 must
obtain new license keys. Keys for previous versions do not work with HP Insight CMU v7.2.
The procedure to obtain license keys is provided with the Entitlement Certificate. For more
details, contact HP support.
Copy the content of all license key files to /opt/cmu/etc/cmu.lic.
Example v7.2 node license key:
To configure HP Insight CMU, run /opt/cmu/bin/cmu_mgt_config -c.
24Installing and upgrading HP Insight CMU
The following is an example of executing the command on a management node running Red
Hat Linux. In this example, the management node has the HP Insight CMU compute nodes
connected to eth0 and has a second network on eth1 as a connection outside the cluster.
# /opt/cmu/bin/cmu_mgt_config -c
Checking that SELinux is not enforcing... [ OK ]
Checking for required RPMs... [ OK ]
Checking existence of root ssh key... [ OK ]
Checking if firewall is down/disabled... [ OK ]
Checking tftp for required configuration... [ UNCONFIGURED ]
Making required changes to tftp... [ OK ]
Starting/restarting xinetd services...
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
Checking that NFS is running... [ STOPPED ]
Configuring NFS to start on boot and starting NFS...
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS mountd: [ OK ]
Stopping RPC idmapd: [ OK ]
Starting RPC idmapd: [ OK ]
Starting NFS daemon: [ OK ]
Checking number of NFS threads >= 256... [ WARNING ]
The management node is currently running 8 NFS threads.
HP Insight CMU recommends a minimum of 256 NFS threads
on the management node regardless of cluster size.
How many NFS threads would you like me to configure? [256]
Configuring the number of NFS threads to 256 ... [ OK ]
Setting CMU_MIN_NFSD_THREADS in cmuserver.conf to 256 ... [ OK ]
Restarting NFS
Shutting down NFS daemon: [ OK ]
Shutting down NFS mountd: [ OK ]
Shutting down NFS quotas: [ OK ]
Shutting down NFS services: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS mountd: [ OK ]
Stopping RPC idmapd: [ OK ]
Starting RPC idmapd: [ OK ]
Starting NFS daemon: [ OK ]
Checking dhcp for required configuration
Locating dhcp file... [ OK ]
Which eth should CMU use to access the compute node network?
0) eth0 10.117.20.78
1) eth1 16.117.234.140
:0
Checking if dhcpd interface is configured for "eth0"... [ UNCONFIGURED ]
Configuring dhcpd interface for "eth0"... [ OK ]
Setting dhcpd to start on (re)boot...
Checking if CMU is configured to use 10.117.21.37 [ OK ]
Checking for required sshd configuration... [ UNCONFIGURED ]
Making required changes to sshd... [ OK ]
Restarting sshd
Stopping sshd: [ OK ]
Starting sshd: [ OK ]
Checking if CMU supports the default java version... [ OK ]
Checking for valid CMU license... [ OK ]
The following files were modified by cmu_mgt_config
modified file: /etc/xinetd.d/tftp
backup copy: /etc/xinetd.d/cmu_tftp_before_cmu_mgt_config
modified file: /etc/sysconfig/nfs
backup copy: /etc/sysconfig/cmu_nfs_before_cmu_mgt_config
modified file: /opt/cmu/etc/cmuserver.conf
backup copy: /opt/cmu/etc/cmuserver.conf_before_cmu_mgt_config
modified file: /etc/sysconfig/dhcpd
backup copy: /etc/sysconfig/cmu_dhcpd_before_cmu_mgt_config
modified file: /etc/ssh/sshd_config
backup copy: /etc/ssh/cmu_sshd_config_before_cmu_mgt_config
#
2.3 Installation procedures25
This command can be rerun at any time to change your configuration without adversely
affecting previously configured steps. You can also verify your current configuration by running
/opt/cmu/bin/cmu_mgt_config -ti.
For additional options and details on this command, run /opt/cmu/bin/cmu_mgt_config
-h.
6.Start HP Insight CMU.
After the initial rpm installation, HP Insight CMU is configured in audit mode. To run HP Insight
CMU, unset audit mode and start the HP Insight CMU service.
# /etc/init.d/cmu unset_audit
cmu service needs (re)start
# /etc/init.d/cmu start
starting tftp server check ... done
cmu:core(standard) configured
cmu:java running (*:1099)
cmu:cmustatus running
cmu:monitoring not running
cmu:dynamic user groups unconfigured (cf ${CMU_PATH}/etc/cmuserver.conf
CMU_DYNAMIC_UG_INPUT_SCRIPTS)
cmu:web service running (port 80)
cmu:nfs server running
cmu:dhcpd.conf configured ( subnet X.X.X.X netmask Y.Y.Y.Y {})
cmu:high-availability unconfigured
Where X.X.X.X is the subnet IP address, and YYYY is the netmask of the subnet served by the
dhcp server.
The output lists all the daemons started by the service and their status. Verify that the daemons
are in their expected state.
core
Indicates whether the core components of HP Insight CMU are configured.
java
Indicates whether java is running and the interface used by the java to receive commands
from GUI clients and to send status back to them.
cmustatus
Indicates the status of the utility that checks the state of all the compute nodes.
Monitoring
Indicates the status of the monitoring daemon that gathers the information reported by the
small monitoring agent installed on the compute nodes.
NOTE:Because compute nodes are not installed on the cluster at this time, the monitoring
agent is not started after the installation. This behavior is normal. The cluster must be
configured for monitoring to start.
dynamic user groups
Indicates the configuration status of dynamic user groups.
web service
Indicates the status of the web service on the HP Insight CMU management node. By
default, the web service listens on port 80. The HP Insight CMU GUI can be launched
from a web browser that is pointed to the home page provided by the web service.
nfs server
Indicates the status of the NFS server.
dhcpd.conf
Indicates the status of the DHCPD configuration.
26Installing and upgrading HP Insight CMU
high-availability
Indicates whether the HP Insight CMU management node has been configured for high
availability.
7.Configure HP Insight CMU to start automatically.
IMPORTANT:This installation depends on the operating system installed and might have to
be adapted to your specific installation.
NOTE:The /etc/init.d/cmu file is available as a result of the HP Insight CMU installation.
a.Choose one of the following options:
•If your distribution supports chkconfig:
# chkconfig --add cmu
•If your distribution does not support chkconfig, add start and kill links in the rc.d
directory:
b.After system reboot, verify that the /var/log/cmuservice_hostname.log file does
not contain errors.
8.Install HP Insight CMU on the GUI client workstation.
2.4 Installing HP Insight CMU with high availability
If you are not using HP Insight CMU with high availability (HA), skip this section and go to the
instructions on configuring the cluster in “Defining a cluster with HP Insight CMU” (page 44).
A ”classic” HP Insight CMU cluster has a single management server. If that server fails, although
the HP Insight CMU cluster continues to work for customer applications, you lose management
functions such as backup, cloning, booting a compute node, and ssh through the HP Insight CMU
GUI. If the HP Insight CMU cluster uses a private network for management, you also lose connection
to the site network. Installing and configuring HP Insight CMU under the control of HA software
provides redundancy to avoid this HP Insight CMU service degradation. The following figure
describes a “classic” HP Insight CMU cluster connected to two networks: the site network and a
private cluster network where compute nodes are connected. The HP Insight CMU management
server is known by its IP0 address on the site network, and by the IP1 address on the cluster network.
The next figure shows the corresponding configuration where two servers can run HP Insight CMU
software in active or standby mode under control of HA software. Mgt server1 and mgt server 2
are connected to form an HP Insight CMU management cluster. The IP addresses IP0 and IP1 are
2.4 Installing HP Insight CMU with high availability27
attached to the HP Insight CMU management server that is running the HP Insight CMU software
at a given time. The HP Insight CMU management cluster is known on the site network by the
address IP0, and on the compute network by the address IP1. IP0 and IP1 are the only addresses
HP Insight CMU recognizes. If that server fails, then IP0 and IP1 migrate to the other server. The
two servers each have one IP address per network (IP2, IP3, IP4, IP5). The two servers are connected
to shared storage which hosts the HP Insight CMU directory. This configuration is perceived as a
“classic” HP Insight CMU configuration with a single management server by the compute nodes,
and from the user's point of view.
The next figure shows a “classic” HP Insight CMU cluster with one HP Insight CMU management
server and compute nodes connected directly to the site network. A unique IP address IP0 is used
for compute node management and site network access.
The next figure shows the corresponding configuration with two HP Insight CMU management
servers running HP Insight CMU software in active or standby mode under control of HA software.
28Installing and upgrading HP Insight CMU
The address IP0 is attached to the server running the HP Insight CMU software. This is the unique
address HP Insight CMU recognizes. Each HP Insight CMU management server has its own IP
address on the site network, IP2 and IP 3 respectively, unknown to HP Insight CMU.
2.4.1 HA hardware requirements
The hardware requirements for HP Insight CMU under HA control are:
•Two or more management servers.
•One shared storage accessed by both servers.
2.4.2 Software prerequisites
In addition to the prerequisites described in “Preparing for installation” (page 20), you must install
and configure the HA software of your choice.
2.4.3 Installing HP Insight CMU under HA
2.4.3.1 Overview
NOTE:To avoid confusion in this section, review the glossary definitions in “Glossary” (page 219).
When installing HP Insight CMU as an HA cluster service, HP recommends completing a normal
HP Insight CMU installation on one management server, as described in “Preparing for installation”
(page 20) and “Installation procedures” (page 22). During this phase, HP Insight CMU can be
used as a normal standalone installation. Compute nodes can be installed, backed up, and cloned.
In the second phase of installation, you must install and configure the HA software of your choice.
This software controls the HP Insight CMU HA service.
After testing the configuration, enable the HP Insight CMU HA service by running the /opt/cmu/
tools/cmu_ha_postinstall script. This operation moves some /opt/cmu directories to a
unique shared file system. This shared file system must be configured as a resource of the HP Insight
CMU HA service.
After this procedure is completed on the first HP Insight CMU management server, a second server
can be installed with HP Insight CMU and added to the management cluster. This procedure is
repeated for additional servers connected to the shared storage.
2.4 Installing HP Insight CMU with high availability29
2.4.3.2 HP Insight CMU HA service requirements
When you configure the HA software layer, configure the HP Insight CMU HA service with the
following resources:
•A shared file system. The mount point of this file system must be /opt/cmu-store and must
be created on all HP Insight CMU management servers.
•A shared IP address.
•If your HP Insight CMU cluster uses separate site and compute networks, an additional IP
address resource must be configured and assigned to your HP Insight CMU HA service.
•The HP Insight CMU HA service must be able to invoke the /etc/init.d/cmu script with
start and stop parameters:
# /etc/init.d/cmu start
# /etc/init.d/cmu stop
2.4.3.3 Installing and testing
1.Install the HP Insight CMU rpm as described in “Installation procedures” (page 22). Be sure
all prerequisites are fulfilled.
2.To test HP Insight CMU on the first cluster member, run the HP Insight CMU software. Verify
that the HP Insight CMU software performs correctly.
2.4.4 Configuring HA control of HP Insight CMU
IMPORTANT:During the following procedure, results of the /etc/init.d/cmu script are saved
to /var/log/cmuservice_hostname.log where hostname is the host name of the HP Insight
CMU management cluster member. Refer to these log files for troubleshooting.
1.If HP Insight CMU is running, set audit mode before you stop HP Insight CMU:
cmuadmin1# /etc/init.d/cmu set_audit
cmuadmin1# /etc/init.d/cmu stop
2.In /opt/cmu/etc/cmuserver.conf, the CMU_CLUSTER_IP variable defines the IP address
used by compute nodes to reach the management cluster. This variable must be set with the
same IP address defined as the shared IP address resource for the compute network on the
HP Insight CMU HA service:
CMU_CLUSTER_IP=X.X.X.X
Where X.X.X.X is the address known by compute nodes to reach the management node.
3.Start the HP Insight CMU cluster HA service. Use the appropriate command for your HA
software to start the service on the first management cluster member. As a result of starting
the service, the following resources must be available:
•The shared file system mounted on /opt/cmu-store
•The cluster IP address
4.Run cmu_ha_postinstall:
cmuadlmin1# /opt/cmu/tools/cmu_ha_postinstall
*** starting setup procedure to operate CMU in HA (Highly Available) environment
*** note: this only affects the management nodes of the HPC cluster
**********************************************************************
requirements to building an Highly Available cluster of cmu mgt nodes:
**********************************************************************
* *
* 1] a shared filesystem mounted at /opt/cmu-store *
* *
* it must support locking via flock() *
* it must be mounted only by one (active) cmu mgt node at a time *
30Installing and upgrading HP Insight CMU
Loading...
+ 193 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.