Forum Discussion
LTM Throttling Proxied Connections in 20 second intervals
- Oct 18, 2018
It turns out this was a faulty OSCP server upstream that was causing certificate checking to fail. The solution was to remove OSCP from our APM access policy until we can find another, better solution. Thanks everyone for the help!
Maybe a HTTP profile added to vip it will wait for at least one http message from the client before opening the server side connection.
do a tcpdump with the -p filter to capture both sides of the connection client to vip - f5 to server.
example "tcpdump -nni 0.0:nnnp -s 0 host X.X.X.X and host X.X.X.X"
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.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com