Hi
Version cman : cman-2.0.95-1
I have a doubt about the behavior of cman with heat-beat quorum disk :
if there is a pb on quorum disk access (IO error) on only one of the 2
nodes
in cluster, but with heart-beat always working fine, does cman will
force the failover ?
or does it keep both
Hi,
I have working failover of virtualized guest. could someone give me hint
how to configure the vm failover to failback after recovery? eg. vm_A
runs xen01, xen01 fails, so xen02 takes over the vm_A, after xen01 is up
again, the vm_A is migrated back to xen01.
I have already tried many
Hello Mike,
I'm doing this implementation too. The problem is fence_vmware, 'cause:
- Not exist officially on Red Hat
- This unofficial fence_vmware (perl) don't compile on x86_64
http://www.tournament.org.il/run/?p=140
Stepan Kadlec wrote:
Hi,
I have working failover of virtualized guest. could someone give me
hint how to configure the vm failover to failback after recovery? eg.
vm_A runs xen01, xen01 fails, so xen02 takes over the vm_A, after
xen01 is up again, the vm_A is migrated back to xen01.
I have
Hi, thanks for the reply.
The problem is when one Physical Machine goes down. Fence of Virtual
Machines works very well using any fence_vmware.
In the past, I've used my fibre channel switch as the fencing mechanism. It was
more complex than I would have liked, too many fencing problems
I've written a perl script, modeled after the fence_drac script, to control
outlets on a TrippLite PDUMH15ATNET PDU, and I'd like to contribute it to the
community.
What do I need to do to make the cluster software (RHCS 5.2, under
CentOS 5.2, cman version 2.0.84) aware of the new agent so that
