Veritas Cluster Server KM for PATROL

Release Notes for v2.4.00

Home  Previous  Next

What's New

Full integration with BMC ProactiveNet Performance Management
New parameter (VCSDaemonCPUUtilization) to monitor each daemon’s CPU usage
Ability to disable custom events from the KM
Debug mode: The time during which the debug information is logged can now be set by the user.

Changes and Improvements

<Component>Summary: Duplicate fields in summary text parameters are removed. Only the first entry is kept and all repetitions are ignored even when their values are different.
The KM performance has been improved to support large number Veritas Cluster Server components.
The delay required to perform a discovery following an Agent restart has been substantially reduced.

Fixed Issues

Incorrect management of date/time and elapsed time displayed by the KM for some timezones.
Due to a misinterpretation of the 'O' status, the DaemonState parameter was set to "Unknown" while the deamon was actually running.
Debug Mode ZIP output: On Windows 2008, the KM failed to create a ZIP archive with the content of the debug mode.
Monitoring Mode: When the Multi-node mode is activated, the KM will no longer prompt for PATROL account credential.
The VCS package (rpm) details processing has been modified to enable the KM to determine the VCS version number on Linux platforms during the initial discovery.
In version 2.3.00, the VCS version number could not be determined on Linux platforms during the initial discovery. As a result, failures were observed for the LLT & GAB commands and a warning was triggered on the VCSLoginStatus parameter.