Operating Environment Software User Manual

The setup consists of an Integrity VM Host in one enclosure (source) and a bare metal server on
another enclosure (target).
1. Configure an Integrity VM Host (HP-UX 11.31 1109, HPVM 4.3 PK2) for NPIV functionality
(HP-UX PI installed and enabled, vSwitch and FC configured.
2. In HP Systems Insight Manager, license and configure the Integrity VM Host and the bare
metal server for Matrix OE and VMM.
3. Create the portability group containing the source and target enclosures, and the Integrity VM
Host.
4. Create and activate NPIV-based VM logical servers on the Integrity VM Host via LSA.
5. Manually deploy the HP-UX OS on these NPIV-based VM logical servers.
6. Power off and deactivate these NPIV-based VM logical servers from the Integrity VM Host via
LSA.
7. Import and move the Integrity VM Host VC-based logical server to another blade in different
enclosure via LSA.
a. Ensure that HP-UX PI is installed and that the kctune gio_portable_image=1
command has been run on the source system.
b. Ensure that the source is properly shut down.
8. After the VC-based logical server move, re-register the Integrity VM Host for VMM, re-identify
and run the logical server refresh.
9. Activate the NPIV-based VM logical servers on the target Integrity VM Host.
Observe that the Integrity VM Host is not listed in the available target selection list.
Suggested action
To resolve this situation, adjust the above steps so that the following is done directly after the
physical to physical move (Step 7) of the VM Host and before the reactivation of the VM logical
server (Step 9) as follows:
1. After the physical to physical move of the VM Host, edit the portability group of the logical
server and remove the VM Host that was moved.
2. Rediscover and re-license the VM Host that was moved.
3. Edit the portability group and add the VM Host again.
Importing an Integrity VM guest with no boot path
An Integrity VM guest configured with SAN-based storage fails during an import operation with
an error message similar to the following:
Import failed for 16.92.100.170. The HP Integrity VM guest uses NVIP
storage but has no boot path configured. A boot path is typically
inserted when HP-UX is installed, or by the HP-UX setboot command or
through the EFI Boot Maintenance Manager.
This issue can occur in the following example scenarios:
1. Create a new Integrity VM guest using SAN-based storage and a LUN that has not been
provisioned with an OS.
a. Create an Integrity VM guest on the VM Host using the hpvmcreate command.
b. Start the guest.
c. Import the guest into LSM using the import operation. An error message similar to the
following is displayed:
Import failed for 16.92.100.170. The HP Integrity VM guest uses
NVIP storage but has no boot path configured. A boot path is
typically inserted when HP-UX is installed, or by the HP-UX
setboot command or through the EFI Boot Maintenance Manager.
Troubleshooting use of HP-UX portable image 77