Important Information
The BMC patch 11.0.00.01: Patch 1 for BMC PATROL Agent 11.0.00 must be installed to use any version of BMC TrueSight Operations Management - Veritas Volume Manager Monitoring. Version 11.0.00i of the PATROL Agent on Windows prevents Veritas Volume Manager KM from operating properly. While apparently successfully loaded, Veritas Volume Manager KM fails to start and can neither monitor the local system or the remote systems.
|
What's New
| • | VVM-258: Support for Veritas InfoScale v7.x and higher. |
| • | VVM-271: Remote monitoring for all supported Veritas Volume Manager systems. |
| • | VVM-272: The monitoring of any additional log file can now be configured in TrueSight. The log filter can also be customized to indicate when Warnings and Alarms are triggered. |
Changes and Improvements
| • | VVM-241: Veritas Volume Manager KM has been improved to support all PATROL Agent v10+ versions and prevent failures due to a compatibility error. |
| • | VVM-271: The monitoring of Windows Event Logs has been significantly improved. |
| • | VVM-337: The path discovery has been improved in order to support variations to binary and library paths. |
Fixed Issues
| • | VVM-223: Handling large values in stats attributes: When the cumulative I/O stats returned by Veritas Volume Manager commands became too large (more than 231), the related attributes failed and stopped collecting data. Thus, metrics for rate-based attributes such as Read KBytes Rate, Write KBytes Rate, IO KBytes Rate were not properly reported for volumes, plexes, disks devices and subdisks. The product now stores the actual read, write or total I/O collected since the last collection cycle to avoid values reported by these attributes to grow cumulatively and to reach their limitation. |
| • | VVM-330: Veritas Volume Manager KM experienced a discovery failure due to a missing VxVM library path. |
Known Issues
| • | VVM-291: On BMC Portal v2.9, volumes (in disk groups) may not be collected by the Veritas Volume Manager KM integration par file. Also, due to hierarchical changes implemented in Veritas Volume Manager KM v3.0.00, migration from versions 2.x is not possible. |
|
