HP XC System Software Installation Guide Version 3.2
Table 5-2 Upgrade Characteristics (continued)
DescriptionCharacteristic
If a node or nodes is in the DOWN state during the upgrade, you must
reimage those nodes as soon as they are returned to operation.
Affect on nodes that are down
You cannot add or remove nodes during the upgrade process.Affect on number of nodes
5.1.4 Upgrade Commands
Table 5-3 lists the commands and utilities that are run as part of a software upgrade process.
Table 5-3 Commands Used During the Upgrade Process
DescriptionCommand or Utility Name
Prepares the system for the upgrade.
preupgradesys
Installs new versions of HP XC RPMs.
upgraderpms
Backs up the existing configuration and management database and
migrates existing data to the new release format.
upgradesys
Reconfigures the system after the upgrade. You have the option to
migrate the existing configuration or apply the new default role
assignments to the existing configuration.
cluster_config [--migrate|--init]
5.2 Task 1: Prepare for the Upgrade
Perform the following tasks before you begin the upgrade process. Make sure you are logged in
as the root user on the head node.
1. Use the information listed in Table 5-4 to ensure that your system meets all requirements.
Your system must meet all requirements in order for an upgrade to be successful.
Table 5-4 Upgrade Readiness Criteria
RequirementComponent
The current HP XC system must be running HP XC System Software
Version 3.0, Version 3.1 ADK, or Version 3.1.
Version of HP XC System Software
currently installed on the system
The firmware versions installed on all system components have
been updated according to the Version 3.2 master firmware list:
http://www.docs.hp.com/en/linuxhpc.html
Firmware
You must have in your possession the HP XC System Software
Version 3.2 DVD that is appropriate for the cluster platform
architecture.
Distribution media
2. Notify users in advance that a software upgrade is planned. Because you must shut down
all nodes, plan the upgrade for a time when system activity is at its lightest.
3. Use your preferred backup solution to perform a full backup of the head node, which can
be done while the head node is up and when jobs are running. If the /hptc_cluster file
system is located on an HP SFS server, ensure you back up the SFS server as well.
It can be beneficial to have online access to the contents of the /etc, /opt/hptc, and
/hptc_cluster directories after the upgrade in case you need to look at previous
configuration files for configuration information.
If the upgrade is not successful, you might have to revert to the previously installed release.
5.2 Task 1: Prepare for the Upgrade 121