HP XC System Software Installation Guide Version 3.2

3. If a new kernel is supplied in a patch, you must rebuild kernel-dependent modules. See the
HP XC System Software Administration Guide for more information about rebuilding
kernel-dependent modules.
4. Reinstall or upgrade any HP, open source, or third-party vendor software products that you
specifically installed (for example, debuggers, compilers, and so on) on the HP XC system.
• To upgrade or reinstall HP StorageWorks Scalable File Share (HP SFS) server or client
software, see the HP SFS Client Installation and User Guide for details.
• To upgrade or reinstall HP Scalable Visualization Array (SVA) Version 2.1 (which is
the SVA release that is compatible with HP XC System Software Version 3.2), follow
the instructions in Section 2.4.2 to run the SVA installation script. Then, optionally,
follow the instructions in Section 3.7.7.1.3 to install HP Remote Graphics Software (RGS)
and load the RGE module.
When you upgrade SVA to Version 2.1, do not rerun the svaconfigure command to
re-create the SVA site configuration file.
5. You might need to upgrade firmware according to master firmware list for this release:
http://www.docs.hp.com/en/linuxhpc.html
6. If you want to configure eligible services for improved availability, you must install and
configure an availability tool now.
See “Task 9: Plan a Service Availability Strategy” (page 28), which describes what improved
availability offers, how it is achieved, the supported availability tools, and the services that
are eligible for improved availability to determine if this is a feature you want to enable.
Proceed to “Task 7: Manually Merge File Customizations.”
5.8 Task 7: Manually Merge File Customizations
Follow this procedure to manually merge customizations you might have made to system
configuration files in the previous release. Customizations are not automatically merged into
the new version of the configuration files, and the contents of the new version of the file might
have changed in the new release:
1. Use the method of your choice to open and search the log files for HP XC configuration files
that have an .rpmsave or an .rpmnew extension appended to them. These files contain
user customizations that were not merged into the new files in this release. This example
uses the grep command to search for the affected files.
# grep -E ".rpmsave|.rpmnew" /var/log/yum_upgrade.log
2. Use the method of your choice (the diff command, for example) to determine differences
between the customized and current versions of configuration files. As software evolves,
configuration file formats might change. Carefully compare the original configuration files
to the new files before integrating your changes.
3. Carefully copy customizations from the *.rpmsave version of the file into the new version
of the file. Certain *.bak files must also be considered for merging if they have been
previously customized.
As an example, the /opt/hptc/systemimager/etc/chkconfig.map.rpmsave file
contains the previous customized contents, and you use it to determine the customizations
you have to manually add into the new version of the file, which is
/opt/hptc/systemimager/etc/chkconfig.map.
Table 5-5 contains a list of configuration files that are specific to HP XC and standard Linux
configuration files that are likely to contain user customizations that you must merge.
5.8 Task 7: Manually Merge File Customizations 125