It has come to a decision now to making the OS standalone for now as there is *not* much time to troubleshoot / correct the cluster configuration. Even removing the cluster fileset is not acceptable. Looking at the cluster resources and verify logs, which seemed to be running every midnight, it looks healthy (though I can't really say much as I have never seen the resource group working). All the while its a cluster without a substance having clcomd running and RG (meaning VG, FS mounted normally, apps started manually) and downtime not as generous. As much as possible, I want the cluster to be taken out completely if that will be the direction but even so, they can only give me a 5 minute window for a reboot.

My question lives wherein will below suffice in taking out the cluster service and no "dead man switch" or that can take over the system and have it just crash:

1.) Comment out / Take out cluster startups (harc.net, telinit, clcomd) from inittab
2.) Set the VGs to be varied on upon boot, filesystem be mounted automatically
3.) Putting the service IP as alias to one interface
4.) Reboot machine

Maybe until they can migrate to a new box with a more intensive tests done before rolling it out and see to it that failover testing needs to be done if need be and of course resource group failing over the way it should be. It may sound like a irresponsible move now but the uptime is more important as of this 5.2 setup. They *think* its a risk even starting the cluster thus a decision to making it standalone as that it functions currently all manual. Thanks.