|
 This user documentation was written for BMC Capacity Optimization v9.5.00. The procedures described may therefore slightly differ if you are using BMC Capacity Optimization v9.0.03.
What's New
| • | EMC SMI-S Agent ETL for BMC Capacity Optimization now supports BMC Capacity Optimization v9.5. |
| • | Host mapping information is now available for the EMC platforms through the STOHOST dataset. The information can be visualized in the Storage Capacity view and from the Workspace, under the Volume entity. |
| • | Support of dynamic tiering configurations (FAST VP policies in EMC Symmetrix VMAX). |
| • | The VOLUME_EXTERNAL_ID metric was added to the STOGLB dataset to provide the Volume's Network Address Authority (NAA) identifier, when available. |
Changes and Improvements
| • | EMC SMI-S Agent Extractor Service Log: The service log now indicates the number of connections opened to the BCO data warehouse. Additional information about the connection, and more particularly whether the thread is opened or released, is available in the connector saver logs. |
| • | FC port discovery: The time required to discover FC ports has been reduced. |
STOGLB Dataset Performance Metrics
| • | The following metrics of the STOGLB dataset have been renamed in BMC Capacity Optimization v9.5: |
|
|
|
ST_AVAILABLE_CAPACITY
|
ST_FREE
|
ST_CAPACITY
|
ST_CONFIG_SUM
|
ST_CONFIG_SIZE
|
ST_CONFIG_SUM_RAW
|
ST_ACC_USED
|
ST_CONFIG_SIZE
|
ST_CONSUMED_CAPACITY
|
ST_ACC_USED
ST_USED
|
ST_CONSUMED_CAPACITY_PCT
|
ST_USED_PCT
|
ST_OVERSUBSCRIBED_CAPACITY
|
ST_POOL_OVERSUBSCRIBED_TOTAL
|
ST_POOL_RAID_LEVEL
|
ST_POOL_PROTECTION_LEVEL
|
ST_POOL_SUBSCRIBED_CAPACITY
|
ST_THINPOOL_SUBSCRIBED_TOTAL
|
ST_SIZE
|
ST_RAW
|
ST_SYSTEM_MODEL
|
ST_MODEL
|
ST_SYSTEM_PORT_NUM
|
ST_PORT_COUNT
|
ST_SYSTEM_SUBSCRIBED_CAPACITY
|
ST_ACCESSIBLE
|
ST_SYSTEM_VENDOR
|
ST_VENDOR
|
ST_VOLUME_CONSUMED_CAPACITY
|
ST_VOLUME_USED
|
 Please note that the values collected under the former metric names will be automatically transferred under the new metric name.
Fixed Issues
| • | The error BCO_SCH_ERR015 would be displayed when an internal connection management problem occurred. The ETL now handles the connection to the data warehouse properly. |
| • | A problem related to disk identification prevented the ETL to accurately match disks with their related storage systems. This issue mainly occurred when one SMI-S provider was used for storage systems from the same vendor. |
| • | The Consumed Capacity and Consumed Capacity Percentage of the volumes were incorrectly reported when FAST VP Policies were enabled. In such a configuration, the connector only took into account the first storage pool instead of all the storage pools to which the volume belonged. |
Known Limitation
| • | The capacity of FAST VP volumes (dynamic tiering) is reported as fully subscribed in each of the underlying storage pools. If, for example, a 1TB volume consumes 100GB of an SSD pool and 500GB of a SATA pool, both pools will be considered as subscribed for 1TB. While not false, this will cause the subscription of a pool and of the entire storage system to be greater than what has been actually subscribed by the hosts.
|
|
