HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

the license from the old node name to the new one. Do this by selecting the Show
All Licensed Systems option.
— Change the preferred name of the re-added node to its original name using the
Edit System Properties dialog in HP SIM.
Virtualization Manager
Limitations
• On the Visualization tab, the Virtual Machine perspective does not show VMware Virtual
Center data centers, clusters, or resource pools.
Workaround To see this information, go the HP SIM System Properties page for the
virtual machine.
• 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 will be 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
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.
Major Issues
• A “serious error” page will be displayed with Java errors when trying to save user preferences
if logged into HP SIM on a Windows CMS and supplying a domain name upon login. To
fix this issue, create a directory with the same name as the domain name under <vse
install directory>\userprefs\, where <vse install directory> is the root
directory of the VSE install (by default it is C:\Program Files\HP\Virtual Server
Environment\).
Minor Issues
• When a managed node that is part of a shared resource domain is monitored by version
1.7.14.1 of the utilization provider, the Visualization tab and the Workload tab do not
correctly display immediate CPU utilization and memory utilization. In this case, the
utilization data is only available on the SRD tab.
If the managed node is monitored by an earlier version of the utilization provider, the
visualization and workload tabs should display the data as expected. Use the swlist
UtilProvider command to list the version of utilization provider.
• If Capacity Advisor data collection succeeds for VMware ESX Guests, but no new data is
displayed for the guest in the Capacity Advisor Profile Viewer (that is, the “Data exists
between” dates/times do not change), try restarting the the VMM agent (Configure→Virtual
Machine Management→Restar t VMM Agent...) on the VMware ESX Host.
After restarting the VMM agent, click the Retry link in the resource utilization popup
window.
30 Known Issues