|
|
United States-English | |
|
|
 |
|
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 |
|
|
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. 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:
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.
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:
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:
For more information, see the following documents: 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:
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:
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. 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:
It produces the following log file:
This log file contains a section for each guest configured on the server and displays the following message types:
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. 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:
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:
Table 2-3 lists the HP-UX 11i v2 to HP-UX 11i v3 supported OE server upgrades. Table 2-3 Supported Operating Environments
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.
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 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: 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:
If you choose the update path, follow these steps:
Follow these steps after installing layered products:
After you upgrade to 11i v3, examine the following issues:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
