HP Insight Cluster Management Utility v7.2 User Guide

/opt/cmu/hardware/FOO/cmu_FOO_power_osoff
/opt/cmu/hardware/FOO/cmu_FOO_power_uid_off
/opt/cmu/hardware/FOO/cmu_FOO_power_uid_on
All of these programs are invoked with the following arguments:
<PROGRAM> -n <NODENAME> -i <BMC_IP> -e <ERRFILE>
Where:
<NODENAME>
The host name of the target server.
<BMC_IP>
The IP address of the management card for the target server.
<ERRFILE>
The name of the file to log any errors.
After a new HP Insight CMU hardware API is developed and tested, it must be added to HP Insight
CMU as a valid hardware type. To do this, add the name of the new hardware API to the
CMU_VALID_HARDWARE_TYPES variable in /opt/cmu/etc/cmuserver.conf. The setting of
this variable is:
CMU_VALID_HARDWARE_TYPES=ILO:lo100i:ILOCM
To add the IPMI hardware API, add IPMI to the list of valid hardware types:
CMU_VALID_HARDWARE_TYPES=ILO:lo100i:ILOCM:IPMI
After this is done, then you can configure servers in the HP Insight CMU database with this new
"management card type".
8.4 Customizing kernel arguments for the HP Insight CMU provisioning
kernel
When backing up or cloning nodes, HP Insight CMU PXE-boots each node into an NFS-based
diskless operating system provided by HP Insight CMU. HP Insight CMU invokes processes within
this diskless operating system to perform the backup or cloning operation on the underlying disk.
The PXE-boot process includes a standard bootloader (pxelinux.0) and a boot configuration file.
HP Insight CMU provides a stock boot configuration file named default which is located in
/opt/cmu/etc/bootopts/ on the HP Insight CMU management node. This boot configuration
file contains the minimum Debian kernel boot arguments required to boot this kernel in standard
HP Insight CMU cluster configurations.
The HP Insight CMU boot configuration file requires occasional modifications to adapt to specific
cluster configurations or specific hardware needs. If a cluster-wide change to /opt/cmu/etc/
bootopts/default is required, this file can be edited directly.
If the boot configuration file needs to be modified for a subset of the nodes in the cluster, then the
default file can be copied to another file in the same directory and changes can be applied to
the new file. The name of the new file determines the scope of the nodes to which the file applies.
HP Insight CMU uses the following process to select a boot file for each node:
• If /opt/cmu/etc/bootopts/<nodename> exists, HP Insight CMU uses this file when
netbooting <nodename>. Else;
• If /opt/cmu/etc/bootopts/<hex-IP-address> exists, HP Insight CMU uses this file
when netbooting nodes that are configured with an IP address that falls within the range of
<hex-ip-address>. The hex-IP-address can range from the full 8-character address
representing a specific IP address, to a single character representing a broad subnet of IP
addresses. Else;
• The /opt/cmu/etc/bootopts/default file is used. This is the default behavior.
For example, to create a node-specific PXE-boot file:
146 Advanced topics