VCS CRITICAL "v-16-1-51135 GlobalCounter not updated" appears repeatedly in Veritas Cluster Server (VCS) engine log and Windows application event log.
Article ID: 100008355
Updated On:
Description
Error Message
VCS CRITICAL V-16-1-51135 GlobalCounter not updated
Cause
After every 49.7 days, VCS logs report that the Global Counter VCS attribute is not updated. This error is reported on all nodes in the cluster, except the node with the lowest node ID value. The 'GloablCounter not updated' error also appears in the Event Viewer.
Resolution
This issue has been fixed and the error is no longer reported at that odd interval.
Fixed on SFWHA6.0 CP5, refer to https://sort.Veritas.com/patch/detail/7627
Fixed on SFW/HA 6.0.1 CP1,refer to https://sort.Veritas.com/patch/detail/7841
Fixed on SFWHA6.0 CP5, refer to https://sort.Veritas.com/patch/detail/7627
Fixed on SFW/HA 6.0.1 CP1,refer to https://sort.Veritas.com/patch/detail/7841
Applies To
Veritas Cluster Server (VCS) 6.0
Veritas Cluster Server (VCS) 6.0.1
Storage Foundation High Availablity (SFW HA) 6.0
Storage Foundation High Availablity (SFW HA) 6.0.1
Issue/Introduction
VCS CRITICAL "v-16-1-51135 GlobalCounter not updated" appears repeatedly in Veritas Cluster Server (VCS) engine log and Windows application event log.
The error indicates that there could be communication issue between the cluster nodes. However, this error is incorrectly reported, and no communication issue actually occurs.
The error indicates that there could be communication issue between the cluster nodes. However, this error is incorrectly reported, and no communication issue actually occurs.
Was this article helpful?
Yes
No
Powered by
