Hi and thanks for answering
> > As you can see the realserver 192.168.100.32:80 is listed
> > as Local. Which DO make sence since that realserver is
> > local to the director im issuing the command on.
>
> do you have 4 boxes or 2?
I have 2 hardware servers.
>
> > Now here comes the problem: If
Gerry Reno wrote:
> Schedulers question:
>
> To test I am using the 'rr' scheduler and sure enough the accesses are
> bouncing from one real server to the other. But this is occurring even
> when I am in a session. Is there no session 'stickiness' with the
> schedulers?
>
Note that you have a
On Sun, 2007-07-22 at 22:24 -0400, Gerry Reno wrote:
> What exactly would be the benefit of notify_master/backup/fault and this
> script. It just puts a VIP/32 on 'lo' for the backup director and delete
> the VIP/32 from 'lo' for the master director. Is this necessary? I mean
> wouldn't you just
On Mon, 23 Jul 2007, Jonas Akrouh Larsen wrote:
> I have 2 hardware servers.
Have you read the documentation for the two box setup?
>> is the route set correctly for the 2nd realserver?
>
> I guess that depends on what "correctly" means?
correctly for LVS-DR. Is the default gw
not_through_the_
Just a followup: it is definitely a driver issue. The tg3 broadcom
kernel module doesn't seem to work properly at gigabit speeds. 100 mbit
works fine (which is OK in this situation).
Thanks for all the helpful suggestions,
-Jesse
Joseph Mack NA3T wrote:
> On Fri, 20 Jul 2007, Jesse Cantara wrot
> Have you read the documentation for the two box setup?
Yep, as I described I have followed the ultramonkey guide on setting up
the 2 boxes,2 directors, 2 realservers example.
Are there any other guides/documentation on setting up such a system?
I did btw test with a simpler telnet setup with 1
Hi!
On Mon, 23 Jul 2007, Jesse Cantara wrote:
> Just a followup: it is definitely a driver issue. The tg3 broadcom
> kernel module doesn't seem to work properly at gigabit speeds. 100 mbit
> works fine (which is OK in this situation).
Then I'd look into the matter more closely. We use about 1k
On Mon, 23 Jul 2007, Jonas Akrouh Larsen wrote:
> Are there any other guides/documentation on setting up such a system?
you could try the LVS-DR example in the mini-HOWTO
Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at h
Tobias, thanks for the information.
The device on my machine is the Broadcom BCM5721, and the reason why I
decided that the driver was at fault is because I found somebody else
online with the same problem and that particular model of Broadcom NIC.
Also to re-update the situation, setting it to
Hi!
On Mon, 23 Jul 2007, Jesse Cantara wrote:
> The device on my machine is the Broadcom BCM5721, and the reason why I
> decided that the driver was at fault is because I found somebody else
> online with the same problem and that particular model of Broadcom NIC.
My fault, I neglected to take
I have found a technique that allows me to control LVS-DR VIP with
keepalived only. I modified the /etc/keepalived/ip_localhost script that
I have been using to issue a remote "ip addr add' command to the real
servers for the 'del' case and put the VIP on the lo device. Right now
I'm using 'rsh
Gerry Reno wrote:
> I have found a technique that allows me to control LVS-DR VIP with
> keepalived only. I modified the /etc/keepalived/ip_localhost script that
> I have been using to issue a remote "ip addr add' command to the real
> servers for the 'del' case and put the VIP on the lo device.
Today while testing my LVS-DR I have been running into the situation
where keepalived gets itself into some kind of sync issue. Basically
both directors end up as master and then nothing works after that. Here
is a snip from logs:
DIRECTOR 1:
Jul 23 21:52:50 grp-01-00-50 Keepalived: Starting
Here is what I added to the 'del' case in ip_localhost:
rsh 192.168.1.200 /sbin/ip addr add 192.168.1.240/32 dev lo brd + scope host
rsh 192.168.1.201 /sbin/ip addr add 192.168.1.240/32 dev lo brd + scope host
rsh 192.168.1.200 echo "1" > /proc/sys/net/ipv4/conf/eth0/arp_ignore
rsh 192.168.1.201 ec
14 matches
Mail list logo