HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

NOTE: Many software subsystems require upgrades on the 11i v2 Integrity VM server before
updating to HP–UX 11i v3. The most obvious of these is that Integrity VM must be upgraded to
V3.0 or V3.5 before beginning the HP-UX upgrade. Other layered products, such as Serviceguard,
require version upgrades before updating the operating system to 11i v3. Analyze each layered
product for required upgrades.
Remove HP Integrity Virtual Machines Manager (vmmgr) Version 3.0 or earlier before upgrading
to Integrity VM Version 4.2. After installing Integrity VM V4.2, install Integrity VM Manager
V3.5 or later.
The latest available version of Integrity VM Manager is V4.1. You can use Integrity VM Manager
V4.1 with Integrity VM V4.2 and any earlier versions that are still supported. However, Integrity
VM Manager V4.1 is not guaranteed to support new features provided by Integrity VM V4.2.
NOTE: If you are upgrading an Integrity VM Host from 11i v2 to 11i v3 and are using Veritas
file systems and volumes, update to Veritas V5.0 and become familiar with the Veritas 5.0
Installation Guide.
2.3.3 Decide Whether to Perform a Cold-Install or an Update
The preferred method for upgrading an HP-UX 11i v2 based Integrity VM Host to an 11i v3
based VM Host is to use the Update-UX program. The update-ux command takes as input
the new 11i v3 OE depot. The update-ux command strives to maintain all your current user,
storage, and network configurations. There are some 11i v2 multipath solutions that are not
compatible with 11i v3. This same set of multipath solutions must be dealt with whichever
method you choose. In most cases, the multipath conversion is to use the agile devices on 11i v3
in place of the device names that the multipath solutions invented. The Update-Ux program
also strives to keep volume definitions the same. This is helpful because a cold-install most likely
changes all the device names requiring a mapping of devices to volumes and to guests.
One reason to choose a cold-install over an update-ux update is the ease by which you can
immediately return to the 11i v2 environment. The update-ux path changes the original 11i v2
system configuration making a restore from backups the only way to return to the original 11i
v2 system. The cold-install can and should be given separate disks to use allowing the original
11i v2 system disks to remain unchanged. Because the original disks can remain unchanged,
there is less of a need to back up the 11i v2 based Integrity VM Host.
NOTE: HP recommends a full back up of both the Integrity VM Host and guests before updating.
Whether an update-ux or a cold-install upgrade is chosen, the administrator needs to study
the documentation that covers the differences between HP-UX 11i v2 and HP-UX 11i v3. To
obtain input on potential upgrade problems, the administrator should also run the HP-UX
msv2v3check tool and the hpvmupgrade -e utility.
2.3.4 Perform Required Hardware and Firmware Upgrades
Perform all hardware and firmware upgrades that are supported on 11i v2 and that are needed
for 11i v3 while still running on 11i v2. This allows the administrator to verify that all guests are
fully functional with the changes before upgrading to 11i v3. Read the following information:
• Hardware Specific Information
• System Firmware Support Matrix
• Ethernet System Driver Support Matrix
• HP 9000 and HP Integrity Server Connectivity/
2.3 Upgrading the VM Host from Previous Versions of Integrity VM V3.X to Integrity VM V4.2 37