|
On 16/07/06, Robinson, Eric <eric.robinson@xxxxxxxxxx> wrote:
Okay, but...
[root@lb1 ~]# ipvsadm -l
IP Virtual Server version 1.2.0 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn
InActConn
TCP 192.168.5.100:ftp rr
-> 192.168.10.61:ftp Masq 0 0 0
[root@lb1 ~]#
Doesn't that show that ipvsadm has been told to do something?
('scuse me jumping late, and in in the middle here.) We have FTP
working through LVSs for a couple of systems though it is a little
inconsistent for some users though that could be network
equipment/clients their end or some combination of that and LVS.
There's no weighting for your FTP virtual server in the ipvsadm output
listed above. On a server we have configured for FTP we have a
weighting specified, even for round-robin configured virtual
servers...
[root@manlvs1b ~]# ipvsadm -ln | grep :21
TCP 172.16.28.17:21 rr
-> 192.168.24.218:21 Masq 1 0 0
TCP 172.16.28.16:21 rr
-> 192.168.24.30:21 Masq 1 0 0
TCP 172.16.28.10:21 wlc
-> 192.168.24.211:21 Masq 1 0 0
TCP 172.16.28.15:21 rr
-> 192.168.24.211:21 Masq 1 0 0
TCP 172.16.28.13:21 rr
-> 192.168.24.11:21 Masq 1 0 0
The man page has the following to say about weighting...
-w, --weight weight
Weight is an integer specifying the capacity of a server rela-
tive to the others in the pool. The valid values of weight are
0 through to 65535. The default is 1. Quiescent servers are
specified with a weight of zero. A quiescent server will
receive no new jobs but still serve the existing jobs, for all
scheduling algorithms distributed with the Linux Virtual
Server.
I have found it's necessary to have the helper module (ip_vs_ftp)
loaded, whether for active or passive connections.
[root@manlvs1b ~]# lsmod | grep ip_vs
ip_vs_rr 1729 16
ip_vs_wlc 1857 8
ip_vs_ftp 5577 0
ip_vs 86369 30 ip_vs_rr,ip_vs_wlc,ip_vs_ftp
Will.
|
