I've spent the last two days getting ultramonkey with ldirectord up and
running on two boxes. It's been a pretty smooth ride with the
documentation being a big help.
I'm having trouble getting multiple VIPs to work in the way I want it to,
however.
I want to have 2 VIPS that direct http/https traffic to two different
pools of RIPs (a production and a test environment)
In this config I'm trying to get x.x.x.180 to forward to 192.168.2.150,
and x.x.x.189 to forward to 192.168.2.151
my ldirectord.cf:
# Global Directives
checktimeout=3
checkinterval=1
fallback=127.0.0.1:80
autoreload=yes
quiescent=yes
virtual=x.x.x.180:80
real=192.168.2.150:80 masq
fallback=127.0.0.1:80
service=http
request="hb.html"
receive="Test Page"
scheduler=rr
#persistent=600
#netmask=255.255.255.255
protocol=tcp
virtual=x.x.x.189:80
real=192.168.2.151:80 masq
fallback=127.0.0.1:80
service=http
request="hb.html"
receive="Test Page"
scheduler=rr
#persistent=600
#netmask=255.255.255.255
protocol=tcp
--However, both VIPs are directing traffic to both RIPs:
ipvsadm output:
IP Virtual Server version 1.0.10 (size=65536) Prot LocalAddress:Port
Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP x.x.x.180:http rr
-> lb1.sdsu.edu:http Local 0 0 0
-> 192.168.2.151:http Masq 1 0 23
-> 192.168.2.150:http Masq 1 0 24
TCP x.x.x.189:http rr
-> 192.168.2.150:http Masq 1 0 9
-> 192.168.2.151:http Masq 1 0 8
-> lb1.sdsu.edu:http Local 0 0 0
ldirectord is launched by /etc/ha.d/haresources
lb1.sdsu.edu IPaddr::192.168.2.100 IPaddr::x.x.x.189/24/eth0
IPaddr::x.x.x.180/24/eth0 ldirectord::ldirectord.cf
192.168.2.100 is the DIP. It seems to think that the two different VIPs
are supposed to point to the two different RIPs:
(tail of /var/log/ldirectord.log)
[Fri Mar 26 18:15:21 2004|ldirectord.cf] Restored real server:
192.168.2.151:80 (0 x x.x.x.180:80) (Weight set to 1)
[Fri Mar 26 18:15:21 2004|ldirectord.cf] Quiescent fallback server:
127.0.0.1:80 (1 x x.x.x.180:80) (Weight set to 0)
[Fri Mar 26 18:15:21 2004|ldirectord.cf] Restored real server:
192.168.2.151:80 (-1 x x.x.x.189:80) (Weight set to 1)
[Fri Mar 26 18:15:22 2004|ldirectord.cf] Restored real server:
192.168.2.150:80 (1 x x.x.x.180:80) (Weight set to 1)
[Fri Mar 26 18:15:22 2004|ldirectord.cf] Restored real server:
192.168.2.150:80 (0 x x.x.x.189:80) (Weight set to 1)
Do you have any ideas as to why this it's behaving this way?
|