|
... I have some issues I hope some of you can clarify.
I'ld like to start off by regretting that this is going to be quite
lengthy.
The director and realservers all use kernels 2.4.22.
Director:
patched with linux_kernel_ksyms_c.diff and linux_net_netsyms_c.diff
from ipvs-1.0.10
Realservers:
patched with hidden-2.4.20pre10-1.diff also from ipvs-1.0.10
I use configure-lvs_0.9.4 and the conf file I ran configure on is as
follows:
LVSCONF_FORMAT=1.1
LVS_TYPE=VS_DR
INITIAL_STATE=on
CLEAR_IPVS_TABLES=yes
VIP=eth0:110 lvs 255.255.255.255 192.168.27.110
DIP=eth0 dip 192.168.27.0 255.255.255.0 192.168.27.255
DIRECTOR_GW=client
SERVICE=t telnet rr RS1 RS2
SERVER_VIP_DEVICE=lo:0
SERVER_NET_DEVICE=eth0
SERVER_GW=client
The host files are
/ets/hosts:Director
127.0.0.1 localhost
192.168.27.254 client
192.168.27.1 dip
192.168.27.110 lvs
192.168.27.30 RS1
192.168.27.31 RS2
/etc/hosts:Realservers
127.0.0.1 localhost
192.168.27.1 dip
192.168.27.30 RS1
192.168.27.31 RS2
Now, though everything seems to work (multiple telnets to 192.168.27.110
ends up on either RS1 or RS2) I am a bit worried about the errors I get
when executing rs.lvs_dr on the director and realservers respectively.
On the Director (minor issue I guess - meaning I believe I'll manage to
get rid of this one):
Error: DIRECTOR_GW is set to 192.168.27.254
It should not be set for vs-dr
setting DIRECTOR_GW to null
Errors: 1
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.
Your LVS may not be setup properly.
On the realservers (This one I'm clueless about):
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: File exists
Error: table RIP already has entry: via dev eth0
cannot overwrite entry, you'll have to delete the old one first.
RTNETLINK answers: File exists
Error: table RIP already has entry: via 192.168.27.1 dev eth0
cannot overwrite entry, you'll have to delete the old one first.
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
Dump terminated
RTNETLINK answers: File exists
Error: table VIP already has entry: via 192.168.27.254 dev eth0
cannot overwrite entry, you'll have to delete the old one first.
RTNETLINK answers: Invalid argument
Dump terminated
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.
Your LVS may not be setup properly.
What am I doing wrong? Any clues will be greatly appreciated.
On another note. I'ld really like to use the noarp module. How am I to
use this on the realservers? Should I simply setup the lo:x interface
using noarpctl and skip executing the rc.lvs_dr script on the
realservers
or is the script still needed?
TIA
Thomas Wentzel
|
