Release Notes

This page lists the new features, improvements, changes and bug fixes in each version of Veritas Cluster Server KM.

1 Changes - Released 2022-11-10

ID	Description
VCS-512	Security vulnerability in Swagger UI (OpenAPI) when displaying the documentation through Monitoring Studio

9 Changes - Released 2022-08-04

ID	Description
VCS-504	Web UI & CMA: Added an option to enable Veritas Volume Manager & File System monitoring
VCS-502	Improved log monitoring
VCS-493	Added Windows event log monitoring for VCS errors
VCS-492	Daemon monitoring is activated on passive nodes in multi-node monitoring mode
VCS-490	Integration with the Monitoring Studio X console
VCS-485	Sudo privileges are no longer required for KM shell scripts
VCS-480	Automatic command reload when the OS check command fails

ID	Description
VCS-500	The high number of KPI parameters impacts the overall performance of TSOM/BHOM
VCS-482	Failing to use Remote Temp Directory Path

8 Changes - Released 2018-01-24

ID	Description
VCS-396	Ability to Configure Logs & Filters from CMA
VCS-381	InfoScale Enterprise v7.x Support
VCS-378	Support for Remote Monitoring

ID	Description
VCS-454	CLONE - Default Binary & Library Path Settings
VCS-441	CMA Log Description Not Set
VCS-434	Event logs can't be added in classic mode for monitoring
VCS-371	CLONE - Log Scan Limit Cannot be Set Through CMA
VCS-362	Upgrading to v10.x of Patrol Agent blocks the KM from functioning properly.

2 Changes - Released 2016-05-12

ID	Description
VCS-321	Unwanted LLT and GAB instances on the console
VCS-315	The current method to determine if VCS is in CMA mode is not correctly working.

16 Changes - Released 2015-09-09

ID	Description
VCS-201	Annotation on VCSResourceFailoverStatus to Reflect Current Status
VCS-171	Ability to filter monitored instances by regular expressions

ID	Description
VCS-255	KMF v2.1.04, v2.1.05 & v2.1.06 Related
VCS-244	Long KM failover while VCSMonitoringMode swaps values
VCS-243	VCSLoginStatus in warning for CHECK_MODE
VCS-230	VVM references in VCS Guide (Doc Only)
VCS-224	Sudo error: you must have a tty to run sudo (Doc only)
VCS-218	Sporadic discovery cycles setting Server parameter datapoints interval unequal
VCS-217	PATH missing in sudo configuration making KM failing to find VCS commands (Doc Only)
VCS-211	VCSGroupFailoverStatus triggering false warning
VCS-191	VCSGabState does not set to the correct Jeopardy state
VCS-185	Poor KM performance on Linux
VCS-173	Missing Path: Library Path
VCS-166	Patrol Agent crashes on Patrol Agent v9.0.20i
VCS-150	WAN heartbeat status is not set on Windows managed nodes
VCS-143	KMF v2.1.03 Related

14 Changes - Released 2013-01-24

ID	Description
VCS-105	Ability to monitor cluster system load - VCSSystemLoadWarnDuration
VCS-91	KMF v2.1.02 Related
VCS-74	New parameters VCSResourceState/VCSResourceStatus
VCS-73	GAB discovery to alert through port status when a required port is not found
VCS-63	Monitor syntax errors in main.cf
VCS-56	Monitor AutoDisabled state for resource groups
VCS-51	Support for Veritas Global Clusters
VCS-28	KMF v2.1.01 related
VCS-19	KMF v2.1.00 related
VCS-14	VCS 6.0 Compatibility

ID	Description
VCS-102	VCSGSystemState in unknown state
VCS-64	VCSSystemFrozenState is not set to TFrozen
VCS-41	hagrp command on Linux not returing all systems in the cluster.
VCS-40	Patrol Agent version 3.8.50 with VCS KM version 2.4.00 on 64-bit Win2008 is crashing.

4 Changes - Released 2012-07-31

ID	Description
VCS-11	CLONE - Product support InfoBox items in the main container and service release
VCS-10	CLONE - New parameter (VCSDaemonCPUUtilization) for monitoring daemon CPU utilization
VCS-8	BPPM Ready

ID	Description
VCS-12	KM is failing to find the VCS version number, leading to command reload every discovery cycle and failing LLT and GAB monitoring

Search Results for {{siteSearch | truncate:'50'}}

No results.