Tolerant gateway_icmp monitor?

Well, there seems to be some disagreement in how F5 monitors work and what other administrators are claiming.

They claim is the gateway was only down for ~10 seconds. Implying that ping 1 and ping 2 would timeout, but ping 3 would succeed (and be under 1s) But, the F5 failed over, suggesting that it reacted to ping 1 timing out.

And, as evidence they are point to the standby unit, which logged a 10 second outage of its gateway (which is configured not to react when its in standby.) Where I would think that it indicates the outage had been at least 26 seconds.

I don't suppose there's a verbose logging option that can show that the gateway_icmp monitor is working correctly.

Other administrators have also complained similar when the F5 reports that their web server or other application servers are marked down Including servers where they connect to the vip themselves and it eventually responds (after almost a minute...and the monitor timeout was set to 31 seconds....)

But, then everything is always the F5's fault.

Like a few weekends ago....when there was much strangeness going on with the datacenter network (a ticket was logged at 12:40pm about it)....The F5 failed over around 6:25pm...resulted in major service outages lasting for about an hour, when I started poking around on the F5's...where the secondary seemed to finally start moving traffic... which seemed to coincide with doing a config sync of primary to secondary. Wouldn't have thought that there would've been that much difference, but didn't think to check.

What I did see was that there were pools that primary could see one member and second could see the other member....or pool completely down to one and completely up to the other, etc. Suggesting that there was a problem between the two main datacenter switches. primary is connected to switch A, and secondary is connected to switch B.

It was after this disruption that I discovered the problem with how gateway failsafe had been configured....since the secondary was reporting outages, but stayed active.