|
Hi, Doug!
>I have apache listening on 10.0.3.3 and setup
different
>index pages so I could tell which real server I was
hitting.
I like this, too!
>I fired it up and it kinda works. It will switch
back and forth
>a few times then hang. If I hit stop it will then
work again
>a few more times. Looking at the activity LEDS on the
hub I noticed
>they were on solid between the two boxes.
Do you get always the same index-page again or do you get an
error message (page not found...)?
Did you set the default gateway to 10.0.3.5 (your
Router/Client, very important for Direct Routing)
We had similar problems using a completely diferent
configuration (Slackware, 2.2.16, 2 directors / 4 realservers...)
One thing we found out is that in some cases the VIP on one
(and always the same, don't know why) realserver took over the VIP from the
director. So the VIP was bound to only ONE realserver, so we got always the same
index page from this server :(
I think we had problems with the subnet mask (won't get to be
255.255.255.255).
We didn't find a special reason for it, but after we changed
the VIP from dummy to dummy0:0 and restarted a few times, it was all good
again.
One other thing was, that we had a failure after "flooding"
the director's NIC (webbench :-)
We had "mon" running to check the realservers over the same
NIC (on the director), so after some time of testing we got service failures for
one client (which is in your case about 50% ;-)
I don't know if this could help you (I learned very much about
LVS and Heartbeat by reading logfiles...), that's just my
experience.
Henning Schiel
----- Original Message -----
Sent: Sunday, April 22, 2001 12:35
AM
Subject: Packet Storm w/ 2.4.3 & lvs
0.2.11
Hi,
I'm trying to implement a two box lvs cluster with
failover.
I'm very close to having this working. I have heartbeat
installed
and configured to use both lans with UDP. I test that the
VIP (10.0.3.3)
switches when I disconnect either server. They switch
on a VIP of eth:0.
I then moved on to the load balancing
portion.
This is what I
have:
client
10.0.3.5
|
|
-------------------------
10.0.3.0/24
|
|
eth0 |
10.0.3.1
| 10.0.3.2
box
1
box 2
eth1 |
192.168.1.1
|
192.168.1.2
|
|
--------------------------
192.168.1.0/24
(cross-over cable)
Box 1 and 2 are both directors and servers.
I'm using the latest 2.4.X patches (Apr 20th) and ipvsadm 1.17
I
installed the following on both boxes:
ipvsadm -A -t 10.0.3.3:80 -s
rr
ipvsadm -a -t 10.0.3.3:80 -r 10.0.3.1:80 -g -w 1
ipvsadm -a -t
10.0.3.3:80 -r 10.0.3.2:80 -g -w 1
I have apache listening on 10.0.3.3
and setup different
index pages so I could tell which real server I was
hitting.
I fired it up and it kinda works. It will switch back
and forth
a few times then hang. If I hit stop it will then work
again
a few more times. Looking at the activity LEDS on the hub I
noticed
they were on solid between the two boxes.
I read as much as
humanly possible of the HOWTO and figured it might
have something to do
with the "arp problem" so I added the "hidden"
patch to both kernels,
changed the VIP for the real servers to 10.0.3.4
(left it 10.0.3.3 for the
Directors/HeartBeat), and ifconfig'd dummy0
on both boxes to 10.0.3.4, and
turned hidden on in /proc/sys/net/...dummy0
I still get the packet
storm.
I'm going to try to sniff the network and see what's going on
but I'm
rapidly approaching areas where I'm a total novice.
I think
there must be something stupid I'm doing
?
Thanks,
Doug
_______________________________________________
LinuxVirtualServer.org
mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send
requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or
go to http://www.in-addr.de/mailman/listinfo/lvs-users
| 