Error Code details
Severity: Critical 
Component: Cluster Server 
Did not receive cluster membership, manual intervention may be needed for seeding

The message appears if Veritas Cluster Server (VCS) starts but cannot receive the cluster membership from Global Atomic Broadcast (GAB). VCS requires GAB to deliver the cluster membership when it starts. If GAB is not configured or seeded, VCS cannot function due to lack of the status info of other nodes in the cluster. The mechanism prevents multiple nodes from starting their own clusters without knowledge of each other and starting service groups in an incoherent manner, which jeopardizes the data integrity.


Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2012-05-17 06:45:38 PDT
Platform: Red Hat Enterprise Linux 3 (x86-32)
Release: 4.0MP3


To resolve this issue:

  1. Make sure that GAB is configured and seeded. On the node where you see this message, run the following command:

    /sbin/gabconfig -a

    The output should show the current node in GAB membership. If it does not, configure GAB by:

    /sbin/gabconfig -c
  2. Verify the network (private interconnects) configuration and cluster ID in the /etc/llttab file.
  3. If the cluster membership cannot be formed because some node(s) is in an unrecoverable state and cannot join the cluster, you can manually seed GAB on the node where you see the message. Note that the action can only be performed once on only one node in the entire cluster. Run the following command:

# gabconfig –x

Caution: It is the only case in which manual seeding can be applied; otherwise, it can lead to potential split brain scenario.


User solutions
No user solutions yet.


Read and accept Terms of Service