Still Having Issues with Failover

Routers
1

Have been using the Route10 for a couple of weeks now and still having issues with failover, and even more importantly - failback. I’ve read through most, if not all the recent failover threads on this board already.

I’ve got 2gig fiber into WAN1 with a metric of 1 as my primary internet. My backup internet is 100mbps Verizon Home Wireless with a metric of 2. Will connect to Fiber (WAN1) out of the gate and then a few minutes later (with no outage), it will flip over to the Home Wireless (WAN2). Never goes back unless I disconnect WAN2 altogether. Then if I plug WAN2 back in, it will connect to WAN1 for a few minutes then over to WAN2. Constant circle. Right now, I’ve got WAN2 unplugged, but really want to get failover working. Has anyone cracked this nut that can help out?

2

Diceman,

I don’t see the same issue, did you change the default monitor hosts by chance?

I’ve got Frontier Fiber on SFP+, and Comcast on a copper port. I’ve got my fiber metric at 10, and my comcast metric at 20. The only odd thing I’ve found is in the rare case the fiber goes down (mostly maintenance related) I may have to power cycle to get some flows back on Frontier - but I don’t have an issue where it switches unexpectedly,

If you haven’t changed the monitor type, try to copy my metrics and see if it makes any difference?

-Joe

3

I’ve set mine up identically - let’s see how it goes. I know I had modified the monitor hosts, but I’ve left it at default now. Really appreciate the assist!

4

Failover was working for awhile, but not failback. Then router went stupid and I rebooted - now it will connect to Fiber for a short bit, then flip over to backup. I’m losing patience with this router. I’m pretty tolerant with technology, but I need something a bit more reliable.

5

I have another report regarding the failback that I’m looking into. In the meantime, I would recommend to set the metrics to equal value to operate in load balancing mode instead. This will at least keep your connections alive without the frustrating experience of failback not triggering.

1 Like
6

Thanks Josh!

1 Like