Realize new workload migration and consolidation possibilities

Process overview

• Review the new capabilities available on HP-UX vPars v6.1 and their associated resource requirements

• Design the new VSP (physical server) to meet your current and anticipated needs

• Install, provision, and configure the VSP

• Generate and run vPar creation scripts (or create the vPars with the Integrity Virtual Server Manager GUI)

• Install or migrate the virtual partition boot disks

• Install or update applications

• Mount/copy existing data disks

• Validate and tune the environment

Prepare for the migration

Review the new features and paradigms

It is strongly recommended that you review the section titled “An overview of HP-UX vPars and Integrity VM 6.1” in this

document and the HP-UX vPars and Integrity VM 6.1 Release notes. There are several new features that you may wish to

take advantage of which will impact your server configuration. For instance, NPIV is only supported by some of the

available Fibre Channel cards. Likewise, DIO for networking is supported only by a subset of the available network

interfaces (NICs).

You should also determine whether you are going to try to preserve your existing boot disk. This is not generally

recommended, but may be possible for SAN-based boot devices that have been updated within the last 2–3 years. It is

not possible to reuse boot devices from PA-RISC systems.

Once you have decided which capabilities are desirable, refer to the following table for the resulting configuration

impacts.

Table 1. Capability requirements

Feature Requirements

NPIV

NPIV capable HBAs include 451871-B21, 403619-B21, AH400A,

AH401A, AB378B, AB379B, AD193A, AD194A, and AD300A. More

HBAs may have been added since the writing of this paper.

DIO

DIO capable NICs include:

• SD2 & BL8x0 i2 LOMs

• NC532m, NC552m, and NC553m mezzanine cards

• AM225A/232A/233A, AT111A, and AT118A PCIe

“standup” cards

Offline migration to a different VSP

VSPs must be on the same SAN and subnet

DIO cannot be used

Serviceguard

VSPs for vPars participating in the same Serviceguard cluster

must have the same Fibre Channel and LAN connectivity that

physical servers for legacy vPars had