Data Collection for Capacity Overview > Architecture Overview
  
Version 9.2.01
Architecture Overview
Capacity Manager provides end-to-end storage capacity reporting from the hosts to the storage arrays. The Data Collector is a software component that is responsible for interfacing with one or many storage arrays for information related to the capacity management environment. In most cases, the Data Collector software module can reside on any server within your network that is Java 1.7 compatible and, where applicable, has a working copy of specific storage array command line utilities already installed. The exception is EMC Symmetrix, which requires the Data Collector to reside on the server that manages the arrays. The following diagram illustrates how the Capacity Manager Data Collector could be deployed in your environment:
Figure 1.1 Data Collector for Capacity Manager
The Data Collector obtains all of its monitoring rules from a configuration file maintained in the database. This file is called the Data Collector Configuration File and is stored in the database in XML format. When the Data Collector is first started, it downloads the Data Collector Configuration File from the database. The Data Collector uses this file to determine the list of storage arrays that are to be monitored and included in its data polling.
In most cases, a single instance of the Data Collector can support any number of storage arrays. The only real limitation is the memory and CPU processing power of the server on which the Data Collector resides. For each storage array, the Data Collector will establish connections to the database. The Data Collector Configuration file contains all the connection information for each server including such parameters as the hostname / IP address of the server.
The Data Collector communicates with the storage array’s system service processor (SSP) to gather storage capacity data. The information is then sent via http(s) to the Portal. Users can then access the Portal via a web browser.
Which Data Collector Policies Are Needed?
Policies need to be configured via the Portal to establish communication with the installed Data Collectors. The following example illustrates a typical Capacity Manager deployment for array and host data collection.
In this example of 100 Linux servers:
50 servers will have only capacity information collected
Another 50 servers will have capacity information collected, plus some of those servers will also have Host Resources data collected:
5 Memory
2 Network
1 Oracle Server
Storage Array Prerequisites
Before you install Data Collectors, refer to the individual array vendors for additional specific prerequisites.
Pre-Installation Setup for Dell Compellent
Pre-Installation Setup for EMC Isilon
Pre-Installation Setup for EMC VNX Celerra
Pre-Installation Setup for EMC VNX CLARiiON
Pre-Installation Setup for EMC VPLEX
Pre-Installation Setup for Hitachi Block
Pre-Installation Setup Hitachi NAS
Pre-Installation Setup for HP 3PAR
Pre-Installation Setup for HP EVA
Pre-Installation Setup for NetApp E-Series/IBM Modular
Pre-Installation Setup for IBM Enterprise
Pre-Installation Setup for IBM SVC
Pre-Installation Setup for IBM VIO
Pre-Installation Setup for IBM XIV
Pre-Installation Setup for NetApp
Pre-Installation Setup for NetApp Cluster
Pre-Installation Setup for NetApp E-Series/IBM Modular
Host Resource Prerequisites
For specific prerequisites, refer to Host Resources Prerequisites and Configurations.
Array Performance Data Collection Prerequisites
The following array families are supported for block storage LUN performance and port performance data collection.
LUN Performance Metrics
Array Family
Read/Write IO/sec
Total IO/sec
Read/Write
MB/sec
Read/Write Cache Hits/sec
Read/Write Response (ms)
Total Response (ms)
Dell Compellent
X
X
X
X
--
--
EMC VNX (CLARiiON) 1
X
Calculated
X
X
X
Calculated
EMC Symmetrix
X
X
X
X
--
--
HDS Tuning Manager 2
X
Calculated
X
X
X
X
HP 3PAR
X
X
X
X
--
--
IBM SVC
X
X
X
--
--
--
IBM XIV
X
X
X
X
X
X
NetApp ONTAP (Block only) 3
X
Calculated
X
--
--
Avg Latency
1 For CLARiiON arrays: The minimum FLARE OS version required to capture response times is 04.30.000.5.524 A11. Note that VNX (Block) will have completely different FLARE releases and all support the collection of the counter fields needed for capturing response time, starting with FLARE version 05.31.000.5.006 A01.
2 For Hitachi arrays: To collect performance data from Hitachi Tuning Manager, the Data Collector must be installed on the same server as Tuning Manager. And, a single Data Collector policy must be used to collect both the capacity data from the Device Manager server and the performance data from the Tuning Manager server.
3 For NetApp ONTAP (Block only): Total response time is the average latency (ms) for all LUN read and write operations. Performance data is collected for both iSCSI LUNs and FC LUNs.
4 For Dell Compellent: Only Fibre Channel port statistics are collected.
Port Performance Metrics
Array Family
Read/Write MB
Total MB
Read/Write I/O
Total I/O
Dell Compellent 4
X
Calculated
--
X
EMC VNX (CLARiiON)
Not Supported
Not Supported
Not Supported
Not Supported
EMC Symmetrix
--
X
--
X
HDS Tuning Manager
X
X
X
X
HP 3PAR
X
Calculated
--
X
IBM SVC
Not Supported
Not Supported
Not Supported
Not Supported
IBM XIV
X
X
X
X
NetApp ONTAP (Block only)
X
Calculated
--
--
Calculated = Calculated from collected data, X = Collected from the array, -- = Not Collected