HP XC System Software Installation Guide Version 3.0

Appendix I Reinstalling an HP XC System with Version 3.0
This appendix describes how to reinstall HP XC System Software Version 3.0 on a system that is already
running Version 3.0.
Reinstalling an HP XC system with the same release may be necessary if you participated as a field test site
of an advance development kit (ADK) or an early release candidate kit (RC).
The procedure differs depending upon your cluster platform architecture:
• Reinstalling Opteron- or Xeon-Based Systems (page 131)
• Reinstalling Itanium-Based Systems (page 131)
Reinstalling Opteron- or Xeon-Based Systems
This section describes the following tasks:
• Reinstalling the Entire System (page 131)
• Reinstalling One or More Nodes (page 131)
Reinstalling the Entire System
Follow this procedure to reinstall Opteron- or Xeon-based systems with HP XC System Software Version 3.0:
1. Begin this procedure as the root user on the head node.
2. Ensure that all jobs are drained from all nodes, where nodelist represents the entire set of client
nodes (for example, n[1–64]):
# scontrol update NodeName=nodelist State=DRAIN Reason="system shutdown"
3. Shut down all nodes:
# stopsys
4. Insert the HP XC Version 3.0 DVD distribution media in the DVD tray on the head node.
5. Reboot the head node to start the Kickstart installation:
# reboot
6. Follow the instructions in this document, beginning with Chapter 3 (page 27), to complete the system
installation.
Reinstalling One or More Nodes
Follow this procedure to reinstall one or more Opteron- or Xeon-based client nodes from the latest golden
image on the image server. This procedure sets the specified nodes to network boot from the DHCP server
and automatically starts a reinstallation operation on the specified nodes by temporarily removing the
appropriate local boot file in the /tftpboot/pxelinux.cfg directory for each node to be reinstalled.
This example assumes nodes n1 through n5 are being reinstalled.
1. Begin this procedure as the root user on the head node.
2. Ensure that all jobs are drained from the affected nodes:
# scontrol update NodeName=n[1-5] State=DRAIN Reason="system shutdown"
3. Prepare the specified nodes to network boot instead of booting from local disk:
# setnode --resync n[1-5]
4. Reboot nodes n1 through n5:
# stopsys n[1-5]
# startsys --image_and_boot n[1-5]
The nodes automatically reboot when the reimaging is complete.
5. Reset the job state on nodes n1 through n5:
# scontrol update NodeName=n[1-5] State=IDLE
Reinstalling Itanium-Based Systems
This section describes the following tasks:
Reinstalling Opteron- or Xeon-Based Systems 131