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

What_Lies_Bene1's avatar
What_Lies_Bene1
Icon for Cirrostratus rankCirrostratus
Aug 08, 2014

Monitor Timeouts

Hi all, I have more monitor questions. I promise not to mention Administrative Partitions ;-)   1) Lets say my timeout is 16s. Probe 1 is sent at 0s, probe 2 at 5s. Before probe 3 is sent at 10s a...
application delivery
availability
LTM
management
JG's avatar
JG
Icon for Cumulonimbus rankCumulonimbus
Aug 09, 2014

As I understand it, the timeout period starts as the first probe is sent out. If the probe succeeds right away, the timeout period is over, the pool member is marked as up, and a new generic "interval" period, or an "up" interval if defined, starts.

 

If the first probe fails right away, a second probe is sent after the defined generic interval; if the first probe hangs, a second probe is also sent after the defined interval period. More probes are sent in this way until the defined timeout period is over, at which time the system will kill all existing connections used by the probes and mark the pool member down.

 

It would be good if somebody from F5 can confirm / deny this is how it works, and in the latter case, provide a detailed description.