Operating Environment Software User Manual

Installing HP-UX portable Image
The HP-UX portable image product is a key component of the Integrity VM and HP-UX
cross-technology logical server feature. It provides the necessary operating system support to ensure
network configuration information is properly maintained across cross-technology move operations.
You must configure this product as part of your HP-UX installation. It is part of the Base OE for
1103, 1109, and future Fusion releases. However, it is not installed by default and you will need
to explicitly select the HP-UX Portable Image product during the OS installation process. The product
is named HPPortableImage B.11.31.1109 (or B.11.31.1103) HP-UX Portable
Image.
Turning on HP-UX portable image in the OS
This section describes the process to enable and disable the HP-UX portable image (PI) in the OS.
The HP-UX kernel global variable (tunable) gio_portable_image must be set to one (1) using
the kctune command to turn on the HP-UX PI functionality in the HP-UX OS.
• Enter the following command to turn on HP-UX PI:
kctune gio_portable_image=1
• Enter the following command to turn off HP-UX PI:
kctune gio_portable_image=0
HP-UX PI functionality ensures network instance numbers are properly maintained across move
operations to different target servers.
Powering off HP-UX
In order for the HP-UX PI product to properly prepare the system for move operations, you must
shut down the HP-UX OS prior to the move operation. This allows the HP-UX PI shutdown script to
run and save important information that will be used to ensure that the target server is properly
configured after the move.
If the OS is not properly shutdown, all network configuration files might need to be manually
reconfigured on the target as the network instance changes.
Network setup
The vSwitch network names on the Integrity VM Host must match exactly with the VC Ethernet
Uplink names that have been defined for the VC Domain Group that is configured in the same
portability group as the VM Host. For example, if you have a VC Ethernet Uplink defined as
“Sitelan,” then the vSwitch defined on the VM Host must be named “Sitelan” in order to properly
perform cross-technology logical server move operations.
SAN fabric setup
For HP Matrix OE logical server management, Integrity VM Hosts introduce a new concept that
requires all supported FC HBA devices to be named with a SAN fabric name. The FC HBA SAN
fabric names must match exactly with the VC FC SAN fabric names that have been defined for
the VC Domain Group that is configured in the same portability group as the VM Host. This is
conceptually similar to the network naming model where we assign vSwitch names to be consistent
with VC Ethernet uplink names.
This allows the target selection logic in logical server management to properly identify valid Integrity
VM Hosts available for physical to virtual move operations. In addition, virtual to physical move
operations are able to properly match up physical servers that are available for move operations
by validating the SAN fabric matches with one of the VC FC SAN fabric names.
Integrity VM and HP-UX cross-technology logical servers 31