Forum Discussion
Michael_Yates
Jul 23, 2013Nimbostratus
Even with Cookie Persistance you are still running a large number of Client and Server Side connections and will run into the same problem through the configuration of your TCP Profiles with a Persistence Requirement of that size. If your TCP Profiles are configured for anything less that your applciation timeout the F5 LTM will send a TCP Reset in both directions and any reconnections (regardless of if they are persisted to the same server will be new connections...if this is not a problem and the applciation is truly stateless...then no persistence should be required at all).
See SOL9812: Overview of BIG-IP TCP RST behavior for more information on the TCP Resets.
Specifically under Profiles (Reset on Timeout is active by default):
Protocol profile idle timeouts (if the Reset On Timeout setting is enabled)
The BIG-IP system tracks connection flows by adding an entry to the connection table. When the connection flow becomes idle, the BIG-IP system starts a timer and closes the connection with a TCP RST packet when the connection reaches the idle session timeout. The TCP RST packet is sent on the client and server side of the connection, and the source IP address of the reset is the relevant virtual server IP address.