Gateway monitor spams email inboxes.. WHY?!
-
I have gateway monitoring on in this latest version of the 64bit firewall.
However, it seems that it is email us every time it detects the gateway has met the failure criteria instead on ONE email for a down state and then an email when it is resolved.
In other words, if we have it set to test the link every 30 seconds, we get an email every 30 seconds while the link is down.
This is killing our in boxes, but we need link monitoring running and we need email alerts.
help!
-
Yeah, we get that too. Sadly still in 2.2 - could anyone please take a look at this?
-
Go to the System - Routing - Gateways, click "e" and under Advanced sanitize the apinger thing there. I mean, set everything way more relaxed than the insane defaults. (Latency thresholds, Packet loss, Probe interval, Down… etc.)
Really hope this thing gets rewritten or replaced ASAP.
-
Can you recommend good settings? We want a fast switch over to our other WAN connection in case of gateway failure.
-
Hmmm, not really for "want a fast switch over". First you need to figure out what's a genuine broken connection and what's just apinger being overzealous and doing more harm than good. (I.e., see the logs and try to find some patterns about what's still "normal" regarding delay/packet loss and when the WAN should really be flipped.) Needs local fiddling till you get some reasonable compromise; if things are flipping too often, I'd imagine this just disrupts connectivity in general, rending the failover to backup WAN more or less useless.
-
Really hope this thing gets rewritten or replaced ASAP.
We're looking at rewriting it. I haven't found an alternative that's anywhere near complete as a drop-in replacement, though if anyone knows of something, suggestions would be appreciated.
Hmmm, not really for "want a fast switch over". First you need to figure out what's a genuine broken connection and what's just apinger being overzealous and doing more harm than good. (I.e., see the logs and try to find some patterns about what's still "normal" regarding delay/packet loss and when the WAN should really be flipped.) Needs local fiddling till you get some reasonable compromise; if things are flipping too often, I'd imagine this just disrupts connectivity in general, rending the failover to backup WAN more or less useless.
Yes, this. You don't want it to be really sensitive (where "really sensitive" is relative to your connection's quality), as flapping back and forth across WANs unnecessarily will cause issues.