[Pacemaker] Cluster Communication fails after VMWare Migration

[Andrew Beekhof]

On Wed, Feb 23, 2011 at 10:31 AM,  <u.schmeling at online.de> wrote:
>
> Have build a 2 node apache cluster on VMWare virtual machines, which was running as expected. We had to migrate the machines to another computing center and after that the cluster communication didn't work anymore. Migration of vmS causes a change of the networks mac address. Maybe that's the reason for my problem. After removing one node from the cluster and adding it again the communication worked. Because migrations between computing centers can happen at any time (mirrored esx infrastructure), I have to find out, if this breaks the cluster communication.

Cluster communication issues are the domain of corosync/heartbeat -
their mailing lists may be able to provide more information.
We're just the poor consumer of their services :-)

>
> regards Uwe
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>
>