Hitachi Device Manager ETL for BMC TrueSight Capacity Optimization

Release Notes for v6.0.00

Home  Previous  Next

Changes and Improvements

Volumes IDs were not consistent in version 5.0.00 and had therefore been changed in this new version. IMPORTANT: Volumes history will be lost when migrating from version 5.0.00 to 6.0.00.
Query results now temporarily persist in a file stored in the localdb directory when the scheduler's heap memory is going to run out of memory.
Log files can be downloaded from the BMC TrueSight Capacity Optimization console.
The discovery log is now available as a separate file.
The Log message "Class xxx ignored in file" was improved to indicate why entities have been ignored.
New Computation Methods:
The Storage Capacity metric (ST_CAPACITY) is now the sum of the storage pools capacity that is allocated from a primordial pool, of the remaining capacity in the primordial pool, and of the capacity of the external primordial pools.
The Consumed Capacity metric (ST_CONSUMED_CAPACITY) is now the difference between the Storage Pool Capacity (ST_CAPACITY)  and the Storage Pool Available Capacity (ST_AVAILABLE_CAPACITY).
The capacity of all imported primordial storage pools is now used for calculating the size of the array (ST_SIZE).
The Available Capacity in Storage Pools (ST_AVAILABLE_IN_STORAGE_POOLS) metric is now the sum of the available capacity of all pools. For VSP storage systems, only Dynamic Pools are considered.

Fixed Issues

Log files were not properly deleted on log rotation.
The value of the Pool Devices Count metric (ST_POOL_DEV_COUNT) metric was not correct.
Negative values were sometimes reported for the following metrics: System Transfer Byte Rate (ST_SYSTEM_TRANSFER_BYTE_RATE), Volume Transfer Byte Rate (ST_VOLUME_TRANSFER_BYTE_RATE), Transfer Rate by Controller (BYCONT_TRANSFER_RATE), and Input/Output Traffic Rate for the Port (BYPORT_BYTE_RATE) .
An exception occurred when the array status was not available.