Deploying and Configuring IBM SVC-Storwize ETL 10.7.01 for TrueSight Capacity Optimization

This topic contains the following sections:

• • Compatibility details
  • Prerequisites
  • Deploying the ETL module
  • Configuring the ETL module
  • Post-configuration steps
  • Lookup details

Compatibility details

BMC TrueSight Capacity Optimization

BMC TrueSight Capacity Optimization v10.7.00 and later

IBM SVC-Storwize systems

IBM Hardware	Supported versions of the embedded CIM Agent
IBM SVC	7.2.0.14
IBM Storwize V7000	7.4.0.22

For more recent versions, please contact our support team.

Prerequisites

IBM SVC-Storwize ETL for TrueSight Capacity Optimization leverages the embedded SMI-S provider to collect capacity information about IBM SVC and Storwize storage systems.
The embedded SMI-S provider is automatically activated and the ETL accesses it via port 5989 (default). A user with security/Admin or administrator role is required.

Deploying the ETL module

Complete the following steps to deploy the ETL Module:

1. Navigate to Administration > SYSTEM > Maintenance.
2. Verify the installation status of the already uploaded packages. If their status is "READY" or "RUNNING", wait for the installation to complete before proceeding.
3. At the bottom of the Maintenance page, locate the Upload patch or additional package file section.
4. Click Browse.
5. Locate and select the ETL installation package.
6. Click Upload.
7. Read the Overview and click Next to continue.
8. Read and accept the End User License Agreement.
9. Select the server on which the operation must be executed; that is the server on which the package will be saved. Click Proceed to continue.

10. A successful installation will result in a green line in the Additional Packages table.

    Warning

    Note

     In case of unsuccessful outcome (e.g. a yellow WARNING line), click the  icon to inspect the deployment log.

Configuring the ETL module

Complete the following steps to configure an ETL service and add it as an ETL task to extract capacity and performance metrics:

1. Navigate to Administration > ETL & SYSTEM TASKS > ETL tasks.
2. In the ETL tasks page, under the Last run tab, click Add > Add ETL. The Add ETL page is displayed.
3. In the Run configuration tab, in the ETL module property, select Storage - IBM SVC-Storwize CIM Agent Extractor Service
   

1. 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 IBM SVC-Storwize ETL module: 

   • Basic
   • Advanced

   Warning

   Note

    Basic properties that are displayed by default in the Add ETL page are the most common properties that you can set for an ETL.

   Property	Description
   Connection settings
   Hostname	Hostname or IP address of the server where the IBM SVC-Storwize CIM Agent is running.
   Port	Port number used by the IBM SVC-Storwize CIM Agent (Default: 5989).
   Connect As	Username to connect to the IBM SVC-Storwize CIM Agent (Default: admin).
   Password	Password to connect to the IBM SVC-Storwize CIM Agent.
   Transport Protocol	Transport protocol used by the IBM SVC-Storwize CIM Agent (for HTTP, the default port is 5988; for HTTPS, the default port is 5989).
   ETL additional settings
   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 the section "Customizing Volumes Monitoring" below.

   Warning

   Note

   To view or configure Advanced properties, click Advanced. You do not need to set or modify these properties unless you want to change the way the ETL works. These properties are for advanced users and scenarios only.

   Property	Description
   Collection level
   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 [4] Extended. For more information about Aging Class Mapping, refer to the topic Adding and modifying metrics profile.

Post-configuration steps

• Testing the connection to the embedded SMI-S Provider
• Customizing volumes monitoring
• Running the Extractor Service task
• Setting the collect frequency

Testing the connection to the embedded SMI-S Provider

The ETL relies on the embedded SMI-S Provider to collect information about IBM SVC-Storwize 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:

1. Download the troubleshooting tool from EPD.
2. Run the command java –jar <Troubleshooting_Tool_Name.jar> to launch the tool.
3. Enter the information required to connect to the system and click Test Connection.
4. Wait for the test to complete.
5. If a connectivity issue is detected, an error message will appear. In this case, the issue encountered does not concern the ETL. Check your configuration to diagnose the source of the issue.
6. Click Save As to export the connection test results into a txt file.

Customizing volumes monitoring

Discovering volumes 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 monitoring at will and fine-tune the creation of volume 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:

Dataset	Metrics
STOGLB	ST_CONFIGURED_VOLUME_CAPACITY_PCT (Storage System Configured Capacity Percentage) ST_DEVICE_TOTAL (Device Space) ST_DEVICECOUNT (Storage Devices Number) ST_HOSTCNT (Attached Hosts Number) ST_POOL_DEV_COUNT (Pool Devices Count) ST_POOL_SUBSCRIBED_CAPACITY (Pool Subscribed Capacity) ST_POOL_SUBSCRIBED_CAPACITY_PCT (Pool Subscribed Capacity Percentage) ST_PRIMARY_ALLOCATED (Primary Allocated Usable Space) ST_SYSTEM_SUBSCRIBED_CAPACITY (Storage Subscribed Capacity) ST_VOLUME_CONSUMED_CAPACITY (Volume Consumed Capacity) ST_VOLUME_CONSUMED_CAPACITY_PCT (Volume Consumed Capacity Percentage) ST_VOLUME_HOST_VISIBLE_CAPACITY (Host Volume Visible Capacity) ST_VOLUME_IO_RATE (Volume Operation Rate) ST_VOLUME_MAPPED (Volume Mapped) ST_VOLUME_RESPONSE_TIME (Volume Response Time) ST_VOLUME_TIME_SINCE_LAST_ACTIVITY (Volume Time Since Last Activity) ST_VOLUME_TRANSFER_BYTE_RATE (Volume Transfer Byte Rate) ST_VOLUME_TYPE (Storage Volume Type)
STOHOST	BYHOST_ALLOCATED (Allocated Space by Host) BYHOST_SIZE (By Host Physical Size)

To customize volumes monitoring

1. Edit the ETL Run Configuration.
2. Expand the ETL additional settings menu.

3. From the Volumes pull-down lists, select one of the following options:

   Option	Result
   Disabled	Volumes are not discovered. Volumes-related metrics are not loaded in the console. Warning Note Use this configuration if the number of volumes to manage significantly slows down the system performance. Disabling the volumes 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)	All volumes are discovered and their metrics are collected and processed. Volumes-related metrics are not loaded in the console.   Warning Note Use this configuration if you wish to collect and process volume-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	All volumes are discovered and their metrics are collected and processed. Volumes-related metrics are saved in the database, processed and loaded in the console. Warning Note Use this configuration if your system is powerful enough to manage all the volumes to monitor.

4. Click Save.

Running the Extractor Service task

Click here to expand...

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:

1. Access the TrueSight Capacity Optimization Console.
2. In the Administration tab, select ETL & System Tasks > ETL Tasks.
3. Click  to execute the ETL task.

When the execution is complete, the value of the Status column in the ETL tasks table changes to SERVICE_ON.

Setting the collect frequency

Click here to expand...

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.

Warning

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:

1. Edit the ETL Run Configuration:
   1. In the Administration tab, click ETL & System Tasks > ETL tasks.
   2. Click the link of the ETL task for which you wish to set the collect frequency.
   3. Click the Stop button to stop the service execution; then click the  Edit button available in the Run configuration section.
2. Click the link You can manually edit ETL properties from this page provided at the bottom of the page to display a list of editable options.
3. Locate the service.period option, and enter the number of milliseconds corresponding to the frequency at which data will be collected. If you want the collect frequency to include both storage systems and storage pools for example, you will have to set the collect frequency to 7200000 milliseconds (2 hours).
4. Click Save.
5. Start the ETL.

Lookup details

IBM SVC-Storwize ETL for TrueSight Capacity Optimization defines the following lookup fields:

Entity type	Lookup fields
Storage System	DEFAULT
Storage Pool	DEFAULT
Storage Volume	DEFAULT