Hi, we’re having an important issue and I’d really appreciate your help.
We have a Peplink 310 with three dedicated internet circuits (WANs). We’ve configured all WAN’s Health Check Settings to use DNS lookup, using both our own DNS servers and also public DNS servers.
Health check parameters are set as follows:
Timeout: 1 second
Health Check Interval: 5 seconds
Health Retries: 5 seconds
In other words, we’re being as aggressive as possible (lowest timeout and lowest health check interval possible) in trying to detect if a WAN is down, so that it can fail-over to the other WANs as quickly as possible. We deal with live streaming, and having the lowest possible downtime is critical to us.
However, daily usage has shown that when a particular WAN is not completely down (say that it is having 40% packet losses), those Health Check Settings apparently are not enough to actually detect that although it is “UP” (and responds to some DNS requests or pings) it cannot not actually be considerered as “healthy”.
So I’m wondering if there is a way to make the “WAN health check” more efficient than it is today. Apparently one ping every five seconds is an interval too high to detect “erractic” (but not completely unavailable) connectivity. Is there a way to have health check tests every second? Should I be using another better method to check the health of the WANs?
Thanks in advance for your help and expertise.