HP XC System Software Installation Guide Version 3.0

You may have to reboot the head node if there is a patch to the kernel; the patch README file provides
instructions if a reboot is required.
2. Reinstall or upgrade any previously installed HP, open source, or third-party vendor RPMs that you
specifically installed (for example, HP StorageWorks File System (SFS), TotalView, Intel compilers, and
so on).
Task 6: Manually Merge Customized Files
Perform the following tasks to manually merge customizations you made to system configuration files in the
previous release that were not merged into the new version of the configuration files:
1. Use the method of your choice to open and search the /var/log/postinstall.log file for XC
specific configuration files that have an .rpmsave extension appended to them. These files contain
user customizations that were not merged into the new files in this release. Table 7-5 illustrates how
the manual merge process works using the /opt/hptc/systemimager/etc/chkconfig.map file
as an example.
Table 7-5 Merging User Customizations After An Upgrade
You Merge the Customized Contents Into This FileYour Previous Customized Contents Are Contained In This File
chkconfig.mapchkconfig.map.rpmsave
The following example uses the grep command to search for the affected files:
# grep -E .rpmsave /var/log/postinstall.log
2. Use the method of your choice, such as the diff command, to determine differences between the
customized and current versions of configuration files. As software evolves, configuration file formats
might change. Carefully compare your 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.
Table 7-6 contains a list of XC specific configuration files and standard Linux configuration files that
are likely to contain user customizations that you must merge.
Table 7-6 Files Containing User Customizations
Important NotesFile Name
If the head node was previously configured as a
NIS slave server, do not merge the nis ports from
the iptables.proto.bak 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.bak
/hptc_cluster/slurm/etc/slurm.conf.bak
/etc/my.cnf.rpmsave
/opt/hptc/systemimager/etc/updgi_exclude_file.rpmsave
/opt/hptc/systemimager/etc/chkconfig.map.rpmsave
/opt/hptc/systemimager/etc/base_exclude_file.rpmsave
/opt/hptc/systemimager/etc/*.conf.rpmsave
/opt/hptc/config/*.rpmsave
/opt/hptc/config/etc/*.rpmsave
4. Follow the same process to find Linux specific customizations.
Use the method of your choice to open and search the /root/upgrade.log file for Linux specific
configuration files that have either a .rpmsave or a .rpmnew extension appended. This step should
only be necessary if you know you changed standard Linux configuration files.
82 Upgrading Your HP XC System