HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

Manager version 3.5 does not fully support them. A nested APA device is a grouping of
other APA devices. For example, if lan900 is an APA device composed of physical network
interface cards (NICs) lan1 and lan2, and lan901 is an APA device composed of physical
NICs lan3 and lan4, the HP network configuration utilities allow you to define a nested APA
lan902 device that is composed of lan900 and lan901. VM Manager does not fully support
a nested APA device such as lan902 as a backing device for a virtual switch. VM Manager
does fully support APA devices that are directly composed of physical NICs, such as lan900
or lan901.
When you use VM Manager to create a virtual switch, VM Manager does not list nested
APA devices (or their components) as possible backing devices to choose from. If a virtual
switch backed by a nested APA device already exists on a VM Host or virtual machine
managed by VM Manager, VM Manager displays the virtual switch on the VM Host, VM
Properties, and Vswitch Properties Network tabs as an unknown device (using the question
mark icon). VM Manager displays the correct LAN device name (such as lan902) but the
device is not associated with the physical network resources that comprise the APA device.
Workaround If you want to create a virtual switch that uses a nested APA backing device,
use the Integrity VM hpvmnet command. For more information about this command, see
the HP Integrity Virtual Machines Installation, Configuration, and Administration manual.
• VM Manager Does Not Fully Support Virtual Device Files Located in /hpap as Backing
Devices Integrity VM version 3.5 supports virtual device special files located in /hpap
(introduced in HP StorageWorks Secure Path software version 3.0F SP2) as backing devices
for virtual storage; however, VM Manager does not fully support these files as backing
devices for storage. When you use VM Manager to add or create a storage device on a virtual
machine, VM Manager does not display device files in /hpap as possible backing devices to
choose from. If a virtual storage device using an /hpap device special file already exists on
a virtual machine managed by VM Manager, VM Manager displays it on the VM Host and
VM Properties Storage tabs as an unknown device (using the question mark icon). VM
Manager displays the correct device special file name (for example, /hpap/rdsk/hpap1) but
the box representing this device is not connected to the boxes that represent the physical
storage devices associated with that virtual device special file. In general, VM Manager
correctly displays only those device special files located in /dev.
Workaround To add a virtual storage device that uses a virtual device special file in /hpap
to an existing virtual machine, use the Integrity VM hpvmmodify command. To add such
a device to a new virtual machine, use the hpvmcreate command. For more information
about these commands, see the HP Integrity Virtual Machines Installation, Configuration, and
Administration manual.
• VM Integrity V2.0 (and earlier) Providers Do Not Work with WBEM Services V2.5 or Later
Integrity VM WBEM providers that are version 2.0 or earlier are incompatible with HP
WBEM Services for HP-UX version 2.5 or later. If you install HP WBEM Services for HP-UX
version 2.5 on a VM Host where version 2.0 or earlier of an Integrity VM WBEM provider
is installed, when you access VM Manager, an error message from the VM Host's WBEM
server appears at the top of the VM Manager screen, and no data is available on that screen.
The error message is as follows:
An error occurred collecting data -- query failed.
An error occurred communicating with WBEM: CIM_ERR_FAILED CIM_ERR_FAILED: A GENERAL ERROR
OCCURRED THAT IS NOT COVERED BY A MORE SPECIFIC ERROR CODE.: "PGS00200: NULL POINTER."
To manage a VM Host with VM Manager and VSE Management Software, an Integrity VM
WBEM provider is required on the VM Host. Integrity VM WBEM providers are optional
on the virtual machines; however, HP recommends that you install them on each virtual
machine on a VM Host managed by VM Manager or VSE Management Software.
Workaround If you are required to install HP WBEM Services version 2.5 or later on a
virtual machine, first upgrade the Integrity VM WBEM provider on the virtual machine to
52 Known Issues