BMC TrueSight Capacity Optimization v10.7.00 and later
EMC SMI-S Agent ETL for TrueSight Capacity Optimization relies on the EMC SMI-S provider to collect capacity information about the EMC storage systems. Refer to the table below to know which version of the EMC SMI-S provider should be used to collect information about your EMC Disk Arrays and EMC NAS.
|EMC Hardware||Supported versions of the EMC SMI-S Provider|
|CLARiiON (CX, CX3, AX series)2|
|CLARiiON (CX4, AX4 series)|
|Symmetrix DMX (DMX-2, DMX-3, DMX-4 series)|
|VMAX (10K, 20K, 40K series)|
|VMAX3 (100K, 200K, 400K series)3|
1 Tested and validated with EMC SMI-S Provider v220.127.116.11. For more recent versions, please contact our support team.
2 Tested and validated with EMC SMI-S Provider v4.4 for older versions of EMC CLARiiON.
3 The full support of VMAX3 is available only if you apply the Feature Pack 1 (10.7.01) of TrueSight Capacity Optimization 10.7.
EMC Celerra supports the embedded SMI-S provider v8.1.0.
Before installing the EMC SMI-S Agent ETL for TrueSight Capacity Optimization, you must ensure that the following requirements are met.
|CPU||2 x 64 CPUs (or 2 virtual CPUs)|
|Disk space||50 GB, 10K rpm class|
|Network||1 Gb/s network adapter|
|TrueSight Capacity Optimization||A version supported by the ETL. Refer to the Compatibility details section for the exhaustive list.|
|Operating System||A supported 64-bit version of Linux or Solaris.|
The SCHEDULER_HEAP_SIZE environment variable must be set to the following heap size: 2048m
Before installing the EMC SMI-S Agent ETL for TrueSight Capacity Optimization, you must ensure that the following elements are installed and properly configured:
To collect information about EMC Celerra storage systems, EMC SMI-S Agent ETL for TrueSight Capacity Optimization leverages the SMI-S Provider embedded within the Control Station. This SMI-S provider is installed by default when the base NAS software is installed in the directory /celerra/wbem on the Control Station.
To enable the embedded SMI-S provider:
Uncomment the following lines in the nas_mcd.cfg file:
Restart the NAS services:
Start the CIM Server:
To collect capacity information about EMC CLARiiON and VNX systems, you must ensure that the following prerequisites are met:
EMC SMI-S Agent ETL for TrueSight Capacity Optimization leverages the EMC SMI-S Provider for CLARiiON and VNX systems that needs:
The following procedure explains in details how to get, install and configure EMC SMI-S Provider to enable the ETL to efficiently interact with it.
Before installing the EMC SMI-S Provider, please note that the system hosting the EMC SMI-S Provider requires:
The SMI-S Provider also needs to be configured with a "Heap Size" of 4 GB.
To install the SMI-S Provider:
Before adding CLARiiON/VNX disk arrays, please note that EMC states that the EMC SMI-S Provider can manage up to 5 arrays, with up to 10,000 volumes each. Real-life experience shows that the scalability of the EMC SMI-S Provider depends on:
The performance of the EMC SMI-S Provider is affected by the number of client applications performing concurrent data requests. For example, if both TrueSight Operations Management and TrueSight Capacity Optimization are to extract metrics for EMC, the SMI-S Provider has to be sized accordingly, i.e. to handle twice the workload described in this page.
The most important factor is the number of volumes. As a result, an EMC SMI-S Provider can handle up to 50,000 volumes. The maximum number of volumes that can be handled by EMC SMI-S Agent ETL for TrueSight Capacity Optimization 10.7 are listed below:
|Discovery cycle||System collect cycle||Storage collect cycle||Volume collect cycle||Maximum number of volumes|
|24h (default)||15 minutes (default)||1h (default)||24h (default)||30,000|
EMC does not recommend managing more than 50,000 volumes per SMI-S Provider.
The CLARiiON/VNX Array is now added to the installed SMI-S provider.
You must list the information for storage processor A first, then storage processor B. Any time a locally-attached CLARiiON is added to the EMC SMI-S Provider, the EMC CIM Server must first be shut down. Once shut down, the authorization information can be added as described below and the EMC CIM Server must be restarted.
Use the SYMCLI symcfg command, as shown in the following syntax example, to add the username and password for each CLARiiON storage processor:
Add authorization for CLARiiON storage processor A with IP address <ip1>, username clariion and password clarpass, using the following command:
If you are using a version older than SMIKit 6.4.2, the EMC SMI-S Provider does not recognize changes in the array when a LUN or RAID Group is created or deleted from Navisphere. It is thus recommended to upgrade your EMC SMI-S Provider to version 6.4.2 or higher to benefit from the auto-synchronization mechanism set by default to one hour after the last update. If you do not upgrade your EMC SMI-S Provider, you will have to run the refsys command from testsmiprovider each time you create or delete LUN or RAID groups from Navisphere.
To manage EMC VMAX and Symmetrix DMX systems, the EMC SMI-S Provider requires at least one LUN to be mounted from each array to manage. These special LUNs are called "gatekeepers" and are used for the communication between the Symmetrix array and the SMI-S Provider (which does not have an IP address). EMC recommends having between 4 and 6 gatekeeper LUNs for each managed array. Increasing the number of gatekeepers dramatically improves the performance of the EMC SMI-S Provider.
Complete the following steps to deploy the ETL Module:
A successful installation will result in a green line in the Additional Packages table.
Complete the following steps to configure an ETL service and add it as an ETL task to extract capacity and performance metrics:
Specify values for the common and advanced properties that are listed under the expandable tabs. To view or configure advanced properties, click Advanced.
For details about the common properties, see Common configuration properties. The following table lists the properties that are specific to the EMC SMI-S Agent ETL module:
Hostname or IP address of the server where the EMC SMI-S Agent is running.
Port number used by the EMC SMI-S Agent (Default: 5989).
Username to connect to the EMC SMI-S Agent.
Password to connect to the EMC SMI-S Agent.
Transport protocol used by the EMC SMI-S Agent (for HTTP, the default port is 5988; for HTTPS, the default port is 5989).
ETL additional settings
|Shares||This property allows you to fine-tune the creation of shares entities in the TrueSight Capacity Optimization environment. For more information, refer to.|
|Volumes||This property allows you to disable or enable volumes monitoring and fine-tune the creation of volume entities in the TrueSight Capacity Optimization environment. For more information, refer to.|
|Levels up to||
By default, extended level metrics are not imported by the ETL. To import them, you will have to customize the collection level and set it to  Extended.
The ETL relies on the EMC SMI-S Provider to collect information about EMC storage systems. Because some connectivity issues may exist and cause the ETL to fail, it is highly recommended to test the connection to this specific component. The procedure is as follows:
Discovering volumes and/or shares and collecting their performance metrics are resource-intensive actions that can create extra workload on the system. To reduce the system resource consumption, administrators can disable or enable the volumes and/or shares monitoring at will and fine-tune the creation of volume and/or share entities into the TrueSight Capacity Optimization environment.
The following metrics are no longer collected and displayed in the console when volumes monitoring is disabled:
From the Shares/Volumes pull-down lists, select one of the following options:
Use this configuration if the number of volumes/shares to manage significantly slows down the system performance. Disabling the volumes/shares monitoring prevents the discovery of volumes and consequently does not allow the ETL to collect, save or process their data. Note that the calculation of metrics for other sources may be impacted.
|Collected for metric computation (Default)|
Use this configuration if you wish to collect and process volume/shares-related metrics without loading this information in the console. The collected data will however be used to calculate metrics for other sources, when required. This will reduce the resource consumption of your system.
|Collected and Imported|
Use this configuration if your system is powerful enough to manage all the volumes to monitor.
Host-related metrics are not available when the option Disabled and Collected for metric computation (Default) are selected.
An ETL task can be run manually to retrieve performance metrics. Please note that the steps listed in this section are not mandatory and are only required if the ETL is not already scheduled for execution.
To run the ETL task:
When the execution is complete, the value of the Status column in the ETL tasks table changes to SERVICE_ON.
The collect frequency is the rate at which data is collected. Collect frequency is set to 15 minutes by default, which means that it only applies to entities with an average duration of 900 seconds. It can however be modified to include more entities and performance metrics.
To know the average duration, under the Worskpace tab, select one entity, click the Metrics tab, and verify the Average duration column of the performance metrics.
To set the collect frequency:
EMC SMI-S Agent ETL for TrueSight Capacity Optimization defines the following lookup fields:
|Entity type||Lookup fields|