[Linux-cluster] Basic Active Active File Server

[Jason Fitzpatrick]

Hi Kit..

Awesome and all as I am when it comes to computers, networking is a
serious weak point ;0)

How would I go about checking if multicast traffic is making it
between the two nodes, they are now hosted of the same ESX server and
therefore only hitting the virtual switch in the ESX and should not
have to traverse our network at all.

I will review the ESX switch config and DNS (I have a horrible feeling
that the DNS gremlins are responsible, but am pretty sure that this
should not affect Multicast)

Also the multicast address that should be used, I am using 244.0.0.1
which I believe is 	The All Hosts multicast group that contains all
systems on the same network segment, but am not a 100% sure if this is
the correct setting.

Thanks again

Jay

On 22 June 2010 09:12, Kit Gerrits <kitgerrits at gmail.com> wrote:
>
> Keep in mind that multicast requires a multicast router to handle the
> traffic.
> Mere Layer2 connectivity is not enough.
>
> If broadcast does work, that might be your problem.
>
> Kit
>
> -----Original Message-----
> From: linux-cluster-bounces at redhat.com
> [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Jason Fitzpatrick
> Sent: maandag 21 juni 2010 18:14
> To: linux clustering
> Subject: Re: [Linux-cluster] Basic Active Active File Server
>
> Hi..
>
> I have tried both multicast and broadcast to no avail, as above I am moving
> the systems to the same ESX to try and rule out the networking end of
> things, I have not tried the tcpdump but was running wireshark in an attempt
> to do the same as you recommended
>
> Jay
>
> On 21 June 2010 16:49, Kaloyan Kovachev <kkovachev at varna.net> wrote:
>> Hi,
>> On Mon, 21 Jun 2010 16:07:34 +0100, Jason Fitzpatrick
>> <jayfitzpatrick at gmail.com> wrote:
>>> Hi all
>>>
>>> I am having no end of trouble getting a basic Active Active Cluster
>>> working. at the moment it is in test / proof of concept and has
>>> manual fencing in place but I cannot for the life of me get the 2
>>> nodes to join to the one cluster (they both report joined in crm_tool
>>> status but only to a local clustered instance if that makes any
>>> sence)
>>>
>>> I have tried to use luci and system-config-cluster to get this up and
>>> running and have been at it over a week, the network guys swear that
>>> there is nothing blocking multicast traffic between them and the
>>> firewalls have been disabled (they are on the same VLAN but connected
>>> to different switches) servers have been rebuilt and have RHEL 5.5
>>> installed
>>>
>>
>> your problem is the multicast traffic - check with tcpdump if it is
>> comming to the other server at all (network) and if it is, then
>> doublecheck the firewall.
>> alternatively you may try using broadcast instead of multicast
>>
>>> Shared Storage is being provided by an Active Active DRBD setup
>>> (tested and working)
>>>
>>> I have attached a copy of my cluster.conf
>>>
>>> Thanks in advance
>>>
>>> Jay
>>>
>>> --
>>>
>>> "The only difference between saints and sinners is that every saint
>>> has a past while every sinner has a future. "
>>> - Oscar Wilde
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>
>
>
> --
>
> "The only difference between saints and sinners is that every saint has a
> past while every sinner has a future. "
> - Oscar Wilde
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.829 / Virus Database: 271.1.1/2952 - Release Date: 06/20/10
> 20:36:00
>
>



-- 

"The only difference between saints and sinners is that every saint
has a past while every sinner has a future. "
— Oscar Wilde