HP XC System Software Installation Guide Version 3.0

Table 7-2 Upgrade Characteristics
DescriptionCharacteristic
There is a period of system down time because all nodes have to be shut down
in order to upgrade to the next release. Therefore, to minimize user interruption,
schedule the upgrade for a time when system use and user activity is low. For
your site, this might be over the weekend or perhaps after work hours or late
in the evening.
Effect on system availability
The upgrade does not affect XC licensing. Your current XC license is still valid,
and you do not require a new XC license.
However, you must contact your HP representative to upgrade your license
file if your previous HP XC system was configured with LSF-HPC with SLURM
and you want to switch to the standard LSF option in Version 3.0.
Effect on HP XC licensing
It takes approximately 30 minutes to upgrade the head node. The number of
nodes to be reimaged influences the amount of time it takes to complete the
entire upgrade process. You must also allow some time to upgrade your
third-party applications as well.
Time to complete the upgrade
The upgrade process attempts to upgrade all Linux and HP XC RPMs currently
installed on your system.
Effect on existing RPMs
The upgrade process preserves existing configuration files by renaming them
with a .rpmsave file extension.
You must perform amanual merge for any standard Linux or HP XC
configuration files that contain previous user customizations.
Effect on configuration files
You must reimage any nodes that are in a DOWN state during the upgrade
when they are returned to operation.
Effect on nodes that are down
Is Upgrading Right for Your System?
An upgrade path from the HP XC System Software Version 2.n stream of releases to Version 3.0 is provided,
but HP recommends a new installation of Version 3.0. This recommendation is consistent with other Linux
vendors, who also recommend a new installation rather than an upgrade because the Linux upgrade operation
has a lower probability of success and does not provide a consistent experience. In some cases, some Linux
RPMs might fail to operate properly after the upgrade.
Readiness Criteria
Use the requirements listed in Table 7-3 to determine whether or not an upgrade is appropriate for your
system. Your system must meet all requirements in order for an upgrade to be successful.
Table 7-3 Upgrade Readiness Criteria
RequirementSoftware Component
Versions 2.0, 2.0A, or 2.1Version of HP XC System Software currently
installed on your system
The firmware revision installed on all system components must be updated
according to the Version 3.0 master firmware revision list located at:
http://www.hp.com/techservers/clusters/xc_clusters.html
Firmware
You must have in your possession the HP XC System Software Version 3.0 DVD
that is appropriate for your cluster architecture
Distribution media
Task 1: Prepare for the Upgrade
Perform the following tasks before you begin an upgrade of your system. Make sure you are logged in as
the root user on the head node.
1. Use your preferred backup solution to perform a full backup of the head node. If the upgrade is not
successful, you might have to revert to the previously installed release.
2. To change your system's hardware configuration, you must add or remove nodes before or after the
upgrade. Adding or deleting nodes during the upgrade process is not supported.
78 Upgrading Your HP XC System