Wednesday, March 29, 2006

VCS Stuff (What to do after a crash)

If you've had a Veritas Cluster Server node crash and see this:

VCS CRITICAL V-16-1-11306 Did not receive cluster membership,
manual intervention may be needed for seeding

Try this:

# gabconfig -x

This will re-seed the control port, and should bring the box back up
into the cluster. Check your logs: /var/VRTSvcs/log, and don't forget
engine_A.log.

Reference:
Solaris VCS 4.0 User Guide: http://seer.support.veritas.com/docs/266481.htm
Soalris VCS 4.0 Install Guide: http://seer.support.veritas.com/docs/265394.htm

5 comments:

Anonymous said...

Thanks. This worked perfect ....

Anonymous said...

Thanks for this post. after like 10 hours of pointless searching / reading / testing i found your post via the v-16-1-11306 error. I didnt figure the GAB seeding bit by myself and you just saved my evening.

Anonymous said...

Thanks for this valuable post.

Anonymous said...

Thanks for the valuable comment

utsavagarwal said...

Thanks. Worked great. Wish I had seen this post an hour earlier.
Also related to VCS ERROR V-16-1-1005 CVMCluster:???:monitor:node - state: out of cluster