HP Insight Dynamics 6.0 Update 1 Release Notes

Application Discovery
Major issues
Restart Application Discovery service after installation
The Application Discovery service does not start properly after a DVD installation. The service
must be restarted once to run with full functionality.
Suggested action Restart the service.
Application Discovery service may run out of memory on initial start-up
On larger scale systems (on a 64-bit CMS), the Application Discovery service may run out of
memory and display an out of memory error on initial start-up. This can be corrected by modifying
the configuration file to increase memory allocation.
Suggested action Perform the following steps to increase the heap size parameter.
1. Modify the configuration file in the default location at C:\Program Files\HP\
VirtualServer Environment\conf\hp_ad_service.conf.
2. Increase the value of wrapper.java.maxmemory=768. HP suggests a value of 1536.
Capacity Advisor
Limitations
Automatic power calibration of Integrity Linux systems running SUSE 11 operating system is not
supported
The HP Insight Dynamics 6.0 software does not support the automatic power calibration of
Integrity Linux systems running the SUSE 11 operating system.
Suggested action Manually calibrate Integrity Linux SUSE 11 systems for power.
Sub-OS workloads on Linux systems are not supported
On x86 and Integrity Linux systems, Linux sub-OS workloads cannot be created or modeled,
and sub-OS workload data cannot be collected.
On Linux systems where the Utilization Provider was previously installed and sub-OS workloads
were defined, those sub-OS workloads will no longer be displayed in Virtualization Manager.
The definition of these sub-OS workloads on a Linux system will be removed from Virtualization
Manager by the upgrade process because they are no longer used by Insight Dynamics Global
Workload Manager (gWLM), nor supported by Capacity Advisor or Virtualization Manager.
Data collected for VMs or OS workloads that migrate across three or more dissimilar hosts in a
24-hour period may be marked invalid
Some historical performance data in Capacity Advisor will be marked as “invalid” (and will
appear to be missing in the Profile Viewer) when VMs or operating systems instances have
migrated across three or more VM hosts or servers with different clock speeds since the last
Capacity Advisor data collection. By default, invalid data is not included in Capacity Advisor
calculations.
Suggested action For planned migrations between dissimilar VM hosts or servers, always
collect Capacity Advisor data at least once between migrations to obtain a valid data sample for
each configuration visited. Alternatively, avoid frequent VM or OS migrations across three or
more dissimilar hosts or servers. If these actions are not possible (for example, for automatic
migrations within clusters with dissimilar hosts), you can validate any data that was invalidated
as a result of multiple migrations, and use it as an estimate of historical performance data, even
though it may not be accurately normalized.
18 Issues and suggested actions