HP XC System Software Administration Guide Version 3.0
Enter the network type of your system.
Valid choices are QMS32 or QMS64: [QMS64]:
e. When prompted, enable Web access to the Nagios monitoring application and create a password
for the nagiosadmin user. This password does not have to match any other password on your
system.
Running C50nagios
Would you like to enable web based monitoring? ([y]/n) y
Enter the password for the 'nagiosadmin' web user:
New password: your_nagios_password
Re-type new password: your_nagios_password
f. The cluster_config utility prompts you that it recognizes an existing slurm.conf file and
asks if you want to reconfigure it.
Answer n if the slurm.conf file has any changes that you made manually. Otherwise, answer
y.
The cluster_config utility adds the node to the slurm.conf file in either case.
g. The golden image is created automatically, and all other system services are configured and
started.
9. Boot the system and propagate the golden image to the new node or nodes with the startsys
command:
# startsys --image_and_boot node_name
The node_name indicates the newly added node or nodes.
10. Run the spconfig utility.
# /opt/hptc/sbin/spconfig
Replacing a Client Node
The following procedure describes how to replace a faulty client node in an HP XC system. The example
commands in the procedure use node n3.
CAUTION
Do not use this procedure to replace the head node.
CAUTION
The replacement node must have the identical (exact) hardware configuration to the node being replaced;
the following characteristics must be identical:
• Number of processors
• Memory size
• Number of ports
1. Prepare the replacement node hardware as described in the
HP XC System Software Hardware
Preparation Guide
. Note the following requirements for each replacement node:
• The node must be set to boot from the network.
• The console port (cp) is set to request IP addresses through DHCP.
• The node's power must be turned off.
2. Log in as superuser on the head node.
3. If your system is a CP4000, execute the following command:
# setnode --resync n3
4. Perform the following steps if the power for the node to be replaced is currently on:
a. Issue the following command to prevent any further job scheduling on the node to be replaced:
168 Servicing the HP XC System