HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

Discovery agent can be stopped by running /opt/amgr/bin/agent_stop as root on
the HP-UX– or Linux-managed system.
• If the clock on managed systems are off by more than a few minutes to the current time on
the CMS, then the Application Discovery agent communication with the CMS may be delayed
by the clock differential.
• Application Discovery user interface screens display OS version number “SLES0” for SLES10
Linux managed nodes.
Capacity Advisor
Limitations
• Headroom ratings are not available for scenario targets.
• The capreport command does not support complexes or scenarios as targets.
• The Scenario Comparison report does not support network I/O and disk metrics.
• The option that allows you to choose whether to display data in percentages, absolute
numbers, or both is not available on the Scenario Comparison report.
• PMP data cannot be imported from a virtual machine.
• You cannot edit more than one scenario at a time.
• On a Windows CMS, the capreport command can only be executed by users who are
members of the Administrators group.
• Automatic IPM power calibration on the Edit Power Settings pages requires that IPM and
iLO2 Advanced or iLO2 Select be properly licensed, configured, and discovered. There is a
time delay of up to a day before power and utilization data is collected from iLO2 by IPM
for use by Capacity Advisor. This data collection can be started manually from the IPM user
interface. Configuration of IPM requires Administrator privileges.
Major Issues
• Capacity Advisor Extension Pack licenses available with VSE Management Software Version
4.0 will incorrectly have the value of “Free Trial” in the License Source field in the HP SIM
License Manager graphical interface, even though they have been purchased.
• If the Profile Viewer or Scenario Editor displays no data for a node (“Error: No data has
been collected for the specified workload”), and this occurs even after a successful collection
from that node (that is, data collection completes without errors), then restarting Systems
Insight Manager or rebooting the CMS may correct the issue.
• Reporting algorithms are not optimized to minimize CPU and memory consumption on the
CMS.
Workaround For best results and minimal impact to system performance, limit the number
of systems included in any one report. For example, with 512 MB maximum heap size and
2 GB RAM on the CMS and a year of data, run the report on no more than 50 managed nodes
at a time.
• The cappmpextract command (command-line interface for HP PMP data import) reports
one physical CPU for machines that actually have dual-core processors, as compared to data
provided by the Utilization Provider, which would report two CPU cores.
Workaround Do not include PMP and Utilization Provider data within the same report.
If necessary to do so, mark the PMP data as invalid to obtain a more useful analysis.
• There is a substantial difference in data reported by PMP agents and Utilization Provider
agents when one logical NIC is composed of two physical networks. This difference affects
the usefulness of network utilization reports that contain both types of data.
• If you encounter the following error message in a Capacity Advisor data collection output:
Capacity Advisor 33