LTM Throttling Proxied Connections in 20 second intervals

Thanks for replying! We do have an HTTP profile but I'm not sure what you mean by adding it to a vip (did you mean vs?). It uses the default http parent profile and the only option we've enabled is "Insert X-Forwared-For". I dug around in there but can't find anything that would limit each proxied message to exactly 20 seconds.

Hi Mike

I have never seen any material from f5 that indicates a delay of 20 seconds per packet, and yes I meant vs. a standard vs with a http profile will result the vs will complete the 3 way handshake with the client and at wait for a http request from the client before opening up the connection on the server side. but even that will surely not cause a 20 seconds delay.

Like I mentioned you can try to do a tcpdump on the f5 with the -p filter does will allow you analyze traffic from both client to vs and f5 to server. you will then be able to see when the f5 receive the 1st syn or http request and the time difference since the request is made to backend server.

Thanks Kevin, I will keep trying with the tcpdump and your suggested settings. It's a bit hard to troubleshoot because we can't trigger the event due to the data coming in from an external source on a random schedule. It's definitely odd because it "should" fire everything to the backend as soon as it received but you could set your watch to the 20 second interval, it's that precise. Was hoping it was just a 20s congestion queue setting somewhere I haven't found yet. Thanks for your help!