Veritas File System KM for PATROL

Release Notes for v2.1.00

Home  Previous  Next

What's new

Full compatibility with BMC ProactiveNet Central Monitoring Administration, a feature supported by BMC ProactiveNet Performance Management version 9.0.00.
Veritas File System KM for PATROL now supports Veritas Storage Foundation v6.x.
Monitoring Quick I/O: KM automatically discovers and monitors all Veritas Quick I/O files under all VxFS file systems. New application classes are added for monitoring Quick I/O and configuration menus are available for customizing this feature.
In order to easily identify which step the initial discovery is processing, the setup icon now reflects the successive phases:
Upgrading (PATROL Classic Console only)
Loading (Commands)
Initializing (KM paths. Missing path is now specified in the System Output Window)
Discovering (Monitored application)
Cleaning (Temp files)
Validating (Application paths)

Changes and Improvements

All collectors are now automatically refreshed as soon as the KM configuration and the initial discovery are complete.
The default number of instances of Application Classes has been removed. This information must be defined by the user if a maximum limitation is required. When set to 0, the monitoring of a specific Application Class is not performed.
Logs: The default log scan limit was increased to 500 KBytes. Also, The KM-related messages that are sent to the System Output Window (SOW) are also logged to the VFS.log file available under <PATROL_HOME>/log.
When one or more required paths are missing, the setup instance label will now indicate which paths are missing. A message will also be displayed in the System Output Window.
The VFSRemoveTempFiles parameter was removed.
All previous pconfig variables available under /VFS are now split to /VFS and /Runtime/VFS while upgrading the KM.
The KM Status report now provides collector/discovery collection time information as well as additional performance details.
The overall performance of the KM has been improved.
The KM failover time has been reduced to sooner discover VFS node status errors.

Fixed Issues

With some Windows platforms the Debug KM Command was prompting for an OS login to turn the debug on.
The KM now reports correctly on VFSFileSystemInodesUsedPercent and VFSFileSystemSpaceUsedPercent parameters.
I/O errors on mounted VxFS file systems are monitored through the VFSFilSystemMountState/Status parameter. A new state is added to VFSFileSystemMountState (4 = Mounted/Error), to report on such I/O errors on file systems.
When File Systems were created on volume sets, the I/O stats were only collected across individual volume. Therefore the I/O stats parameters for the VFS_FILESYSTEM application class were not set.