HP XC System Software Installation Guide Version 4.0
Two system services that are based on syslog-ng log the UDP based information sent by each
client during installation and the node configuration phase (which is called the nconfigure phase).
The hptc-ire-serverlog service runs persistently on the imaging server. It is responsible
for accepting UDP messages from the imaging client and from the hptc-ire-clientlog
service running when a node is running through its nconfigure phase. The hptc-ire-clientlog
service is managed by autoinstall and the nconfig process. It is only started during these processes
and turned off after the processes have been completed.
The rsync log daemon is responsible for logging start and completion time stamps for imaging
and golden image updates in the /var/log/systemimager/rsyncd file. The information is
sent through TCP for reliability. This is a required service because imaging completion timestamps
are used to generate the per node entries in the /tftpboot/pxelinux.cfg file that denote a
system has imaged successfully.
3.2 Preparing to Answer cluster_prep Questions
Table 3-1 describes the information required by the cluster_prep command.
Table 3-1 Information Required by the cluster_prep Command
Description and User ActionItem
During the system discovery process, each node is automatically assigned an internal
name. This name is based on a prefix defined by you. The default node prefix is the
letter n. All node names consist of the prefix and a number based on the node's
topographical location in the system. You have the option to change this default,
perhaps to differentiate the nodes from another system or to customize node names
according to your corporate policies.
Choose a node prefix that adheres to these guidelines:
• The node name consists of a maximum of six alphanumeric characters:
— The lowercase letters a through z
— The uppercase letters A through Z
— The numbers 0 (zero) through 9
• The first and last characters in the prefix must be alphabetic.
• Hyphens (-) and periods (.) are not permitted.
By default, nh is assigned as the head node alias, regardless of the node prefix.
Node name prefix
Enter the exact number of nodes in the hardware configuration or enter the maximum
number of nodes allowed by the interconnect.
For example, if the interconnect allows a maximum of 128 nodes, but the hardware
configuration contains only 64 nodes, it is acceptable to enter the number 128 when
prompted. This number affects only the internal node naming of the head node.
If you run the cluster_prep command with the --enclosurebased option, you
are not prompted to supply the maximum number of nodes.
Maximum number of nodes
in the system
Define and set a password to protect the configuration and management database.
Make this password different from the root password.
You are prompted for this password any time you log into the configuration and
management database.
See Section B.2 (page 191) if you need recommendations on choosing strong passwords.
Database administrator's
password
You are prompted to configure an external Ethernet device on the head node. Doing
so connects the node directly to the public network. The most likely Ethernet device
to use as the external network connection is presented to you by default. You can
use this value or provide a different value.
If you need more information to verify that you are selecting the correct Ethernet
device on the head node, open a new terminal window and use the ethtool
ethernet-device-name command to provide more information about the Ethernet
devices on the node.
External Ethernet connection
on the head node
54 Preparing to Configure the System