|
I have three boxes set up (1 director, 2 realservers) using DR...All
boxes are running 2.4.9 with the 0.8.1 LVS patched into them.
When I run Joseph Mack's configure script, it looks as though it
properly configures both my director and real servers (i run it like
this: ./configure lvs_dr_my_conf -i). It does its stuff...and works.
Anyway, my config looks like this:
#----------lvs_dr.conf----------------------------------------
LVSCONF_FORMAT=1.0
LVS_TYPE=VS_DR
INITIAL_STATE=on
CLEAR_IPVS_TABLES=yes
VIP=eth0:33 192.168.0.33 255.255.255.255 192.168.0.33
VIP=eth0:34 192.168.0.34 255.255.255.255 192.168.0.34
DIRECTOR_INSIDEIP=eth1 192.168.0.35 192.168.0.0 255.255.255.128
192.168.0.127
#no default gw for director with VS-DR or VS-Tun
#DIRECTOR_GW=192.168.0.1
#SERVICE=t telnet rr sneezy bashfull
#SERVICE=t ftp rr 192.168.0.36 192.168.0.37
#SERVICE=t http rr 192.168.0.36 192.168.0.37
SERVICE=t https rr 192.168.0.36 192.168.0.37
SERVER_VIP_DEVICE=lo:110
SERVER_NET_DEVICE=eth0
SERVER_GW=192.168.0.1
#----------end lvs_dr.conf------------------------------------
...now here's the catch. when I run ipvsadm it says this:
IP Virtual Server version 0.8.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP jules.mydomain.com:0 rr persistent 360
-> 192.168.0.36:0 Route 1 0 0
TCP jules.mydomain.com:http rr
-> 192.168.0.37:http Route 1 0 0
-> 192.168.0.36:http Route 1 0 0
It also performs what looks like rr balancing on all tcp packets that i
send it...even telnet, ssh, http, etc even though they are all disabled.
I am guessing that the jules.mydomain.com:0 rr persistant 360 is my
problem. Why is it putting it in there?
but wait...theres more!
When i try to https to jules.mydomain.com, it only sends me to
192.168.0.36. but when i telnet to jules.mydomain.com, to looks like it
performs balanced rr on it. Weird? When I change the SERVICE line from
SERVICE=t https rr 192.168.0.36 192.168.0.37 to SERVICE=t https rr
192.168.0.37 192.168.0.36 then it does the exact opposite. It sends all
https requests to 192.168.0.37.
Any Ideas?
Thanks in advance guys. This seems like a pretty bitchin' project. I
hope I can get it to work!
Ryan
|
