HP XC System Software Installation Guide Version 3.1

5. You might need to upgrade firmware according to Master Firmware List. The master firmware list
for this release of the HP XC System Software is available at the following Web site:
http://www.docs.hp.com/en/highperfcomp.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 26), 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 may 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 and an .rpmnew extension appended to them. These files contain user customizations
that were not merged into the new files in this release. The file you view depends on the type of
upgrade you performed. This example uses the grep command to search for the affected files.
• Major upgrade
# grep -E ".rpmsave|.rpmnew" /var/log/postinstall.log
• Minor upgrade
# 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-7 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.
Table 5-7 Files Containing User Customizations
Important NotesFile Name
*.bak files
/hptc_cluster/slurm/etc/slurm.conf.bak
*.rpmsave files
If the head node was previously configured as
a NIS slave server, do not merge the nis ports
from the iptables.proto.rpmsave file into
the iptables.proto file because the
nis_server service automatically opens the
necessary ports when it is configured during
cluster_config processing.
/etc/iptables.proto.rpmsave
/etc/my.cnf.rpmsave
/opt/hptc/systemimager/etc/updgi_exclude_file.rpmsave
/opt/hptc/systemimager/etc/chkconfig.map.rpmsave
5.8 Task 7: Manually Merge File Customizations 103