[Pacemaker] Nodes unable to connect / find each other

[Regendoerp, Achim]

Hi,

According to the network guy the multicast is all there, but we've got no step further, so we're trying your suggested method now :)

Didn't know that corosync now supports unicast too, must've missed that...

Thanks for the heads up!

Achim



-----Original Message-----
From: Andreas Kurz [mailto:andreas at hastexo.com] 
Sent: 14 March 2012 21:56
To: pacemaker at oss.clusterlabs.org
Subject: Re: [Pacemaker] Nodes unable to connect / find each other

On 03/14/2012 08:22 PM, mark - pacemaker list wrote:
> Hi,
> 
> On Wed, Mar 14, 2012 at 1:43 PM, Regendoerp, Achim 
> <Achim.Regendoerp at galacoral.com 
> <mailto:Achim.Regendoerp at galacoral.com>>
> wrote:
> 
>     Hi,____
> 
>     __ __
> 
>     Below is a cut out from the tcpdump run on both boxes. The tcpdump
>     is the same on both boxes.____
> 
>     The traffic only appears if I set the bindnetaddr in
>     /etc/corosync/corosync.conf to the machines' individual IP instead
>     of to 10.26.29.0 (as advised by howtos).____
> 
>     Having the latter IP as bindnetaddr, there's no traffic at 
> all.____
> 
>     __ __
> 
> 
> 
> I initially had some communication issues like these, then I realized 
> I'd forgotten to set up my switch/vlan to handle multicast.  Oops.  
> With that fixed, everything came up and has worked wonderfully since.

Or use upnp ... unicasts if you don't want/can change your network setup

Regards,
Andreas

--
Need help with Pacemaker?
http://www.hastexo.com/now

> 
> Something to check, anyhow.
> 
> Regards,
> Mark
> 
> 
> _______________________________________________
> 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://bugs.clusterlabs.org