HP Insight Cluster Management Utility - Manual (Page 147)

An HP Insight CMU compute node (login1) is connected to the lab network (eth0) and the private
cluster network (eth1). Depending on the hardware configuration and wiring for that node, the
kernel might send the DHCP IP request over the lab network (eth0), causing the kernel to hang. To
avoid this, the system administrator can:
1.
Copy /opt/cmu/etc/bootopts/default to /opt/cmu/etc/bootopts/login1.
2. Edit the new login1 file by changing the existing ip=::::::bootp to
ip=:::::eth1:bootp
.
This new kernel boot argument instructs the kernel to send the DHCP IP request over the private
cluster network (eth1).
NOTE: This change might not be applicable to all of the nodes in the cluster because compute
nodes that do not have a lab network connection might have private cluster networks configured
on eth0.
If three nodes (login[1-3]) require this boot file modification, copy /opt/cmu/etc/bootopts/
login1
to /opt/cmu/etc/bootopts/login2 and /opt/cmu/etc/bootopts/login3.
If a subnet of compute nodes require this boot file modification, for example nodes with IP addresses
172.20.0.[1-15], then copy or rename /opt/cmu/etc/bootopts/login1 to /opt/cmu/
etc/bootopts/AC14000
. The hexadecimal IP address AC14000 covers IP addresses 172.20.0.1
- 172.20.0.15.
8.4.1 PXE-boot configuration file keywords
As of HP Insight CMU v7.2, the following keywords are added to the PXE-boot configuration files
in /opt/cmu/etc/bootopts/:
Related HP Insight CMU database field Default keyword text Keyword
Node architecture setting x86_64 CMU_ARCH
Node platform setting generic CMU_PLATFORM
Node console and speed settings console=ttyS0 conole=tty1 CMU_CONSOLE
Node vendor args setting <none> CMU_VENDOR_ARGS
Note that the CMU_CONSOLE keyword attempts to replace console=ttyS0 console=tty1 in
the PXE-boot configuration files when the HP Insight CMU v7.2 rpm is installed. If this attempt fails,
a warning is displayed. The other keywords are additions to the file.
These keywords are needed to support the new HP Moonshot servers. They are replaced by the
corresponding setting in the HP Insight CMU database when the nodes are PXE-booted. If the
database setting is default, then they are replaced by the 'Default Keyword Text' above.
These keywords and the corresponding fields in the HP Insight CMU database provide HP Insight
CMU with a way to override these 'Default Keyword Text' settings when new servers that require
different PXE-boot settings are detected. HP Insight CMU detects the new server types automatically
during the Node Scanning process, or when the nodes are added to HP Insight CMU manually.
During the manual process, the given architecture and platform settings determine the recommended
HP Insight CMU database field settings.
The console and console speed fields in the HP Insight CMU database also provide a method
for users to store customized node-specific console settings in the HP Insight CMU database. For
example, if the Virtual Serial Port of "nodeX" is connected to 'COM2', then you can configure
ttyS1
in the console field for "nodeX". When "nodeX" is PXE-booted, the CMU_CONSOLE
keyword is replaced with console=ttyS1. If the console speed field is set to "9600n8",
then the CMU_CONSOLE keyword is replaced with console=ttyS1,9600n8.
8.4 Customizing kernel arguments for the HP Insight CMU provisioning kernel 147