|
Good day,
recently i came across into the tunneling method, i did a simple setup and
have noticed that the output of "ipvsadm -Ln" looks a bit strange.
This is my test setup:
# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.1.218:3128 wlc
-> 192.168.88.191:3128 Tunnel 100 0 0
-> 192.168.88.192:3128 Tunnel 100 0 0
-> 192.168.88.193:3128 Tunnel 100 0 0
VIP 10.0.1.218 has three RS (proxies) configured using a tunnel,
this is working nice so far.
When sending a few requests to 10.0.1.218 then i'm getting this:
# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.1.218:3128 wlc
-> 192.168.88.191:3128 Tunnel 100 0 3
-> 192.168.88.192:3128 Tunnel 100 0 3
-> 192.168.88.193:3128 Tunnel 100 0 3
I'm wondering about ActiveConn which is being empty but it should not.
See the connections:
lennytest:~# ipvsadm -L -c -n
IPVS connection entries
pro expire state source virtual destination
TCP 14:26 ESTABLISHED 192.168.40.96:1177 10.0.1.218:3128
192.168.88.193:3128
TCP 14:21 ESTABLISHED 192.168.40.96:1187 10.0.1.218:3128
192.168.88.191:3128
TCP 01:23 FIN_WAIT 192.168.40.96:1186 10.0.1.218:3128
192.168.88.193:3128
TCP 01:21 FIN_WAIT 192.168.40.96:1182 10.0.1.218:3128
192.168.88.191:3128
TCP 01:20 FIN_WAIT 192.168.40.96:1179 10.0.1.218:3128
192.168.88.192:3128
TCP 01:20 FIN_WAIT 192.168.40.96:1175 10.0.1.218:3128
192.168.88.191:3128
TCP 01:21 FIN_WAIT 192.168.40.96:1181 10.0.1.218:3128
192.168.88.191:3128
TCP 14:26 ESTABLISHED 192.168.40.96:1178 10.0.1.218:3128
192.168.88.191:3128
TCP 01:20 FIN_WAIT 192.168.40.96:1180 10.0.1.218:3128
192.168.88.193:3128
TCP 01:21 FIN_WAIT 192.168.40.96:1184 10.0.1.218:3128
192.168.88.193:3128
TCP 01:21 FIN_WAIT 192.168.40.96:1183 10.0.1.218:3128
192.168.88.192:3128
TCP 01:21 FIN_WAIT 192.168.40.96:1176 10.0.1.218:3128
192.168.88.192:3128
TCP 14:25 ESTABLISHED 192.168.40.96:1185 10.0.1.218:3128
192.168.88.192:3128
Waiting a bit and run again ...
# ipvsadm -L -n
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.1.218:3128 wlc
-> 192.168.88.191:3128 Tunnel 100 0 3
-> 192.168.88.192:3128 Tunnel 100 0 3
-> 192.168.88.193:3128 Tunnel 100 0 3
# ipvsadm -L -c -n
IPVS connection entries
pro expire state source virtual destination
TCP 00:00 FIN_WAIT 192.168.40.96:1186 10.0.1.218:3128
192.168.88.193:3128
The amount of established connections don't show up in ipvsadm but they
should,
i'm successfully using other methods such as DR where the display works
well but
don't understand the above. Maybe this is a little bug?
The ActiveConn information is quite important to me since i run some
management
applications on this information.
The box is a standard debian squeeze,
# uname -a
Linux squeezetest 2.6.32-5-686 #1 SMP Wed Jan 11 12:29:30 UTC 2012 i686
GNU/Linux
Cheers
Matt.
_______________________________________________
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
|
