HP Matrix Operating Environment Software - Manual (Page 142)

List profileID, available history, and percent valid. (Note that a Percent Valid value of less than
100% can occur when there is invalid or uncollected data. For example, there may be one or two
uncollected data samples on a node right after it reboots.)
capprofile -lv
Name Available History Percent Valid
node01.co.com 01/17/06 05:30 pm - 01/19/06 10:10 am 100.00%
node02.com 12/18/05 05:00 pm - 01/20/06 01:05 pm 99.96%
billing3 12/10/05 05:00 pm - 01/20/06 01:05 pm 100.00%
node03.com.OTHER 01/15/06 03:05 pm - 01/18/06 12:55 pm 82.83%
cimserver 01/17/06 05:30 pm - 01/19/06 10:10 am 99.78%
Import profile data from the file /tmp/nonMatrixOEWorkloadFile.txt for the profile with
profileID nonMatrixOEWorkload.
capprofile -i -p nonMatrixOEWorkload < /tmp/nonMatrixOEWorkloadFile.txt
List profile summaries for non-Matrix OE workloads:
# capprofile -l -p Non-MatrixOE-Workloads-Name
externalBilling2
accounting1
monitoring
FILES ON CMS
/var/opt/vse/profile/bin
•
Root directory for storing collected data for capprofile.
Note that the format of these data files may change without notice from release to release.
The file system where these files are stored needs to be sized to hold all the daily utilization
profile data, which for each system, is about 32K per day per workload, taking into account
minimum block size of 4K.
For example, with a CMS monitoring 100 systems, each with an average of 3 workloads,
with a need to keep historical data for one year, the file system where the profile resides must
have space for (100 systems + 300 workloads) * 365 days * 32K = 4.45 Gigabytes. With
a file system that allocates storage in blocks greater than 24K, then use the larger block size.
AUTHORS
capprofile was developed by Hewlett-Packard Company.
DOCUMENT LAST UPDATED
January 2012
SEE ALSO
capprofile(4), capovpaextract(1M), vseinitconfig(1M)
142 Command reference