Supported collection configurations, Comparison of agentless and up data collection, Supported collection – HP Matrix Operating Environment Software User Manual
Page 18
Collecting data for a workload with a HP Serviceguard package
You can associate a
with a Serviceguard package. This association allows
Matrix OE visualization to show workloads moving from one system to another within minutes of
a Serviceguard migration. It also allows Capacity Advisor to show an uninterrupted history of
utilization data for a workload across migrations.
Associating monitored workloads and Serviceguard packages requires that Serviceguard and the
corresponding version of the Utilization Provider have been installed on all member systems of the
Serviceguard cluster. For specific version information, see the HP Insight Management Support
Matrix.
Supported collection configurations
Table 1 Collection methods by operating system on CMS and managed node types
1
Collector for HP-UX CMS
Collector for Microsoft Windows CMS
Managed node software and/or
OS
not supported
virtual machine management
HP Insight Control virtual
machine management host or
guest
not supported
virtual machine management
Hyper-V VM
Integrity VM Provider and Utilization
Provider
Integrity VM Provider and agentless
method
Microsoft Windows on Integrity
VM
Integrity VM Provider and agentless
method
Integrity VM Provider and agentless
method
Linux on Integrity VM
Integrity VM Provider and Utilization
Provider
Integrity VM Provider and Utilization
Provider
HP-UX on Integrity VM
Utilization Provider
Utilization Provider
OpenVMS on Integrity VM
Utilization Provider (Integrity only)
agentless method
standalone Windows
agentless SSH
agentless SSH
standalone Linux
Utilization Provider
Utilization Provider
standalone HP-UX
Utilization Provider
Utilization Provider
standalone OpenVMS
1
Data is obtained from some managed system types using more than one collector. This is done where the data from both
collectors provide a broader or more accurate view than can be obtained from using only one collector on that managed
system type. For example, where both natively collected data (agentless) and data from the Integrity VM Provider are
used, the Integrity VM agent provides info about the VM that allows Capacity Advisor to obtain more accurate CPU data
for the VM, and the agentless method provides metrics other than CPU utilization.
Comparison of agentless and UP data collection
compares the operational characteristics of
and that
of the Utilization Provider when used to collect data from systems licensed for Capacity Advisor.
•
Agentless Data Collection. This method leverages native data collection already occurring on
the managed server(s).
•
WBEM Utilization Provider. This method uses an agent to gather the data and provide it to
the CMS.
18
Features