Large Deployment For Up To 150,000 Metrics Per Second

CA Performance Management Data Aggregator Deployment Scenarios › Large Deployment For Up To 150,000 Metrics Per Second

Large Deployment For Up To 150,000 Metrics Per Second

The following information describes the requirements for a large deployment that is intended to support 150,000 metrics per second, for monitoring up to one million monitored devices and components. This deployment can be configured on the following seven-host physical machine environment:

One CA Performance Center host
Three Data Repository hosts in a cluster
One Data Aggregator host
Two Data Collector hosts

Note: For information about CA Performance Center system requirements, see the CA Performance Center Release Notes.

Data Repository Requirements

The following table lists the minimum system requirements for installing each Data Repository host.

Component	Requirement
Operating system	Red Hat Enterprise Linux 5.x for x64 Red Hat Enterprise Linux 6.x for x64 Note: Upgrading an existing RH5 Vertica installation to an RH6 installation is not supported.
Processor	12 cores
Processor speed	2.5 GHz
Memory (RAM)	96 GB
Disk space	3 partitions are required for the following directories: catalog directory data directory backup data directory Note: For information about disk space, see the system sizing tool, which is available in the 'Recommended Reading' section on support.ca.com.
Disk input/output	200 Mega Bytes/second

Data Aggregator Requirements

The following table lists the minimum system requirements for installing the Data Aggregator host:

Component	Requirement
Operating system	Red Hat Enterprise Linux 5.x for x64 Red Hat Enterprise Linux 6.x for x64 Note: Upgrading an existing RH5 Vertica installation to an RH6 installation is not supported.
Processor	12 cores
Processor speed	2.5 GHz
Memory (RAM)	48 GB
Disk space	100 GB Note: If Data Export will be used for one hour of data export, a second, separate 5 GB partition is required.
Disk input/output	100 Mega Bytes/second

Note: The data loading process has been rearchitected to persist all polled data temporarily to files on Data Aggregator before loading the data into Data Repository. Polled data files are removed once they are loaded into Data Repository. As a result, the amount of available disk space on Data Aggregator will fluctuate over time.

Data Collector Requirements

The following table lists the minimum system requirements for installing each Data Collector host.

Important! This information is specific to each of the two Data Collector instances. In practice, multiple lighter Data Collector instances can be substituted, as long as the combined capacity does not exceed one million monitored devices and components. For example, you can use five virtual Data Collector instances to approximate one large one. You can see how many devices and components Data Collector is monitoring in the Data Collector List view. For more information about the Data Collector List view, see the Data Aggregator Administrator Guide.

Component	Requirement
Operating system	Red Hat Enterprise Linux 5.x for x64 Red Hat Enterprise Linux 6.x for x64 Note: Upgrading an existing RH5 Vertica installation to an RH6 installation is not supported.
Processor	4 cores
Processor speed	2.5 GHz
Memory (RAM)	32 GB
Disk space	50 GB
Disk input/ouput	100 Mega Bytes/second

Note: For information about prerequisite steps and installation, see the Data Aggregator Installation Guide.

Multi-tenant Deployment Considerations

In a multi-tenant deployment, note the following considerations:

Data Aggregator can be shared between tenants. The information for each tenant is secure and other tenants cannot view this information.
Data Collector is not shared among tenants. However, a tenant can have more than one Data Collector.
Where a managed service provider is monitoring devices for multiple tenants, you can install Data Collector at the MSP site.
Note: This setup requires Data Collector to gain access through a tenant firewall to poll the devices that are being managed.