HP XC System Software Installation Guide Version 4.0

3.1.2.1 Head Node Naming
The head node naming scheme differs if HP server blades and enclosures are present in the
hardware configuration.
• When the hardware configuration does not contain (real) enclosures and HP server blades,
the cluster_prep command determines and assigns the head node name by using the
number that represents the maximum number of nodes allowed in the hardware
configuration, which you supply. For example, if the maximum number of nodes allowed
in your hardware configuration is 128, the head node is node {node_prefix}128.
• When the hardware configuration contains HP server blades, the head node is named for
its location in the enclosure just like every other node, as described in Section 3.1.2 (page 51).
The only exception is when the head node is a non-blade server node whose console port
is not connected to the administration network ProCurve switch. In this case, the head node
is named {node_prefix}0.
3.1.3 System Imaging Process
The SystemImager, an open source software component of the HP XC software stack, provides
a simplified method for automating the installation of large Linux clusters. SystemImager provides
the foundation for the image replication and distribution environment used to install client nodes
in an HP XC system.
As part of the initial software installation, the head node is configured as the golden client, which
is the node that represents the configuration from which all other nodes are replicated. Next, a
golden image is created from the golden client, which is a replication of the local file system
directories and files, starting from root (/). The golden image is stored on the image server, which
is also resident on the head node in this release.
When nodes are instructed to PXE or network boot from the network adapter attached to the
administration network, an installation process starts on the client nodes that does the following:
• Partitions the local disk
By default, the first disk is partitioned because in this release, disks other than the first disk
are not supported because of restrictions in the image replication environment.
• Creates file systems
• Downloads the golden image
• Installs the appropriate boot loader
When the automatic installation process completes, each node is rebooted and continues its
configuration process, eventually ending with the login prompt.
3.1.4 System Configuration and Imaging Log Files
A record of the configuration process is stored in the /var/log/nconfig.log file.
Logging of the system imaging process is stored in the following files:
• /hptc_cluster/adm/logs/imaging.log
• /var/log/systemimager/rsyncd
• /hptc_cluster/adm/logs/startsys.log
The /hptc_cluster/adm/logs/imaging.log file contains log information produced during
the imaging and node configuration processes.
Use the information in this file to diagnose imaging issues such as nodes not booting correctly
or failing during the imaging operation. The node configuration portion of the log file provides
useful information during the first boot after a node has been imaged. If a node configuration
fails, the node is put into single-user mode with network access. The node is not allowed to join
the HP XC system without user intervention. The node or nodes that are put into single-user
mode are listed in the imaging.log file.
3.1 System Configuration and Imaging Overview 53