The error show above may occur if the following conditions are present:
- All nodes in the cluster go down and one or more nodes does not come online in the cluster.
- Veritas Cluster High Availability Engine(Had.exe) hangs in a "Starting" state.
- Cluster not starting.
- HAD can't start on node.
1. Check the Services Control Panel to see if "Veritas High Availability Engine Startup" service is in the "Starting" state.
2. Check the HAD error message in the Application Event Viewer to see if "HAD error returns an message: Did not receive cluster membership, manual intervention may be needed for seeding"(Figure 1).
3. Use the following command to determine the status of the cluster:
C:\>hastatus -sum or
Figure 1 - Command Prompt and Application Event Viewer.
By default, 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 that must be available before HAD will start is defined in gabtab.txt. The file is located under the following path:
Note: 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.
If the "Veritas High Availability Engine Startup" service is in the "Starting" state, the following command can be used to manually seed GAB.
From the Command Line, type:
C:\>gabconfig -c -x
If the configuration file is valid, the node should transition from LOCAL_BUILD to RUNNING.