Problems with two node redhat cluster with quorum disk.

I'm building a RHEL 5.5 cluster with 2 nodes and a quorum disk. When I reboot both the nodes in the cluster at the same time, clustat shows both the nodes online and the quorum disk. When I disable one node, it fences the node and reboots. The problem is, this node is not able to quorate to the cluster and never joins back to the cluster. Hence the cluster is left with one node and the quorum disk and the node which was rebooted thinks it is online (split-brain).

Following is how my cluster.conf looks like. Any comments/suggestions will be helpful :)

Other than the storage fencing, don't you also have an IP based fencing?
Can you post the cluster config?
You need to fence based on all the shared resources.
IP,
http://sources.redhat.com/cluster/wiki/FAQ/Fencing

Quorum is a shared SAN space between these two nodes and I do have fencedevices and fence method, but I've not included it here. It shouldnt make any difference in deciding this, but I can include it if required.

Are you using iscsi to access the storage or do you have FC connection to the drives?
When both nodes are up, can both nodes access the data on the shared drive?
Which fencingmethod and fencing device are you using?
A complete cluster.conf would be helpful.

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

One other thing, make sure that both nodes have an identical copy of the cluster.conf file.
Each node may have itself listed as active and you have post_fail_delay="0" which I think may lead to both trying to comeup as active nodes.

Any error message in /var/log/messages on either node. You should also not reboot both at the same time. power off one, then reboot the other which should configure itself as the active one. Then power up the second node which should then run and attempt to rejoin the cluster. Double check that the IP resource is configured.

"Are you using iscsi to access the storage or do you have FC connection to the drives?"
-> FC Connection

"When both nodes are up, can both nodes access the data on the shared drive?"
-> Should be. Both the nodes can see the quorum drive online at the same time.

Which fencingmethod and fencing device are you using?"
-> IBM blade center.

I've verified the both the nodes have identical cluster.conf. The problem is, eventually when one of the two nodes goes down and is rebooted, that node can not form a quorum with the cluster and shows as offline. The node is not able to rejoin the cluster. So the logs in /var/log/messages says that 'Cluster is not quorate. Refusing connections'

I was not able to find much useful info about two node cluster with quorum disk, hence seeking help here.

Any idea why is the node not able to form quorum and join the cluster.

Featured Post

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

In this article, I provide some information on storage disks which go into calculations that will help you figure out how much Input/output Operations Per Second (IOPS) your disk subsystem can deliver.
To effectively size & tune up applications l…

It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.

Learn how to navigate the file tree with the shell.
Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…

This video teaches viewers how to encrypt an external drive that requires a password to read and edit the drive. All tasks are done in Disk Utility.
Plug in the external drive you wish to encrypt:
Make sure all previous data on the drive has been …