Re: UM3 & High Capacity Highly Availability and Load Balancing problem

Ok a little update, the fedora real servers are using the sysctl.conf for
the arp control.

 

I ended up getting things to work but not as I had hoped. I was initially
putting my cluster on 192.168.2.XXX so my netmask on the Ethernet cards was
set to 255.255.248.0 on both directors and real servers because the actual
development computers here at work run on 192.168.0.XXX

 

The way I got this working was setting my eth netmasks to 255.255.255.0 and
putting all the servers on the same 192.168.0.XXX as I was.  The second I
made the changes and restarted the networks my directors picked up on the
real servers and have been up ever since.

 

This is a good thing, to an extent.. We would really like to separate the PC
network from the server network.

 

My new question pertains to the haresources file, in there I had  the
virtual ip address set like this:

IPaddr2::192.168.2.10/24/eth0/192.168.2.255
 
Would this be the correct value for the virtual ip running on a network that
should have a netmask of 255.255.248.0?

 

  _____  

From: [email protected]
[mailto:[email protected]] On Behalf Of Glen Kendell
Sent: Tuesday, June 26, 2007 9:41 PM
To: [email protected]
Subject: Re: [ULTRAMONKEY-USERS] UM3 & High Capacity Highly Availability and
Load Balancing problem

 

maybe you've already answered your own question.  assuming you are using
direct routing, what have you done on the fedora boxes to suppress arp?

On 6/26/07 3:41 PM, "Nathan Brown" <[email protected]> wrote:

I have 2 load balancers setup running debian and 2 web servers setup running
fedora 7
 
My main problem is that when the load balancers first come up and start
routing traffic everything works fine, I can view ipvsadm and see that it
can see both web servers just fine.  The problem comes about 20 or 30
seconds after the the load balancers starts routing.  What happens is one of
the web servers drops and then a few moments later the other web server
drops and then it adds the fail back 127.0.0.1 to the list being the only
active server.
 
What I cant figure out is why for those first 20 or 30 seconds I can use
everything wonderfully but after that some catastrophe happens.  Is it an
ARP issue with fedora?
 
I was able to use the debian setup for the real servers without a problem,
sysctl.conf took the arp setting without error.  The only other thing that
might throw it I guess would be that my balancers operate on eth0 and the
web servers operate on eth1
 
Let me know if anyone has any suggestions

  _____  

_______________________________________________
Ultramonkey-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/ultramonkey-users

_______________________________________________
Ultramonkey-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/ultramonkey-users