HP Capacity Advisor 7.2 User Guide

the first argument. (See the corresponding command reference pages in Appendix (page 193)
for more information.)
For example:
# capovpaextract node12.company.com
Ascertaining the data collection availability for a set of servers
From within a scenario, or from the Matrix OE Visualization tab, you can see the data collection
period for systems included in a scenario or for individual managed systems, respectively. This
procedure describes how to create a list of selected (or all) licensed servers and their data collection
periods, and is for use when you want to quickly see the data collection periods for a set of servers
without creating or accessing a scenario to do so.
Prerequisites
• You must have command-line access to the CMS managing the systems of interest.
• The systems of interest must be licensed for Capacity Advisor.
Procedure 9 From the command line
• Type
capprofile -lv
to see a list showing the name of each licensed system managed by this CMS, dates for which
data has been collected, and the percent of data considered valid by Capacity Advisor.
For other options, see capprofile in Appendix (page 193).
To return to a planning checklist:
• Obtaining reports on current resource usage (page 131)
• Estimating potential power savings across a range of servers (page 149)
Possible sources of discrepancies in collected data
Several possibilities exist to explain discrepancies that may appear in the data or that may affect
data collection. Check these possibilities to understand what actions you can take to correct the
discrepancy.
No data collected for a managed node
If you do not obtain data on systems from which you expect to collect data, it is possible that the
system has not been licensed for use with Capacity Advisor, either through Matrix Operating
Environment or through HP Capacity Advisor Consolidation software.
Data timestamp appears to be incorrect
For best accuracy in providing simulation solutions and historic reporting of actual system resource
use, it is assumed that the time clocks of managed nodes are synchronized with the time clock of
the central management server. If, on gathering or collecting data, the date stamp on your data
is not current, the time or time zone on a managed node may be set incorrectly in relation to the
CMS.
Dynamic memory in HP Integrity virtual machines
A dynamic memory feature is available in HP Integrity virtual machines. This allows the memory
allocated to each virtual machine to be changed without rebooting the virtual machine. Capacity
Advisor is aware of this feature and records both the memory allocated to each virtual machine,
as well as how much of this memory is in use for each five-minute interval. Both of these values are
correct when the virtual machines are using the dynamic memory feature.
Gathering data for Capacity Advisor 45