|
Hello,
We are trying to setup a LVS load balancer for multiple services (HTTP,
HTTPS, LDAP, ...).
All these services are distributed over several servers, and they all
need persistence.
They also use multiple ports, so we used fwmarks to identify the service.
Here's our ipvsadm output:
lvs1:~# ipvsadm
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
FWM 1234 wrr persistent 180
-> 10.0.20.12:0 Masq 1 0 0
-> 10.0.20.11:0 Masq 1 0 0
FWM 234 wrr persistent 180
-> 10.1.9.10:0 Masq 1 0 0
-> 10.1.9.11:0 Masq 1 0 0
FWM 235 wrr persistent 180
-> 10.1.13.20:0 Masq 1 14 0
-> 10.1.13.21:0 Masq 1 0 0
lvs1:~#
When you connect for the first time, you are sticked to a real server of
the service you're accessing (HTTP for eg).
The problem is that, after that, if you try to access another virtual
service (LDAP for instance), you get a ICMP port unreacheable, because
you're still sticked on the HTTP Real Server.
lvs1:~# ipvsadm -Lcn
IPVS connection entries
pro expire state source virtual destination
[...]
TCP 01:56 TIME_WAIT xxx.yyy.72.84:33042 xxx.yyy.1.148:80 10.0.20.12:80
IP 02:56 NONE xxx.yyy.72.84:0 0.0.0.0:0 10.0.20.12:0
[...]
lvs1:~#
Why are we sticked for 0.0.0.0:0 ?
We don't have this problem if we don't use fwmarks, but we absolutly
need them.
I hope that someone can help..
Thanks in advance!
Fabien
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
