Receiving Error When Connecting to VCS Cluster Explorer Java Console

Problem

Receiving Error When Connecting to VCS Cluster Explorer Java Console

Solution

"V-16-10-4: Could not connect to a live system in the cluster %CLUSTERNAME%" 14141. Closing all windows" appears in Veritas Storage Foundation HA for Windows This error may occur if the following conditions are present:

• The "Veritas High Availability Engine" (HAD) service is not started.
• The cluster is in a STALE_ADMIN_WAIT condition.
• The cluster is in an ADMIN_WAIT condition.

1. Use the following command to determine the status of the cluster:
 

hasys -state

 2. If status of this node is listed as "OFFLINE," HAD may be started by typing the following command:

hastart

If any of the node are unavailable, HAD may not start. The minimum number of nodes that must be available before HAD will start is defined in gabconfig.txt . By default, this file is located under the following path:

c:\Program Files\VERITAS\comms\gab\gabconfig.txt

This file contains a line that defines the "seeding" requirement: the number of nodes for this cluster that must be available before HAD will start.

For example:

gabconfig -c -n 2

In the example shown above, two nodes must be present before HAD can start.

If needed, the following command can be used to temporarily override the seeding requirements:

gabconfig -c -x
 
 
3. If the status of this node is listed as "STALE_ADMIN_WAIT," review 000025064, linked in the Related Articles section below.
 
4. If the status of this node is listed as "ADMIN_WAIT," review 000027610, linked in the Related Articles section below.