Hi Julian,
We do not have an FTP service on the same VIP as an HTTP with persistance. Here
is the full output from ipvsadm. All of our services are on different VIP's.
# ipvsadm -l -n
IP Virtual Server version 1.0.11 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.99.23.64:80 wlc persistent 300
-> 10.99.22.58:80 Masq 1 8 0
-> 10.99.22.53:80 Masq 1 8 6
-> 10.99.22.215:80 Masq 1 8 2
TCP 10.99.23.54:80 wlc persistent 300
TCP 10.99.23.51:80 wlc persistent 300
-> 10.99.22.199:80 Masq 1 30 1
-> 10.99.22.197:80 Masq 1 26 2
TCP 10.99.23.98:5061 wlc
-> 10.99.22.252:5061 Masq 1 0 0
-> 10.99.22.251:5061 Masq 1 0 0
The following appears in the output when the FTP service is added (currently
removed due to the problems it is causing).
TCP 10.99.23.57:21 wlc
-> 10.99.22.208:21 Masq 1 0 0
-> 10.99.22.207:21 Masq 1 0 0
Unfortunately it does not sound like your patch would solve the problem in this
case. Do you have any other ideas?
Jari
|