HP-UX vPars and Integrity VM V6.3 Administrator Guide

NOTE: Many software subsystems require upgrades on the 11i v2 Integrity VM server before
upgrading to HP-UX 11i v3. Integrity VM must be upgraded to V3.0 or V3.5 before beginning the
HP-UX upgrade. Other layered products, such as Serviceguard, must be upgraded before upgrading
the operating system to 11i v3. Analyze each layered product for the required upgrades.
Remove the older HP Integrity Virtual Machines Manager product before upgrading to vPars and
Integrity VM Version 6.3. After installing vPars and Integrity VM V6.3, install the latest Integrity
Virtual Server Manager and HP-UX GUID Manager products. If you are upgrading an Integrity
VSP 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 available at
nl
http://www.hp.com/go/hpux-LVM-VxVM-docs.
4.1.3 Deciding whether to perform a cold-install or an update
The preferred method for upgrading an HP-UX 11i v2 based Integrity VSP to an 11i v3 based VSP
is to use the Update-UX program. The update-ux command takes as input the 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. 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 retain the
volume definitions. This is helpful, because a cold-install most likely changes all the device names
requiring a mapping of devices to volumes and to guests.
To choose a cold-install over an update-ux update is the ease with 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 must be given separate disks to use allowing the original 11i v2 system
disks to remain unchanged. Because the original disks can remain unchanged, the need to back
up the 11i v2 based Integrity VSP is minimal.
NOTE: HP recommends a complete back up of both the Integrity VSP and guests before updating.
Whether you choose update-ux or a cold-install upgrade, as the administrator you must study
the documentation that covers the differences between HP-UX 11i v2 and HP-UX 11i v3. To obtain
information about potential upgrade problems, you must also run the HP-UX msv2v3check tool.
4.1.4 Upgrading required hardware and firmware upgrades
While still running on 11i v2, perform all the hardware and firmware upgrades that are supported
on 11i v2 and that are needed for 11i v3. This allows the administrator to verify that all the guests
are fully functional with the changes before upgrading to 11i v3.
4.1.5 Performing a cold-install or an update
If you choose the cold-install upgrade path, it means the administrator is taking the responsibility
for fully configuring the 11i v3 Integrity VSP to be functionally equivalent to the 11i v2 Integrity
VSP configuration. vPars and Integrity VM V6.3 provides the hpvmdevtranslate utility to assist
in mapping the legacy devices used by guests on the 11i v2 VSP to the new 11i v3 agile devices.
The hpvmdevtranslate utility produces the script /var/opt/hpvm/common/
hpvm_dev_convert. This script must be reviewed and edited before running it to make the
conversions. Device conversions that cannot be made are listed as comments labeled ERROR:.
The administrator is responsible for determining the conversion of the ERROR lines. The
hpvmdevtranslate utility translates only devices that provide unique WWIDs.
After evaluating your 11i v2 Integrity VSP and performing appropriate backups, carry out the
following steps with the hpvmdevtranslate utility as part of a cold-install:
4.1 Upgrading VSP from Integrity VM V3.x to vPars and Integrity VM V6.3 47