LTM Drops TCP Retransmit packets
I cant seem to isolate why the F5 will not send the TCP Retransmit packets back the application servers. I observe the same behavior on several of our F5's on old Software (9.25 , yeah insane!) So in testing I can create a self originated connection from an application server that is behind the F5 via curl.
- The behavior is always the same and looks like this:
- the sender begins to send data to my application server
- at some point there is a packet that does not reach my application server.
- This spawns the application server (receiver) to start sending dup acks (selective ACKS are True)
- the sender will send TCP Retransmit packets which I can see going into the F5 but never make it out (or back to the receiver)
- Eventually the application layer times out the connection and aborts (RST) when we reach the point that the sender cant send any further data without getting an ACK for the retransmit.
I cant figure out why this is occurring as there is no further visibility into the stack in the F5. Also these packets do not fit any of the criteria for drops at either the switch processor or TMM based on what I have read. Anybody have any clue as to what this could possibly be or I am I at the "yeah time to call f5 support". (which of course I cant do with this archaic software version)
FWIW, I do not see this same behavior on newer software.