What's New
| • | The product now integrates Hardware Monitoring (battery, fans, Ethernet ports, power supplies). Loading Hardware Sentry KM is no longer required to monitor basic component health. |
| • | BMC Performance Manager Express for EMC Disk Arrays now supports EMC Celerra storage systems (Support of both SAN and NAS). |
| • | Ports on CLARiiON and VNX systems are now fully monitored. |
| • | The product now provides support for WQL query in WBEM client based on SBLIM method. |
| • | The product now supports the monitoring of FC and Ethernet ports traffic on EMC CLARiiON and VNX series. |
| • | Support of dynamic tiering configurations (FAST VP policies in EMC Symmetrix VMAX). |
| • | Disable Volumes Monitoring: This new option enables users to disable the monitoring of all volumes. |
| • | Volume Application Class: The storage pool to which the volume is associated is now available through the Storage Pool parameter |
| • | The product now reports on Symmetrix controllers' Cache Hit Ratio to provide the percentage of requests that are successfully served by a cache. |
| • | Controllers' Fiber ports are now regrouped under Fiber Ports container. |
| • | The Port Count parameter has been added to the Disk Array application class to report on the number of ports available in the storage system. |
| • | The FQDN parameter has been added to the Disk Array application class to provide the fully qualified domain name of the storage system, as exposed to BPPM. |
| • | The product now reports on the following new parameters for the Controller, Volume and Disk Arrayapplication classes: |
|
|
|
Read Operation Rate
|
Number of read operations per second.
|
Write Operation Rate
|
Number of write operations per second.
|
Operation Rate
|
Total number of operations per second.
|
Changes and Improvements
| • | Device IDs have been improved to provide more meaningful information to BMC Performance Manager Express for EMC Disk Arrays users. Consequently, parameters history will be lost when upgrading to version 2.1.00. |
| • | The "Array" and "FC Port" application classes were respectively renamed "Disk Array" and "Fiber Port" |
| • | The threshold value for the Oversubscription Situation parameter has been changed from 100 % to 75 %. |
| • | The method used by the product to calculate the disk size has been improved to provide a more exact and accurate information. |
| • | The method used to retrieve the volume type, which is displayed between brackets next to the volume name, has been modified to provide more precise information. Possible values for the volume type are: Traditional, VAULT, SFS, DATA, SAVE, Virtual, Thin. |
| • | Back End Fiber Ports are no longer discovered: the collected information from the Back End Fiber Ports were not representative of the real data traffic of the disk array. |
| • | The Speed parameter of the FC Port application class now displays when the speed value is equal to 0 corresponding to a disabled port. |
| • | The error message displayed in debug files when querying an SMI-S provider that doesn't support the EMC namespace has been improved to be more explicit. |
| • | The Storage Pool parameter of the Physical Disk application class now shows the associated storage pool instance name instead of the Pool ID. |
| • | Depending on the information available, the Storage Group parameter of the Volume application class displays either the World Wide Name or the host name. |
| • | In order to report more accurately on the actual available capacity of a disk array, the calculation method used to determine the Available Capacity parameter of the Array application class has been modified. The Available Capacity parameter now reflects the capacity available in storage pools plus the total space available for storage pool creation. |
| • | The Available Capacity for Symmetrix Storage Systems now includes the Available Capacity in Thin Pools. |
| • | The mechanism that handles the parsing of WBEM queries has been improved to reduce the consumption of CPU and memory resources. |
| • | FC port discovery: The time required to discover FC ports has been reduced. |
Fixed Issues
| • | The number of disks in an array is now computed according to the number of physical disks created under this same array. |
| • | The Oversubscription Situation parameter was erroneously computed. |
| • | Read Bytes and Write Bytes parameters for Array, Controller, Physical Disk, and Volume application classes were not properly displayed in the accumulated parameter-type reports. |
| • | For some performance parameters, a missing value was interpreted as zero instead of No Data. |
| • | The value of the Operation Rate parameter is now null when the total number of operations per second performed by the system cannot be computed. |
| • | 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. |
| • | The Time Since Last Activity parameter of the Volume class now displays a "0" value when no data is available. |
| • | Storage pools without volumes now display a "0" value instead of "no data" for the following parameters: |
| ▪ | Consumed Capacity (and Consumed Capacity Percentage) |
| ▪ | Subscribed Capacity (and Subscribed Capacity Percentage) |
| ▪ | Available Capacity (and Available Capacity Percentage) |
| • | A display issue (blank spaces and carriage returns) occurred in Portal's string values. |
| • | When a storage system had a null or empty instance name, the storage system was not displayed in the Portal console and the Application Collection Status parameter reported the issue with the following error message: The instance name of a discovered instance may not be null or theempty string.:SEN_EMC_SMISPROVIDER_MANAGEDARRAY. From now on, storage systems will always indicate an instance name to avoid this issue. |
Known Limitations
| • | When migrating to version 2.1.00, parameters history will be lost and FC Ports will not be available. We therefore recommend uninstalling any previous version of the PM before uploading and installing v2.1.00. |
|
