|
hi there!
i tried the ha-code to reach high availability. the fail over works well,
ip-addresses are taken and reachable afterwards. the only problem is, that the
requests to the vip aren't answered. tcpdump on the director and the webserver
display the requests, but no reply reaches the browser in outside the vs.
here some details:
kernel: 2.2.17
vip: 172.16.2.160/24 (eth1:1)
outside_ip: 172.16.2.161/24 (eth1)
dip: 192.168.10.1/24 (eth0)
web1: 192.168.10.10
web2: 192.168.10.10
kernel routing table:
Destination Gateway Genmask Flags MSS Window irtt Iface
172.16.2.160 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
172.16.2.161 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
172.16.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 172.16.2.254 0.0.0.0 UG 0 0 0 eth1
the ipchainsChain input (policy ACCEPT):
Chain forward (policy ACCEPT):
target prot opt source destination ports
MASQ tcp ------ 192.168.10.1 anywhere telnet -> any
MASQ tcp ------ 192.168.10.2 anywhere telnet -> any
MASQ tcp ------ 192.168.10.1 anywhere http -> any
MASQ tcp ------ 192.168.10.2 anywhere http -> any
MASQ tcp ------ 192.168.10.1 anywhere ftp -> any
MASQ tcp ------ 192.168.10.2 anywhere ftp -> any
MASQ tcp ------ 192.168.10.1 anywhere https -> any
MASQ tcp ------ 192.168.10.2 anywhere https -> any
and the ipvsadm output:
IP Virtual Server version 1.0.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 172.16.2.160:https lc persistent 360
-> 192.168.10.1:https Route 1 0 0
-> 192.168.10.2:https Route 1 0 0
TCP 172.16.2.160:ftp lc persistent 360
-> 192.168.10.1:ftp Route 1 0 0
-> 192.168.10.2:ftp Route 1 0 0
TCP 172.16.2.160:http lc
-> 192.168.10.1:http Route 1 0 0
-> 192.168.10.2:http Route 1 0 0
the funny thing about this is, that, if the regular rc.lvs_nat script is
startet, everything works fine. if the ipvsadm-rules are set manually by me,
also everything is ok. but if the heartbeat-service is started, nothing happens.
i just see packets arriving at port 80 on the director and both webservers, but
no reply is sent. the default gw is the director, set on both of the webservers.
anybody an idea?
thanx
clemens
|
