|
ok, I think I mis-typed. My real-servers orginally had the VIPs of arlx043
and arlx044, but now an ifconfig revels the following:
[arl@arlx044 arl]$ /sbin/ifconfig
eth1 Link encap:Ethernet HWaddr 00:60:CF:20:5D:9C
inet addr:9.3.61.16 Bcast:9.255.255.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4031647 errors:0 dropped:0 overruns:0 frame:0
TX packets:5738803 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:18
eth1:0 Link encap:Ethernet HWaddr 00:60:CF:20:5D:9C
inet addr:10.1.1.3 Bcast:10.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
[arl@arlx044 arl]$
and
[arl@arlx043 arl]$ /sbin/ifconfig
eth1 Link encap:Ethernet HWaddr 00:60:CF:20:5D:8F
inet addr:9.3.61.16 Bcast:9.255.255.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1354260 errors:0 dropped:0 overruns:0 frame:0
TX packets:1842344 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:18
eth1:0 Link encap:Ethernet HWaddr 00:60:CF:20:5D:8F
inet addr:10.1.1.2 Bcast:10.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
[arl@arlx043 arl]$
My lvs_dr.conf file appears as such:
#----------lvs_dr.conf----------------------------------------
LVSCONF_FORMAT=1.0
LVS_TYPE=VS_DR
INITIAL_STATE=on
CLEAR_IPVS_TABLES=yes
VIP=eth1 arlx016 255.255.255.255 arlx016
DIRECTOR_INSIDEIP=eth1:0 10.1.1.1 10.1.1.0 255.255.255.0 10.1.1.255
#no default gw for director with VS-DR or VS-Tun
#DIRECTOR_GW=
SERVICE=t www pard 10.1.1.2 10.1.1.3
SERVER_VIP_DEVICE=eth1
SERVER_NET_DEVICE=eth1:0
SERVER_GW=9.3.61.1
#----------end lvs_dr.conf------------------------------------
(pard is a slightly modified scheduling algorithm - I have also modified
the necessary files to accept this - when it acutally gets called (about
once per thousand requests) it seems to work :) )
Thanks!
alison
"Zachariah Mully" <zmully@xxxxxxxxxxxxxx>@LinuxVirtualServer.org on
07/05/2001 11:20:58 AM
Please respond to lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Sent by: lvs-users-admin@xxxxxxxxxxxxxxxxxxxxxx
To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
cc:
Subject: RE: arp problems
Alison-
Perhaps I have this wrong, or perhaps you mistyped, but on my VS-DR
setup, my RS's have the same non-arping VIP on them (i.e they have to be
able to process the VIP locally once the director hands them the
connection). It looks like you've got your RS on different VIPs than the
director... I am assuming that arlx016, arlx043 and arlx044 are named
for their different IP's.
It might help to have some more information, what is your lvs_dr.conf
look like?
Then again I am on day 7 of learning how to setup and administer an
LVS
system, so I might be TOTALLY wrong.
Back to firewalling.
Zack
> director:
> VIP: arlx016
> DIP: 10.1.1.1
>
> real-servers:
> VIP: arlx043
> RIP: 10.1.1.2
>
> VIP: arlx044
> RIP: 10.1.1.3
>
>
_______________________________________________
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
|
