1. Support
  2. Knowledge base
  3. 100001133

VCS ERROR V-16-1-10600 Cannot connect to VCS engine reported for Veritas Cluster Server for Windows

Article: 100001133
Last Published: 2013-08-14
Ratings: 1 3
Product(s): InfoScale & Storage Foundation

Problem

For a Veritas Cluster Server (VCS) on Windows platform, there may be instances when trying to start the "Veritas High Availability Daemon (HAD)" service, it would fail to start or get stuck in "Starting" phase

 

Error Message

Upon running the command "hasys -state" would report below error

VCS ERROR V-16-1-10600 Cannot connect to VCS engine

 

Cause

The error may occur for any cluster if all or one or more nodes fail to come online, preventing the cluster from achieving valid cluster membership.

 

Solution

1. Check the Services Control Panel to see if "Veritas High Availability Engine Startup" service is in the "Starting" state.
2. Check Application Event Viewer for event ID 11306 or Event with message as  "Did not receive cluster membership, manual intervention may be needed for seeding"  
 
 
3. Use the following command to determine the status of the cluster:
C:\> hastatus -sum or
C:\> hasys -state
 
By default, the Global Atomic Broadcast (GAB) is configured to seed the cluster after all nodes in the cluster have joined the cluster. If all nodes go down for any reason and one node does not come online, the cluster will not start.
 
The minimum number of nodes required to allow HAD to be started is defined in gabtab.txt. The file is located under the following path:  \Program Files\VERITAS\comms\gab\gabtab.txt
 
Note: This file contains a line that defines the "seeding" requirement, which is the number of nodes for this cluster that must be available before HAD will start.
 
If the "Veritas High Availability Engine Startup" service is in the "Starting" state, the following command can be used to manually seed GAB after killing the had.exe from the Tasks list. 
 
From the Command Line, type:
C:\> gabconfig -c -x
C:\> hastart
C:\> hasys -state
 
If the configuration file is valid, the node should transition from LOCAL_BUILD to RUNNING.
 
 
 

 

Was this content helpful?

Article Languages