V-16-1-51135: GlobalCounter not updated
Article ID: 100047062
Updated On:
Description
Error Message
VCS CRITICAL V-16-1-51135 GlobalCounter not updated
Cause
Veritas Cluster Server (VCS) reports this error message in the engine log. It is a self-check message to determine if there are any delays due to a Global Atomic Broadcast (GAB) broadcast. You may also see this message if the high availability daemon (HAD) is busy and cannot update the GlobalCounter in the specified time.
Resolution
Please check the following :
1. Load on the system i.e. memory, CPU, Disk space etc.
2. Network issues and connectivity, Check the network for delays and packet drop, which may affect GAB broadcast.
3. If still issue persists then reboot nodes.
Issue/Introduction
In VCS Cluster one of the node is not able to start had or port h and logs reports as "
VCS CRITICAL V-16-1-51135 GlobalCounter not updated"
Was this article helpful?
Yes
No
Powered by
