On Sun, 2006-03-26 at 12:41 -0300, Celso K. Webber wrote: > We had many problems with quorum formation under this environment. If we > booted both servers at the same time, quorum would be formed successfully. If > after that we rebooted one of the servers, it would not rejoin the cluster > until we stopped clumanager on both sides and restarted. Are you using disk-based or network-based tiebreaker? > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136553 I was never convinced that this was an iSCSI / RHCS3 interaction problem, for what it's worth ;) > Question: is there a limitation or need to use broadcast heartbeating under an > iSCSI environment? Why multicast heartbeating didn't work here? There shouldn't be, but if there is, it's due to a network / iSCSI interaction problem that I do not really understand ;) I wrote some stuff here about RHCS3 + network configuration here, so I won't retype it. Take a look and see if anything rings a bell with your particular hardware configuration: http://people.redhat.com/lhh/network-stuff.html -- Lon -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
