BMC TrueSight Capacity Optimization v10.7.00 and later
All NetApp storage filers with Data ONTAP up to version 9 (both 7-mode and C-mode). For more recent versions, please contact our support team.
We recommend using Data ONTAP version 8.3. For more recent versions, please contact our support team.
Before installing NetApp Data ONTAP ETL for BMC TrueSight Capacity, you must ensure that the following prerequisites are met:
To monitor a NetApp storage system in 7-mode, you need to:
To create a user with read-only access to the DATA ONTAP API, copy-paste the following command lines into the NetApp CLI:
Create a new user in the previously created group:
Data ONTAP supports SSLv3 and TLS (disabled by default) to secure its connection with NetApp Data ONTAP ETL for TrueSight Capacity Optimization. From version 10.3 of BMC TrueSight CO, SSLv3 is disabled by default, which prevents NetApp Data ONTAP ETL for TrueSight Capacity Optimization to connect to Data ONTAP. To guarantee the correct operation of NetApp Data ONTAP ETL for TrueSight Capacity Optimization, you will have to first enable TLS. For more information, see .
To monitor a NetApp storage system in Cluster mode, you need to create a user with read-only access to the DATA ONTAP API. Please copy-paste the following command lines into the NetApp CLI:
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 NetApp Data ONTAP ETL module:
|Hostname||Hostname of the NetApp Filer in Cluster Mode or the IP address of the first controller in 7-Mode.|
Port number to connect to the NetApp Filer (Default: 443).
|Connect As||Username to connect to the NetApp Filer.|
Password to connect to the NetApp Filer.
|Partner Hostname||Partner hostname or IP address of the second controller of the NetApp Filer (7-mode only).|
Transport protocol used to connect to the NetApp Filer (for HTTP, the default port is 80; for HTTPS the default port is 443).
ETL additional settings
This property allows you to specify the terminology to be used for entity types. Select:
|Shares||This property allows you to fine-tune the creation of shares entities in the BMC 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 BMC 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 NetApp Data ONTAP API to collect information about NetApp Filers. 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 BMC TrueSight Capacity Optimization environment.
The following metrics are no longer collected and displayed in the console when volumes monitoring is disabled:
7-Mode and Cluster-Mode:
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.
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:
NetApp Data ONTAP ETL for TrueSight Capacity Optimization defines the following lookup fields:
|Entity Types (Storage - Vendor Agnostic)||Entity Types (NetApp Specific Terminology)||Lookup fields|
NetApp HA Pair