The ETL relies on the Unity SMI-S Agent to collect information about Dell EMC Unity 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:
The ETL relies on the Unity SMI-S Agent to collect information about Dell EMC Unity 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:
- Download the troubleshooting tool from EPD.
- Run the command java –jar <Troubleshooting_Tool_Name.jar> to launch the tool.
- Enter the information required to connect to the system and click Test Connection.
- Wait for the test to complete.
- 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.
- Click Save As to export the connection test results into a txt file.
Customizing volumes and shares monitoring
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 Helix Continuous Optimization environment.
The following metrics are no longer collected and displayed in the console when volumes monitoring is disabled:
| Dataset | Metrics |
|---|---|
| STOGLB |
|
The following metrics are no longer collected and displayed in the console when shares monitoring is disabled:
| Dataset | Metrics |
|---|---|
| STOGLB |
|
To customize volumes and shares monitoring
- Edit the Dell EMC Unity CIM Server ETL Run Configuration.
- Expand the ETL additional settings menu.
From the Shares/Volumes pull-down lists, select one of the following options:
| Option | Result |
|---|---|
| Disabled |
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. |
Click Save.
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:
- Access the Helix Continuous Optimization console.
- In the Administration tab, select ETL & System Tasks > ETL Tasks.
- 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.
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:
- Edit the ETL Run Configuration:
- In the Administration tab, click ETL & System Tasks > ETL tasks.
- Click the link of the ETL task for which you wish to set the collect frequency.
- Click the Stop button to stop the service execution; then click the
Edit button available in the Run configuration section.
- 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.
- 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).
- Click Save.
- Start the ETL.
