Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Integrity Virtual Machines Version 4.0 Installation, Configuration, and Administration > Chapter 2 Installing Integrity VM

Upgrading the VM Host from Integrity VM V3.X to Integrity VM V4.0

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Integrity VM Version 4.0 VM Host requires the HP-UX 11i v3 operating system. Only HP-UX 11i v2 servers running Integrity VM Version 3.0 or Version 3.5 can be upgraded to the HP-UX 11i v3 Integrity VM Version 4.0 release. This section describes the process to follow when upgrading an HP-UX 11i v2 based Integrity VM server to an HP-UX 11i v3 based Integrity VM server.

HP-UX 11i v3 supports many features that are backward compatible with 11i v2, allowing 11i v2 applications to run without modifications. The primary goal of this section is to provide direction to the administrator performing the upgrade of the VM Host to make sure that all configured virtual machines (guests) boot and run after completing the upgrade to 11i v3.

Figure 2-1 provides a flowchart of the upgrade procedure.

Figure 2-1 Upgrade Procedure

Upgrade Procedure

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

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.0 server is to review the following HP–UX 11i v3 operating system update documents:

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.

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 http://docs.hp.com/en/DRD.

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 ) and the Integrity VM hpvmupgrade tool to assist in the analysis.

The msv2v3check tool is free software provided on the http://software.hp.com website. Go to this website, search for msv2v3check, and download this free tool.

The hpvmupgrade tool is provided with Integrity VM V4.0. Use one of the following ways to obtain this tool:

  • Download VMGuestLib from the http://software.hp.com website and follow the instructions documented there.

  • Install VMGuestLib from HP-UX 11i v2 AR media, September 2008 or later.

These analysis utilities are aimed primarily at mass storage problems and problems that are specific to existing virtual machines. In most cases, you can take actions to resolve these incompatibilities before doing the upgrade, such as loading new firmware. Other solutions might require waiting until after the upgrade, such as substituting agile devices for an 11i v2 multipath solution. Another area of particular concern is the layered products running on your 11i v2 based Integrity VM server. Analyze each layered product to determine its upgrade impact:

  • No change - Layered product is compatible.

  • Delete/reinstall - Layered product requires a new version to work on 11i v3.

  • Delay upgrade – Layered product needs a new version that has not yet released.

For more information, see the following documents:

Run the HP-UX msv2v3check Tool

The HP-UX msv2v3check command reviews all mass storage controllers and devices on your system for HP-UX 11i v3 compatibility and support. In addition, msv2v3check attempts to verify that your system meets other 11i v3 system requirements, particularly the minimum memory required and supported platforms. For more information , see the getconf (1M) and model (1M) HP-UX commands.

The msv2v3check command looks at only mass storage controllers (host bus adapters) and devices for HP-UX 11i v3 compatibility and support. This includes the following:

  • Ultra160 SCSI (C8xx) host bus adapters and attached HP supported SCSI devices

  • Ultra320 SCSI (MPT) host bus adapters and attached HP supported SCSI devices

  • Serial Attached SCSI (SAS) host bus adapters and attached HP supported SAS devices

  • Smart Array RAID (CISS) host bus adapters and attached HP supported RAID devices

  • Fibre Channel (FCD/TD) host bus adapters and attached HP supported Fibre Channel devices

  • HP supported SCSI disk enclosures and arrays

  • HP supported Fibre Channel disk enclosures and arrays

The msv2v3check command creates the following log file in the /var/adm/msv2v3check/ directory:

/var/adm/msv2v3check/mmddyy_hhmm is the full log file that contains all notes, warnings, and error messages from an invocation of msv2v3check, where mmddyy_hhmm represents the month, day, year, hours and minutes at the time the msv2v3check utility was started.

Once the msv2v3check utility has completed, a validation result is displayed that indicates the number of errors and warnings detected on your system configuration:

  • An error is a critical message that indicates that your system does not support HP-UX 11i v3 in its current configuration. Do not ignore this message.

  • A warning indicates a task that might require user action, for example, upgrading the firmware on a disk device, or manually reviewing the firmware of a Fibre Channel disk array.

Review all warnings and make the necessary corrections before upgrading to HP-UX 11i v3.

For supported I/O drivers, devices, adapters; see the following document on the HP documentation website:http://docs.hp.com/en/5991-6460/ch02s04.html.

Run the Integrity VM Upgrade Tool

The Integrity VM upgrade tool, hpvmupgrade, can be run on either an 11i v2 or an 11i v3 system. This tool focuses on analyzing guest configurations for problems that might cause the guest not to boot when running on an 11i v3 Integrity VM server. Run this utility during the upgrade analysis stage.

To run this utility, use the following command:

# hpvmupgrade –e

It produces the following log file:

/var/opt/hpvm/common/hpvmupgrade.current_date_and_time

This log file contains a section for each guest configured on the server and displays the following message types:

  • Warning messages indicate problems that can cause a guest booting problem.

  • Error messages indicate problems that can cause a guest problem. For example, if a guest’s virtual disk is backed by a file or device that does not exist on the 11i v2 system, a warning is issued because the problem is likely to be the same on the 11i v3 system. If, however, a guest is using a device associated with a multipath solution that is no longer supported on 11i v3, an error is issued.

The Integrity VM upgrade tool is focused on the devices that are used to back guest virtual devices. Each guest configuration is queried for its virtual backing storage. The guests device list is then compared to known multipath solutions, AutoPath, Secure Path, PowerPath PVLinks, or Veritas DMP devices to detect any dependencies.

Because ,the 11i v3 storage stack supports native multipath access to devices through the agile device names, the common solution for old 11i v2 multipath solutions is to remove them and change the applications to reference the new agile devices.

The upgrade tool also examines guest devices for volume backing storage that was used with multipath devices for physical storage. If this dependency is found, it is flagged in the log file. This tool also verifies that the 11i v2 Integrity VM server is at V3.0 or V3.5.

Determine HP-UX 11i v3 Memory and System Disk Requirements

Integrity VM V4.0 memory requirements vary depending on the number and size of virtual machines supported by the Integrity VM server. When upgrading from an 11i v2 Integrity VM server, use the following steps to determine the amount of memory required for the 11i v3 Integrity VM server:

  1. When your 11i v2 Integrity VM server is running at peak load, use the Integrity VM hpvmstatus –s command to display the available memory.

  2. If the available memory is less than 1 GB, then it is highly likely that your server requires additional memory to run the same load with 11i v3 and Integrity VM V4.0. Before upgrading, add the appropriate amount of memory to ensure that there is at least 1 GB of memory available during peak loading.

NOTE: Different operating environments have different minimum memory requirements

Determine Version Requirements for HP-UX OE and Integrity VM

Only HP-UX 11i v2 servers running Integrity VM Version 3.0 or Version 3.5 can be upgraded to the HP-UX 11i v3 Integrity VM V4.0 release. HP recommends that all virtual machines (guests) be upgraded with Integrity VM Version 4.0 guest kits to take advantage of performance enhancements and bug fixes. Guests that booted and ran on the 11i v2 Integrity VM server will continue to function with equivalent or improved performance after the upgrade.

Existing guest configuration information, operating system software, and application data are not affected when you upgrade Integrity VM. However, when you upgrade, also reinstall the guest kit that is provided with Integrity VM. This operation requires you to reboot the guest. For more information, see Section .

If you have installed the evaluation version of Integrity VM (software bundle T2801AA), remove the evaluation software before installing the Integrity VM product (see Section ).

The reasons for exceptions to this behavior, such as when guests do not boot after the upgrade, are defined in the following documents. The 11i v3 Update 2 release that Integrity VM V4.0 requires has changed its OE packaging. For information about the new 11i v3 OEs, see these documents:

The following are the new HP-UX OEs:

  • HP-UX 11i v3 Base OE (BOE)

    The BOE provides and integrated HP-UX operating environment for customers who require less complex installations. The Base OE includes the entire original Foundation Operating Environment (FOE), and offers complete HP-UX functionality including security, networking, web functionality, and software management applications.

  • HP-UX 11i v3 Virtual Server OE (VSE-OE)

    The VSE-OE provides an integrated HP-UX operating environment for customers who seeking higher resource utilization or who are embarking on consolidation projects and need virtualization for a flexibile UNIX environment. The VSE-OE contains all the products included in the BOE (and the original EOE) and adds a host of other products including the entire VSE suite. The VSE-OE includes Integrity VM (T2767BC).

  • HP-UX 11i v3 Data Center OE (DC-OE)

    Business-critical virtualization builtin—The Data Center OE is the offering for customers who are consolidating, or building an infrastructure for the future. Because the powerful software within the DC-OE is integrated and tested with the operating system, it is an effective choice for a highly available virtualized environment. DC-OE is a complete, fully tested, and integrated UNIX offering. The DC-OE includes Integrity VM (T2767BC).

  • HP-UX 11i High Availability OE (HA-OE)

    For customers requiring continuous access to data and applications, the HA-OE delivers the protection of Serviceguard and related software. The HA-OE also delivers all the software in the Base OE plus what has shipped until now in the Enterprise OE.

Table 2-3 lists the HP-UX 11i v2 to HP-UX 11i v3 supported OE server upgrades.

Table 2-3 Supported Operating Environments

Original 11i v2 Operating EnvironmentsNew 11i v3 Operating Environments
Foundation OEBase OE
Technical Computing OE Base OE
Enterprise OE Virtual Server OE
Mission Critical OEData Center OE

 

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 V4.0. After installing Integrity VM V4.0, install VMMgr Version 3.5 or later.

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.

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.

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:

Perform Either a Cold-Install or an Update

If the cold-install upgrade path is chosen, the administrator is taking the responsibility for fully configuring the 11i v3 Integrity VM Host to be functionally equivalent to the 11i v2 Integrity VM Host configuration. Integrity VM V4.0 provides the hpvmdevtranslate utility to assist in mapping the legacy devices used by guests on the 11i v2 VM Host to the new 11i v3 agile devices.

The hpvmdevtranslate utility produces the script /var/opt/hpvm/common/hpvm_ev_convert. This script needs to 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 world wide identifiers (WWIDs).

After evaluating your 11i v2 Integrity VM Host and performing appropriate backups, use the following steps with the hpvmdevtranslate utility as part of a cold-install:

  1. Choose the system disks that are to be used for the 11i v3 VM Host and make them as reserved disks.

    # hpvmdevmgmt -a rdev:device_name
  2. Back up and collect all relevant configuration from the 11i v2 VM Host.

  3. Back up the /var/opt/hpvm directory so that you can easily restore it to the 11i v3 system after the cold-install.

    NOTE: DRD can be used to clone an HP-UX system image to an inactive disk for recovery. For information about DRD, see http://docs.fc.hp.com/en/DRD.
  4. Verify that all current guests that run on 11i v2 can boot and run successfully. Guests that cannot boot on 11i v2 cannot be expected to boot after the upgrade to 11i v3.

  5. After verifying the guests, back up all relevant configuration data for each guest for a potential return to 11i v2.

  6. Shut down the Integrity VM guests gracefully by logging into each one and shutting it down.

  7. Shut down the Integrity VM Host.

  8. Using the HP-UX cold-install procedure, install the appropriate 11i v3 OE using the selected system disks. For information about performing a cold-install, see the HP-UX 11i v3 Installation and Update Guide.

  9. Remove any blocking layered products that might block the Integrity VM installation.. See Section  for a list products.

  10. Remove layered products that might cause problems or that require a new 11i v3 compatible version after the HP-UX 11i v3 upgrade.

  11. Determine the order of installation of layered products, including Integrity VM V4.0 (T2767BC), so that all dependencies are met. For example, if Veritas is used to provide backing storage for guests, install it before Integrity VM..

  12. Install all 11i v3 compatible layered products that are required for equivalent functionality to the 11i v2 VM Host.

  13. Install Integrity VM Version 4.0 to the 11i v3 VM Host.

    NOTE: See Section  for a list of products that block the Integrity VM installation.
  14. Stop Integrity VM using /sbin/init.d/hpvm stop.

  15. Using the appropriate recovery tool, restore the 11i v2 /var/opt/hpvm directory over the existing 11i v3 /var/opt/hpvm directory on the 11i v3 VM Host.

  16. Start Integrity VM using /sbin/init.d/hpvm start.

  17. Run the translator:

    # hpvmdevtranslate -a /var/opt/hpvm/common/hpvm_mgmtdb_pre1131
  18. Edit the script, /var/opt/hpvm/common/hpvm_dev_convert, taking note of ERROR lines and commenting out the exit line that prevents the running of the script.

  19. Continue with the remaining 11i v3 Integrity VM Host configuration until the host is functionally equivalent to the former 11i v2 Integrity VM Host.

If you choose the update path, follow these steps:

  1. Create a recovery image.

  2. Verify that all current guests that run on 11i v2 can boot and run successfully. Guests that cannot boot on 11i v2 cannot be expected to boot after the update to 11i v3.

  3. After verifying the guests, back up all relevant configuration data for each guest for a potential return to 11i v2.

  4. Install the latest Update-UX bundle from the OE media.

  5. Update the OS/OE from the HP-UX 11i v3 OE media using the update-ux command. For example:

    # swinstall -s /dev/dvd Update-Ux update-ux -s /dev/dvd/HPUX11i-VSE-OE T2767BC
    NOTE: There is a new update-ux option, –p, which previews and update task by running the session through the analysis phase first.

    If you are updating from the VSE-OE depot, specify the following:

    # swinstall -s my.server.foo.com:/OEdepot/path Update-UX update-ux -s my.server.foo.com:/OEdepot/path HPUX11i-VSE-OE T2767BC
  6. Remove any blocking layered products that might block the Integrity VM installation. See Section  for a list products.

  7. Remove layered products that might cause problems or that require a new 11i v3 compatible version after the HP-UX 11i v3 update.

  8. Determine the order of installation of layered products, including Integrity VM V4.0 (T2767BC), so that all dependencies are met. For example, if VERITAS is used to provide backing storage for guests, install it before Integrity VM.

  9. Install Integrity VM Version 4.0 to the 11i v3 VM Host.

  10. Update non-OE applications from the Application media using the swinstall command.

    For example, if you plan to install VMMgr, switch to the AR disk and specify the following:

    # swinstall -s my.server.foo.com:/Ardepot/path VMMGR
  11. Create the recovery image.

Verifying Guests after Installing Layered Products

Follow these steps after installing layered products:

  1. Use the hpvmupgrade utility to see whether any guests have configuration problems.

  2. Start and stop each guest, one at a time, and make sure that they boot to their OS.

  3. Use the guest troubleshooting section, Chapter 12, to resolve guest booting problems.

  4. Upgrade each guest with the new guest kit.

  5. If the guest OS is no longer supported, upgrade the guest OS.

Upgrade Troubleshooting Issues

After you upgrade to 11i v3, examine the following issues:

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.