Filter
Top Products
10.4 Upgrading from Integrity VM A.01.20 Toolkit
Extensive changes to the packaging of the Integrity VM A.02.00 ServiceGuard for Integrity VM Toolkit
require that customers remove the Integrity VM A.01.20 toolkit before installing the Integrity VM A.02.00
version. After you install Integrity VM A.02.00, repackage the distributed guests, as described in this
section.
To upgrade to Integrity VM A.02.00, perform the following sequence of steps on each VM Host node in
the multiserver environment:
1. Move the distributed guest to the adoptive node using the cmhaltpkg and cmrunpkg commands.
2. Remove the old toolkit from the VM Host system as described in “Removing the Serviceguard for
Integrity VM Toolkit” (page 126).
3. Install the Integrity VM A.02.00 product as described in Chapter 2 (page 21).
4. Move the distributed guest back to the VM Host system using the cmhaltpkg and cmrunpkg
commands.
5. Log in to the distributed guest and remove the old toolkit as described in “Guest Toolkit Removal”
(page 126).
6. Repackage the guest using the procedure described in “Repackaging Guests” (page 127).
10.4.1 Removing the Serviceguard for Integrity VM Toolkit
To remove the Serviceguard for Integrity VM toolkit, perform the following steps on the VM Host system:
1. Remove the toolkit package template files and scripts.
The old toolkit files should be removed from every VM Host in the multiserver environment.
Distributed guests andrequired resources are not affectedby removing the toolkit. Remove the toolkit
by removing the toolkit installation directory using the rm command, as follows:
# rm -rf /var/opt/hpvm/cluster
2. Remove the vswitch monitor script and files.
The vswitch monitor script consists of three files: the actual vswitchmon script and the symbolic
links used to start and stop the script during system boot and shut down. Distributed guests and
required resources arenot affected when you remove these files.If a reboot occursduring the interval
between the removal of vswitchmon scripts and the installation of the A.02.00 software, vswitch
monitoring istemporarily interrupted.Todelete the vswitchmonitor, deletethe associatedfiles using
the rm command as show in the following example:
# rm /sbin/init.d/vswitchmon /sbin/rc2.d/K004vswitchmon /sbin/rc3.d/S802vswitchmon
3. Remove the sepd tunable in every distributed guest configuration.
Removal of the sepd tunable is optional for Integrity VM A.02.00. The sepd tunable is specific to
Integrity VM A.01.20; it is not used in Integrity VM A.02.00. To remove the sepd tunable, remove
the sepd entryin the guest configurationfile at /var/opt/hpvm/guestname/, where guestname
is the name of the guest that was packaged under Integrity VM A.01.20.
10.4.2 Guest Toolkit Removal
To remove the Integrity VM A.01.20 guest toolkit, remove the hpvmsgping script from guests created
with theolder toolkit. Thehpvmsgping monitor scriptconsists ofthe hpvmsgping script,a configuration
file, and the links used to start and stop the script during system boot and shut down. Removal of these
files does not affect the currently running guests or the availability of the system. Delete the associated
files using the rm command as shown in the following example:
# rm /sbin/init.d/hpvmsgping /sbin/rc2.d/K003hpvmsgping /sbin/rc3.d/S801hpvmsgping /etc/hpvmsgping.conf
126 Using HP Serviceguard with Integrity VM