Can you try "hastart -onenode" ?

If you have not configured LLT and GAB, then to start VCS you must use:

hastart -onenode

and "hastart" on its own without "-onenode" flag will not work with GAB.

This should work on bootup as the RC scripts have something like:

if [ "$gabconfigured" = "Configured" ]; then
    $HASTART
else
     $HASTART -onenode
fi

One additional thing to check is that you have "ONENODE=yes" inside the file /etc/sysconfig/vcs.

Mike

Thanks very much Tushar and mikebounds for your suggestions.

I tried 'hastart -onenode', but unfortunately 'had' is stiill not in the list of processes :

I wonder if the problem is license-related. I am using 60-day trialware which I originally downloaded and installed on the same machine back in Jan/Feb 2012. Shortly after that, I was tasked with something else, and I've only recently been reassigned to invesiigate VCS use in a one-node cluster. I did a fresh install of RHEL6 and of VCS 6.0.2, but perhaps the original installation is flagged as license expired based on the MAC address on my NIC?

Then again maybe I wouldn't have gotten that far with the install if there was a licensing issue?..

I don't think issue is licencing as this should show in engine log - something "VCS is not licensed" and with 6.0, it comes with its own 60 day eval, but even after 60 days, VCS will still work, you will just get warnings in the log.  You can verify if you have the built-in keyless 60 day eval by using:

vxkeyless -v display

Can you provide the following:

Output from command "gabconfig -a" (expecting it to say nothing)

Contents of main.cf (in /etc/VRTSvcs/conf/config)

Usually if "had" can't start it says in the engine log why it can't so it looks like "had" is just dying rather than exiting.

Mike