Forum Discussion
InquisitiveMai
Cirrostratus
CirrostratusTCP Session Keepalive and Idle timeout
I have few questions
- During the TCP session 3 way handshake , how do we decide the TCP keepalive and timeout. Does it depend on if the client or server?
- Do the same idle timeout/Keepalive values get carried out when a client-->F5 VIP and F5 Self IP --> Pool member?
- In packet capture, I see TCP len 0 for a ACK from pool member to self IP and then a RST from F5 Self IP to the Pool member with TCP timeout of 300.09sec, Does it mean the pool member says there is no more data to send and the F5 self IP waits for 300 sec(default Idle Timeout) and send RST
- zamroni777
Nacreous
the vserver tcp behavior is determined by client side and server side tcp profiles of each virtual server.
https://my.f5.com/manage/s/article/K13004262
CA_ValliMVP
- the idle values are local to the BIG-IP, and are used to determine when certain entries can be removed from the connection table. they depend from TCP profile settings and -since F5 is a full proxy- can be different for client- and server- side.
- this behavior can change, depending on configuration. in the Virtual Server configuration, you can set up which TCP profile should be use for each connection, and in current BIGIP versions "server-side TCP profle" usually defaults to "use the same as client-side". so if you configured your VS to use the same TCP profile for both client- and server- side connection, yes they will be the same
- yes, this is most likely a RST sent by BIG-IP to close client connection, as default idle timer for TCP profile is 300s
