Nimbostratus
Does anyone know of a way to configure a monitor or the server so that if the health monitor fails x amount of times, then the server is marked as offline? At the moment, if the monitor fails on 1 check, then our server is marked as down, which is not desirable.
By the way, I am running F5 GTM 9.4.7.
Thanks,
goulin
Nimbostratus
I guess I should be more specific - we are currently using the http, https and tcp checks, and there does not seem to be the options that there are with the icmp health monitor:
Probe Interval 1 seconds
Probe Timeout 5 seconds
Probe Attempts 3
Which suggests that it would do something like what I am after.
Cirrostratus
Take a look at this post and reply here if you have any questions. It's on LTM monitors, but the concepts still apply to GTM probes. The only difference is the probe timeout setting in GTM. With the probe timeout setting, you can specify how long the monitoring daemon should wait before considering a probe attempt a failure.
HTTP [monitor] timeouts help
http://devcentral.f5.com/Default.aspx?tabid=53&forumid=32&view=topic&postid=59956
Aaron
Nimbostratus
I have had a look at the post and whilst it makes sense, I can't seem to get what I want working. Basically, I have setup a custom Monitor setup on my GTM with the following parameters:
Interval: 15
Timeout: 81
Probe Timeout: 5
So I would expect that the probe would run every 15 seconds, and that 5 consecutive probes would need to be missed before the Server was marked as down (5 x 15 = 75 + 5 for the probe timeout).
However, when I tested this, the GTM was correctly sending Probes every 15 seconds, but the Server was marked as down after the first missed probe.
Am I missing something? GTM version is 9.4.7.
NimbostratusI have not seen a reply here and I have the same inquiry. Which one takes precedence for GTM health monitors. The timeout setting or the probe timeout setting? This item is not very clear on the F5 documents posted on their site.