HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

The first thing the administrator must do is to identify subsystems on the 11i v2 Integrity VM server
that are incompatible with or that are not supported on 11i v3. Some incompatibility issues can
be exposed by tools, and others are found in referenced documents. The most common update
problems are caused by the following:
• Unsupported hardware adapters or firmware
• Memory and system disk space requirements (HP-UX 11i v3 has increased both of these.)
• Obsolete or unsupported storage multipath solutions
• Layered products requiring an 11i v3 compatible version
4.1.1 Study the current HP-UX 11i v2 to HP-UX 11i v3 update documentation
The first stage of upgrading an Integrity VM V3.0 or V3.5 server to an Integrity VM V4.x or V6.1
server is to review the following HP–UX 11i v3 operating system update documents:
• HP-UX 11i v2 to 11i v3 Mass Storage Stack Update Guide
• Read Before Installing or Upgrading
• HP-UX 11i v3 Installation and Update Guide
• HP-UX 11i Version 3 Release Notes
• Serviceguard Specific Documentation
The following websites provide a general reference covering the features and hardware supported
in HP-UX 11i v3. Read these documents and become familiar with the information before beginning
the upgrade procedure.
• QuickSpecs for HP-UX 11i v3 Update 2 features and operating environments
• Upgrading to HP-UX 11i v3
As you are reading, pay particular attention to the new mass storage model, called the agile device
reference model, for naming and identifying devices. The 11i v2 model is called the legacy device
reference model. The new agile device model uses worldwide device identifiers (WWIDs) to identify
devices. The WWID is a device attribute that is independent of the device’s location in a SAN or
in an adapter/controller access path. Therefore, the agile device names are persistent with respect
to changes in the access path and can utilize multiple paths through a single device name.
The legacy devices require multiple device names to access the same device through multiple paths.
Many Integrity VM customers use multipath solutions such as Secure Path, which allow them to use
a single device name to access all paths. Some of these 11i v2 multipath solutions will continue
to work, while others you must remove. The general solution for this particular problem is to replace
the existing multipath device with the new agile device name, with its inherent multipath support,
once the upgrade has completed.
NOTE: Dynamic Root Disk (DRD), an HP-UX system administration toolset, is available to clone
an HP-UX system image to an inactive disk for software maintenance or recovery. The bundle name
is DynRootDisk and the product name is DRD. Administrators can use DRD to reduce downtime
for system maintenance by creating an inactive clone of the booted system, then applying patches
and products to the clone. The modified clone can then be booted at a convenient time. DRD is
available for download from a software depot. For information about HP-UX Dynamic Root Disk,
see HP-UX 11i v3 Documentation.
4.1.2 Analyze HP-UX 11i v2 based Integrity VM server
Analyzing HP-UX 11i v2 based Integrity VM server is the most important stage of the Integrity VM
server upgrade. During this analysis, it is important to discover any incompatible hardware and
software subsystems. You can use the HP-UX 11i v2 to 11i v3 Mass Storage Check Utility
(msv2v3check ) to assist in the analysis.
4.1 Upgrading the VSP from previous versions of Integrity VM V3.x to Integrity VM V6.1 45