HP XC System Software Installation Guide Version 4.0

NOTE: You will see a message "upgrading from v3.1 to 4.0" even though you are upgrading
from another version. This message is expected and you can ignore it.
IMPORTANT: Do not proceed to the next step in the upgrade process if the output from
the upgradesys script indicates failures. If you cannot determine how to resolve these
errors, contact your local HP support center.
The state of the cluster is unstable at this point because the definition of all network interfaces
has been removed. It is important to complete the remaining steps in this task as soon as
possible. The network configuration files are recreated after the cluster_config step has
completed. You must allow cluster_config to generate a new image in order for all
configuration steps to be run.
2. Review the /opt/hptc/systemimager/etc/base_exclude_file to determine if you
want to exclude files from the golden image in addition to the files that are already excluded.
The base_exclude file file is the file that is read when the golden image is re-created
as part of the upgrade process. The HP XC System Software Administration Guide describes
how to add exclusions to this file.
3. If you are using the InfiniBand interconnect, verify that the appropriate configuration files
were successfully changed so that the HP XC system is using the same type of InfiniBand
software stack as the SFS system. The sfsconfig should have changed the following files:
/etc/modprob.conf
/etc/modprobe.conf.lustre
/etc/modprobe.conf.lustre.*
a. If you are using the OFED InfiniBand software stack, verify that the lnet option is
added in the /etc/modprobe.conf.lustre file, and it looks similar to the following
line:
options lnet networks=o2ib0
b. Verify the /etc/sfstab.proto file to ensure that the appropriate lnet entries were
created and the InfiniBand interconnect interface used is o2ib0 (and not vib0). If this
is not the case, contact HP SFS Support for more information on how to manually change
the /etc/sfstab.proto file.
c. If necessary, when all of the above mentioned files are correct (and you are able to
automatically mount the SFS file system on the head node), verify that the corresponding
files under /var/lib/systemimager/images/base_image/etc are also correct
and replace the files.
4. Decide on the cluster_config option to use to configure the upgraded system. Table 9-7
describes two options to the cluster_config utility that you can use to reconfigure a
system after a software upgrade. The option you choose depends upon how you want the
upgrade to proceed.
9.9 Configuring the System and Propagating the Golden Image 149