Release Notes

New supported platform

The ETL now supports EMC Celerra 8.1.0.

Troubleshooting tool

A troubleshooting tool is now available to test the connection to the EMC SMI-S provider.

WBEM results persistence

The mechanism used for WBEM results temporary persistence has been improved.

New supported platform

The ETL now supports Hitachi VSP Gxxxx Series.

Troubleshooting tool

A troubleshooting tool is now available to test the connection to the Hitachi Device Manager.

Performance

The ST_SIZE metric computation algorithm has been improved to reduce workload.

WBEM results persistence

The mechanism used for WBEM results temporary persistence has been improved.

Troubleshooting tool

A troubleshooting tool is now available to test the connection to the HP 3PAR SMI-S provider.

WBEM results persistence

The mechanism used for WBEM results temporary persistence has been improved.

New ETL

This new ETL was developed for BMC TrueSight Capacity Optimization v10.5 to collect capacity information about IBM SVC and IBM Storwize systems.

Troubleshooting tool

A troubleshooting tool is now available to test the connection to the IBM XiV Management Module.

WBEM results persistence

The mechanism used for WBEM results temporary persistence has been improved.

Troubleshooting tool

A troubleshooting tool is now available to test the connection to the NetApp Data ONTAP API.

NetApp Data ONTAP Mode selection

The ETL automatically determines the NetApp Data ONTAP Mode (7-Mode or Cluster-Mode).

Metrics

The BYDISK_TYPE metric is now available for Disks/Cluster Disks.

NetApp capability

The api-snapshot-volume-info capability is required to collect the ST_VOLUME_SNAPSHOT_RESERVE_USED and ST_VOLUME_SNAPSHOT_RESERVE_USED_PCT metrics.

Supported Platforms

Storage Capacity Views and Reports for BMC TrueSight Capacity Optimization supports IBM SVC-Storwize.

Reports

Storage Capacity Views and Reports for BMC TrueSight Capacity Optimization comes with basic reports templates (Storage Allocation, Storage Pool Overview, and Storage Systems Overview).

Storage pools

Storage pools with a capacity of zero are now considered as not available (dash ‘-’ value) instead of ‘Saturated’.

Saturation and oversubscription risks

The computation method for the Saturation Risk and Oversubscription Risk has been improved. It is now based on the consumed capacity observed for the last 30 days.

Columns

• The Updated column is now available for Controllers, Ports, and Disks.
• To avoid confusion with the Oversubscription Risk column, color code was removed from the Storage Consumed Capacity Percentage column.

Relations

The relations between Storage Volume and Storage Pool are now properly discovered.

Connection failures

Connection failed when the hostname contained a white space.

Error messages

When some information about the connection was missing, an improper error message was logged preventing the real cause to be identified.

Data gap

The data gap that occurred after the discovery for the Disk Utilization Percentage (BYDISK_UTIL) and the Disk Response Time (BYDISK_RESPONSE_TIME) metrics (CLARiiON and VNX physical disks only) has been fixed. Metrics are now properly collected.

Relations

The relations between Storage Volume and Storage Pool are now properly discovered.

Connection failures

Connection failed when the hostname contained a white space.

Error messages

When some information about the connection was missing, an improper error message was logged preventing the real cause to be identified.

Errors

Authentication and authorization errors are better handled by the ETL.

Computation methods

The computation methods for the ST_CAPACITY, ST_AVAILABLE_FOR_STORAGE_POOLS, ST_AVAILABLE_CAPACITY, ST_OVERSUBSCRIBED_CAPACITY, and ST_CONSUMED_CAPACITY_PCT metrics have been fixed.

Connection failures

Connection failed when the hostname contained a white space.

Error messages

When some information about the connection was missing, an improper error message was logged preventing the real cause to be identified.

Errors

The CIM_ERR_FAILED error is now better handled by the ETL to prevent collection from being aborted.

Connection failures

Connection failed when the hostname contained a white space.

Error messages

When some information about the connection was missing, an improper error message was logged preventing the real cause to be identified.

Invalid values

The subscribed capacity of the storage pools could temporarily be incorrect when the ETL could not have collected the ST_VOLUME_MAPPED metric required for computation.

Connection failures

Connection failed when the hostname contained a white space.

Error messages

When some information about the connection was missing, an improper error message was logged preventing the real cause to be identified.

Connection failures

Connection failed when the hostname contained a white space.

Error messages

When some information about the connection was missing, an improper error message was logged preventing the real cause to be identified.

Error messages

When users did not have the rights required to request the NetApp API, an improper error message was logged preventing the real cause to be identified.

Collected values

The values of the metrics ST_VOLUME_CONSUMED_CAPACITY, ST_VOLUME_CONSUMED_CAPACITY_PCT, ST_CONSUMED_CAPACITY (Array only), and ST_CONSUMED_CAPACITY_PCT (Array only)  are not accurate for Hitachi VSP Gxxxx Series storage systems due to a bug identified on the Hitachi API. This issue should be fixed in SVOS 6.4.0 microcode (83-03-00+) to be released by Hitachi in February 2016.

Collect issues

Collect issues may occur if Hitachi VSP Gxxxx Series storage systems have been previously attached to a different SMI-S provider for other purposes such as provisioning. To solve this collect issue, you will have to upgrade your version of Hitachi Device Manager to version 8.2.0.-03.