Show Posts
1
17.7 Legacy Series / Persistent apinger issues
« on: October 21, 2017, 02:32:43 am »
Hello!
I have two pppoe connections, one set as a failover (tier 2, much slower than tier 1). Gateway monitoring interval is set to 10s on each gateway. I constantly get incorrect values for the gateway monitoring, which I've come to find out through reading on this forum - is through apinger. Attached is a typical result for the gateway monitoring value. If I ping directly, it's always a much different value. Monitoring is broken for both interfaces; both will read strange values at any given time. This leads to gateway switchovers quite frequently and a logfile filled with apinger alarms. After I restart it, the value seems to stay close to reality for a few minutes, then goes rogue again. Is there any way to fix this? I saw a post where someone had a cron job that restarted apinger every 60s, but I feel like there has to be a better way.
I have two pppoe connections, one set as a failover (tier 2, much slower than tier 1). Gateway monitoring interval is set to 10s on each gateway. I constantly get incorrect values for the gateway monitoring, which I've come to find out through reading on this forum - is through apinger. Attached is a typical result for the gateway monitoring value. If I ping directly, it's always a much different value. Monitoring is broken for both interfaces; both will read strange values at any given time. This leads to gateway switchovers quite frequently and a logfile filled with apinger alarms. After I restart it, the value seems to stay close to reality for a few minutes, then goes rogue again. Is there any way to fix this? I saw a post where someone had a cron job that restarted apinger every 60s, but I feel like there has to be a better way.