HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

version 3.0 or later. If HP WBEM Services version 2.5 or later is required on a VM Host,
upgrade Integrity VM to version 3.0 or later.
Minor Issues
• A Virtual Machine Deleted Soon After Being Created Might Appear in Virtualization
Manager When using VM Manager from HP SIM with VSE, if you create a virtual machine
and then delete it before the new virtual machine has been identified by HP SIM, the virtual
machine might appear in Virtualization Manager as though it had not been deleted. The
appearance of the virtual machine in Virtualization Manager depends on when the deletion
occurred during the HP SIM identification process.
Workaround When using VM Manager with VSE to create a virtual machine, if you decide
to delete the virtual machine soon thereafter, wait a few minutes before doing so. If the
deleted virtual machine does appear in Virtualization Manager, delete it from the HP SIM
All System view. (From the HP SIM Systems and Event Collections list in the navigation
area on the left, select All Systems. For more information, see the HP Virtualization Manager
Version 4.0 Getting Started Guide.)
NOTE: Another disjunction between VM Manager actions and Virtualization Views might
occur when you create a virtual machine using VM Manager and immediately return to
Virtualization Manager. If HP SIM has not yet completed identifying the new virtual machine,
the machine does not yet appear in Virtualization Manager. However, it does appear when
the identification process completes (usually within a minute or two).
• Create Virtual Machine Wizard Next Steps Instructions Display Incorrect Command The
Next Steps screen that appears after you create a virtual machine using the VM Manager
Create Virtual Machine wizard includes instructions for accessing the console. The
instructions incorrectly advise specifying the -F option with the hpvmconsole command.
Workaround Do not specify the -F option. Specify the command as follows, where vmname
is the virtual machine name:
hpvmconsole -P vmname
Instant Capacity Manager
Limitations
• For the Instant Capacity Manager, when non-root accounts are used to retrieve WBEM data,
some of the values displayed by Instant Capacity Manager may not match the icapstatus
command output on the managed system.
Workaround Use a privileged account or WBEM Certificate-Based Authentication to access
WBEM information on the managed nodes.
• Instant Capacity (iCAP) Manager supports Instant Capacity 8.02 or later.
• The GiCAP WBEM provider only allows privileged access. As such, GiCAP information,
including information about GiCAP groups, will not be available to non-privileged users.
Workaround Use WBEM certificate-based authentication for the systems that are GiCAP
group managers. Certificate-based authentication requires WBEM A.02.05 or later.
Minor Issues
• Data is missing for complexes within a GiCAP group.
Workaround Visit the complex page or the GiCAP group page that contains the complex.
• Red duplicate gadget messages are listed due to complexes showing in both the upper table
and a GiCAP group.
Workaround Click the Refresh data link on the page.
Instant Capacity Manager 53