This topic provides information about BMC Capacity Optimization configuration for collecting data directly from VMware environments using one of the following ETL tasks:
You cannot run the VMware - vCenter Extractor and VMware - vCenter and ESX Server History Extractor service simultaneously. To import the historical or legacy data from vCenter and ESX servers you first need to start the VMware - vCenter and ESX Server History Extractor, then stop this service. Once the historical data is imported, start the VMware - vCenter Extractor service which continuously polls and collect data from vCenter servers.
Note
For information about how to configure BMC Capacity Optimization to collect data for VMware environments from BMC Performance Assurance, see Integrating with BMC Performance Assurance.
BMC Capacity Optimization supports collecting data from the following VMware environments:
VMware host | VMware - vCenter Extractor Service | VMware - vCenter and ESX Server History Extractor |
---|---|---|
VMware ESX Server 3.5 | ||
VMware ESX Server 4.0 (vSphere) | ||
VMware ESX Server 4.1 (vSphere) | ||
VMware ESX Server 5.0 (vSphere) | ||
VMware vCenter Server 4.0 (vSphere) | ||
VMware vCenter Server 4.1 (vSphere) | ||
VMware vCenter Server 5.0 (vSphere) | ||
VMware vCenter Server 5.1 (vSphere) | ||
VMware vCenter Server 5.5 (vSphere) |
You can configure BMC Capacity Optimization to collect data from a VMware environment by performing one of the following procedures:
For information about importing events from a VMware environment, see Importing VMware events into BMC Capacity Optimization.
For information about the metrics collected by the VMware ETL modules, see Metrics collected by the VMware ETLs.