HP XC System Software Installation Guide Version 3.2

Removing XC MLIB RPMs
upgradesys output logged to /var/log/upgradesys/upgradesys.log
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 the HP XC Support team at the following e-mail address:
xc_support@hp.com
2. Review the /opt/hptc/systemimager/etc/base_exclude_file to determine if you
want to exclude files from the golden image beyond what is 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. Decide on the cluster_config option to use to configure the upgraded system. Table 5-6
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.
Table 5-6 Upgrade Options for the cluster_config Utility
--init Option--migrate Option
Initializes (resets) your existing node role assignments
and configures the system with the default node role
assignments in this release.
This option does not preserve role-to-node assignments
from the previous release.
The default roles and assignments have been optimized
for performance and you might decide that this
configuration is better suited for your environment.
See Appendix F (page 209) for a description of roles
and the services provided by them, as well as the
default node role assignments.
Brings existing, recognized roles in the configuration
and management database into alignment with the
new roles introduced in this release.
This option retains information about role assignments
and preserves role-to-node assignments.
Using this option does not guarantee the correct
migration process for unrecognized (user-created) roles
and services in the configuration and management
database.
Before you decide to use this option, view the
/opt/hptc/etc/sysconfig/upgrade/role_migration.ini
file to see how the previous role assignments compare
to the roles provided in the new release.
4. Change directory to the configuration directory:
# cd /opt/hptc/config/sbin
5. Specify one of the following cluster_config options:
To migrate the existing system configuration:
# ./cluster_config --migrate
To apply new default role assignments to the existing system configuration:
# ./cluster_config --init
6. If you followed the instructions in “Task 9: Plan a Service Availability Strategy” (page 28)
to install an availability tool and position related scripts to set up improved availability of
services, you are prompted to configure availability sets now. “Task 8: Configure Availability
Sets” (page 86) describes how to configure availability sets. Return here when you are done.
7. View the role assignments when the cluster_config utility displays the command-line
options menu:
[L]ist Nodes, [M]odify Nodes, [A]nalyze, [H]elp, [P]roceed, [Q]uit: l
5.9 Task 8: Configure the System and Propagate the Golden Image 127