What's New
| • | Veritas Volume Manager KM for PATROL now supports Windows 2012. |
Fixed Issues
| • | VVM-129: The value of the VVMVolumeStateNT parameter was sometimes improperly set to Degraded (=5) instead of Active (=0) on Windows systems; which caused a false alarm to be triggered by the VVMVolumeStatus parameter. |
| • | VVM-136: The value of the VVMRLinkKernelState parameter was sometimes improperly set to Enabled (=1) instead of Connect (= 0) on Windows systems; which caused a false alarm to be triggered by the VVMRLinkKernelStatus parameter. |
| • | VVM-143: The KM did not properly interpret the output of the iostat command used to collect statistics from deported volumes on Windows. This resulted in a false alarm to be triggered by the VVMLoginStatus parameter. |
| • | VVM-153: A false alarm was triggered by the VVMDiskdeviceStatus parameter when monitoring a Storage Foundation 5x system running on Windows. |
| • | VVM-159: The Microsoft Cluster active node was not properly detected when the KM was operating in multi-node monitoring mode. |
| • | VVM-174: The Sudo configuration requirements have been updated in the Security Requirements chapter of the user documentation. |
| • | VVM-180: When SRL Overflow Protection was set to "DCM" or "AutoDCM", the KM did not trigger an alert when DCM logging was activated. A new state has been added to the VVMRLinkKernelState of the VVM_RLINK application class, DCM Logging (2), which by default triggers an alarm through VVMRLinkKernelStatus. |
| • | VVM-188: The status report file of Veritas Volume Manager KM for PATROL is now suffixed with the Agent port number to avoid overwriting it when multiple virtual Agents are used. |
| • | VVM-189: Invalid alarms were triggered on the VCSLoginStatus parameter when the KM was unable to check the active node. |
| • | VVM-190: The main discovery cycle was irregular due to an asynchronous default KM discovery interval. It is now reduced to 30 seconds to avoid such irregularity. |
| • | VVM-191: On Windows systems, if the PATROL Agent installation path contained spaces, scripts calls and output redirection commands failed. |
|
