|
Well I tried this on my two real servers that are being load balanced with
LVS and I still have my original problem. It seems even though I have these
entries, when I hit the VIP it continues to resolve to only one of the
servers, even though I turn off apache on the server that it's resolving to.
I'm assuming LVS should tell the request to route to the second server, but
tcpdump reveals that its still hitting the first. Is it possible the ARP is
still messed up or does that clear in some short time frame?
Kirk
-----Original Message-----
From: Con Tassios [mailto:ct@xxxxxxxxxxx]
Sent: Sunday, March 27, 2005 3:16 PM
To: kirk@xxxxxxxxxxxxxxxxx; LinuxVirtualServer.org users mailing list.
Subject: RE: Initial setup
With RHEL3 you can install the arptables_jf package (included in RHEL) and
use
that to overcome the ARP problem. No patching of the kernel is required.
On the Real Servers:
arptables -F
arptables -A IN -d $VIP -j DROP
arptables -A OUT -s $VIP -j mangle --mangle-ip-s $RIP
service arptables_jf save
chkconfig arptables_jf on
where RIP = Real Server IP address and VIP = Virtual IP address.
> [root@web4]# uname -a
> Linux web4.sys.salesjobs.com 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT
> 2003 i686 i686 i386 GNU/Linux
> [root@web4]# more /etc/redhat-release
> Red Hat Enterprise Linux ES release 3 (Taroon Update 4)
>
> I've already set this:
> ifconfig lo:0 <VIP> netmask 255.255.255.255
>
>
> And trying your suggestion for the arp setting in /etc/sysctl.conf yields:
>
> [root@web4]# sysctl -p
> net.ipv4.ip_forward = 0
> net.ipv4.conf.default.rp_filter = 1
> error: 'net.ipv4.conf.lo.arp_ignore' is an unknown key
> error: 'net.ipv4.conf.lo.arp_announce' is an unknown key
> error: 'net.ipv4.conf.all.arp_ignore' is an unknown key
> error: 'net.ipv4.conf.all.arp_announce' is an unknown key
> kernel.sysrq = 0
> kernel.core_uses_pid = 1
> [root@web4]#
>
>
> I guess the above is due to the version I have or no patch installed? Is
it
> that I'm missing the noarp module?? Where do I get that if so?
|
