For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Matt_Randall_64's avatar
Matt_Randall_64
Icon for Nimbostratus rankNimbostratus
Oct 03, 2014

iRule or other mechanism to log when an HTTP request does not get serviced due to timeout?

Greetings!

 

Is anyone aware of any canned iRules or other mechanisms in F5 to detect/log HTTP requests whose requests to a server node are dropped due to TCP idle timeout (e.g. server is not responding within TCP idle timeout)? I'm assuming that the SERVER_CLOSED event may not be triggered, or may be completely orthogonal to the request/response lifecycle (where OneConnect profiles are involved.)

 

application delivery
availability
devops
iRules
LTM

2 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    Oct 03, 2014
    Matt, According to the TCP SERVER_CLOSED wiki entry then "The SERVER_CLOSED event also fires for UDP traffic when the Idle Timeout for the UDP profile is reached" Whilst this doesn't specifcally call out TCP then can we assume the same sympton? Also, according to the following SOL [sol9812](http://support.f5.com/kb/en-us/solutions/public/9000/800/sol9812.html) the BIG-IP sends a TCP-RST to both client and server when the timeout is reached. So SERVER_CLOSED might work here.
  • Mohamed_Lrhazi's avatar
    Mohamed_Lrhazi
    Icon for Altocumulus rankAltocumulus
    Oct 03, 2014

    This might be an option: http://support.f5.com/kb/en-us/solutions/public/13000/200/sol13223.html