LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

LVS-DR

To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: LVS-DR
From: "Alexander Meis" <am@xxxxxxxxxxxxx>
Date: Fri, 12 Dec 2003 16:21:41 +0100
Hi...

i try to get an LVS-DR working on Debian with a kernel 2.4.23.

The director IP is 192.168.0.61, Realserver 192.168.0.63
the VIP ip is 192.168.0.110

The config (for ./configure) looks like this.

#----------lvs_dr.conf----------------------------------------
LVSCONF_FORMAT=1.1
LVS_TYPE=VS_DR
INITIAL_STATE=on
CLEAR_IPVS_TABLES=yes
VIP=eth0:110 192.168.0.110 255.255.255.255 192.168.0.110
DIP=eth0:61 192.168.0.61 192.168.0.0 255.255.255.0 192.168.0.255
SERVICE=t http rr 192.168.0.63
SERVER_VIP_DEVICE=lo:110
SERVER_NET_DEVICE=eth0
SERVER_GW=192.168.0.1
#----------end lvs_dr.conf------------------------------------

i start it on the director and i got

IP Virtual Server version 1.0.10 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  192.168.0.110:www rr
  -> 192.168.0.63:www             Route   1      0          0

starting the same rc.lvs_dr script on the realserver getets me an error, as
shown blow,

can someone tell me how to fix this Problem ?

Thanks

Alex




***********
Installing priority routing
lvs type vs-dr, SERVER_GW 192.168.0.1
priority rules
RTNETLINK answers: Invalid argument
Dump terminated
routes VIP
routes RIP
adding rules to RIP with priority 100 from 192.168.0.63 to 192.168.0.0/24
RTNETLINK answers: Invalid argument
adding routing rules to RIP with priority 100 from 192.168.0.63 to 0/0
RTNETLINK answers: Invalid argument
showing ip rules for priority 100
RTNETLINK answers: Invalid argument
Dump terminated
set src device for packets from VIP
packets with src=VIP are sent out eth0
ip route show table RIP (should be empty):
no gateway - is link route: ip route add table RIP to 192.168.0.0/24 dev
eth0 from 192.168.0.63
RTNETLINK answers: File exists
route add: return_code 2
Error: table RIP already has entry: via  dev eth0
cannot overwrite entry, you'll have to delete the old one first.
current entry: set src device for packets from VIP
packets with src=VIP are sent out eth0
ip route show table RIP (should be empty):
adding route to gateway 192.168.0.61 in table RIP
ip route add table RIP to 0/0 via 192.168.0.61 dev eth0 from 192.168.0.63
RTNETLINK answers: File exists
route add: return_code 2
Error: table RIP already has entry: via 192.168.0.61 dev eth0
cannot overwrite entry, you'll have to delete the old one first.
current entry: adding VIP routing rules with priority 99 to realserver.
RTNETLINK answers: Invalid argument
showing ip rules for prio 99
RTNETLINK answers: Invalid argument
Dump terminated
set src device for packets from VIP
packets with src=VIP are sent out eth0
ip route show table VIP (should be empty):
adding route to gateway 192.168.0.1 in table VIP
ip route add table VIP to 0/0 via 192.168.0.1 dev eth0 from 192.168.0.110
RTNETLINK answers: File exists
route add: return_code 2
Error: table VIP already has entry: via 192.168.0.1 dev eth0
cannot overwrite entry, you'll have to delete the old one first.
current entry: removing default gw
showing priority routing
RTNETLINK answers: Invalid argument
Dump terminated
192.168.0.110 dev lo  scope link  src 192.168.0.110
192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.63
routing for table VIP
routing for table RIP
ntpd not running, won't be restarted
not adding filter rules.
The location of the output file rc.lvs is the default = ./
You can change this (and other output files) by editing the variables
$rc_lvs_home, $rc_mon_home, $rc_ntp_home


Errors: 3
Some of these errors are from tests that failed.
If you're experimenting, it's possible that the LVS will work.
If you're doing production, you can't assume that the LVS will work.

**********

<Prev in Thread] Current Thread [Next in Thread>