HP Insight Dynamics 6.2 Release Notes

Suggested action
Manually calibrate Integrity Linux SUSE 11 systems for power.
Automatic power calibration requires power metering support in server
Auto-calibration of idle/max power with Capacity Advisor requires the power metering features
of iLO in the managed server. For information about which servers support power metering, see
Appendix A in the HP Insight Software 6.2 Support Matrix at www.hp.com/go/insightdynamics/
docs.
Suggested action
Manual power calibration is recommended for servers that do not support iLO power metering.
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.
NOTE: For Integrity VMs, data must always be collected prior to a migration. Failure to do so
will result in either incorrect data or a gap in data that starts from the time that the last collection
occurred before the migration and ends at the time that the VM was migrated.
See the HP Insight Capacity Advisor 6.2 Software: User Guide at www.hp.com/go/
insightdynamics/docs for information about showing, and optionally validating, invalid data.
Minor issues
Socket and core count inaccurate on Microsoft Windows 2003 and HP-UX 11 v2 (IA and
PA) systems
Windows 2003 and HP-UX 11 v2 (IA and PA platforms) operating systems may not correctly report
the number of processor sockets in a multi-core/hyperthreading environment.
Suggested action
The following patches are required to correct this issue.
Capacity Advisor 17