HP XC System Software Administration Guide Version 3.1
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. 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:
# scontrol update NodeName=n3 State=DRAINING Reason="Maintenance"
b. Invoke the stopsys command to shut down the node gracefully:
# stopsys n3
WARNING!
Verify that the power is disconnected to prevent injury or death.
5. Remove the faulty node from the HP XC system.
Note the ports for the Ethernet and system interconnect cables.
6. Add the replacement node to the HP XC system.
Ensure that you reconnect the Ethernet and system interconnect cables to their respective ports and
that you connect the power cable.
7. Enter the following command to force the discovery of the MAC address of the replacement node's
boot interface:
# /opt/hptc/config/sbin/discover --replacenode=n3
NOTE: The -oldmp option is also required for CP6000 systems because their management processors
(MPs) have statically-set IP addresses and are not configured to use DHCP. Thus, for CP6000 systems,
the command to force discovery of the MAC address of the replacement node's boot interface is:
# /opt/hptc/config/sbin/discover --oldmp --replacenode=n3
8. Turn on the replacement node's power:
# startsys --image_and_boot n3
9. Run the spconfig utility:
# /opt/hptc/sbin/spconfig
10. Return the node to service:
21.2 Replacing a Client Node 245