|
On 7/18/07, Graeme Fowler <graeme@xxxxxxxxxxx> wrote:
>
>
> When you say "the clients are idle", do you really mean "idle"? In LVS
> terms that would be determined by whether or not they exchange any
> traffic. If they don't, then I can understand the connection timing out
> perfectly well; if they do, further work is needed.
Ah. Well, what i mean by idle is that no keyboard/mouse input is sent
through the director to the terminal server. I just assumed that no traffic
was sent during that period.
Can you run tcpdump (selectively!) on one established session which you
> then leave "idle" (your meaning of the word) and see what the session
> does over time?
>
> Thanks
>
> Graeme
Hi,
I did as you suggested and let run windump on the client, and tcpdump on the
director, for a couple of minutes. Mind you that this is with the (ipvsadm)
tcp timeout of 3600, because i can't really afford to have people
complaining about disconnecting sessions. In the weekend i will try to
separate one director and configure it in a test environment. Anyway, that's
in the future. The results:
H:\>windump -i 3 host 192.168.50.201 and port 3389
windump: listening on \Device\NPF_{EED19235-5694-4760-96C9-1258E7815A82}
14:47:46.569908 IP 192.168.50.10.3389 > rpz-d1135.int.rpz.nl.1835: P
3832491663:3832491697(34) ack 942753823 win 63876
14:47:46.784940 IP rpz-d1135.int.rpz.nl.1835 > 192.168.50.10.3389: . ack 34
win 17261
14:54:20.305946 IP 192.168.50.10.3389 > rpz-d1135.int.rpz.nl.1835: P
34:68(34) ack 1 win 63876
14:54:20.419672 IP rpz-d1135.int.rpz.nl.1835 > 192.168.50.10.3389: . ack 68
win 17227
On 15:40 i left the session alone (minimized) to see how idle 'idle' really
is.
>From the director's side (i can't copy paste so i have to type it) :
14:47:27.026979 IP 192.168.50.10.3389 > 192.168.50.201.1835 P
3832491663:3832491697(34) ack 942753823 win 63876
14:47:27.242060 IP 192.168.50.201.1835 > 192.168.50.10.3389: . ack 34 win
17261
14:47:27.242073 IP 192.168.50.201.1835 > 192.168.50.10.3389: . ack 34 win
17261
14:54:00.744508 IP 192.168.50.10.3389 > 192.168.50.201.1835: P 34:68(34) ack
1 win 63876
14:54:00.858363 IP 192.168.50.201.1835 > 192.168.50.10.3389: . ack 68 win
17227
14:54:00.858363 IP 192.168.50.201.1835 > 192.168.50.10.3389: . ack 68 win
17227
(client is rpz-1135.int.rpz.nl / 192.168.50.201 --- director is
192.168.50.10)
So it seems (to me) that there definitely is some form of 'keepalive' that
gets sent every 5 - 10 minutes. Now i couldn't find what the default tcp
timeout values are for LVS, so i guessed 300 seconds (ipvsadm --set 300 300
300). Apparently if i had put 600 seconds there wouldn't be a problem. Am i
seeing this correctly? And by the way, what _are_ the default values? :)
kind regards,
Sebastian.
|
