v7.1.1 Failover Routing Invalid

RouterOS General
1

Hi
I had a working Failover Setup with RouterOS 6 (no Script, no Firewall Rules).
Over a year ago I found this solution somewhere and used it without understanding how it actually works.
Changed to 7.1.1 (because of the Rest API) an most of my Routes are now marked as invalid and/or unreachable
This is my setup:

/ip route
add comment="Default Route WAN1 -> Virtual Hop (Cost 1)" distance=1 gateway=10.231.1.1
add comment="Default Route WAN2  -> Virtual Hop (Cost 2)" distance=2 gateway=10.232.2.2
add comment="Route WAN1 CheckHost 1 (Google DNS 1)" distance=1 dst-address=8.8.8.8/32 gateway=130.181.92.97 scope=10
add comment="Route WAN1 CheckHost 2 (OpenDNS 1)" distance=1 dst-address=208.67.220.220/32 gateway=130.181.92.97 scope=10
add comment="Route WAN2 CheckHost 1 (GoogleDNS2)" distance=1 dst-address=8.8.4.4/32 gateway=192.168.8.1 scope=10
add comment="Route WAN2 CheckHost 2 (OpenDNS 2)" distance=1 dst-address=208.67.222.222/32 gateway=192.168.8.1 scope=10
add check-gateway=ping comment="Virtual Hop WAN 1 Checkhost1" distance=1 dst-address=10.231.1.1/32 gateway=8.8.8.8 scope=10
add check-gateway=ping comment="Virtual Hop WAN1 Checkhost 2" distance=1 dst-address=10.231.1.1/32 gateway=208.67.220.220 scope=10
add check-gateway=ping comment="Virtual Hop WAN 2 Checkhost1" distance=1 dst-address=10.232.2.2/32 gateway=8.8.4.4 scope=10
add check-gateway=ping comment="Virtual Hop WAN 2 Checkhost2" distance=1 dst-address=10.232.2.2/32 gateway=208.67.222.222 scope=10

Hopefully somebody with RouterOS 7 knowledge can tell me what to change?

2

In Ros v7.1.1 you need to make sure that for those affected invalid routes target-scope is set with value greater than scope (even just +1 it’s enough).
By doing so your setup will return valid routes.

3

accarda thanks for the reply. I had some days off over new year.
I was tinkering with the rules changing scopes and target scopes (like a monkey pressing buttons in a space ship :slight_smile: ), but there were always invalid routes.
Then I disabled all the route in winbox and enabled the all together again with one klick. No more Invalid rules and the backup route with distance 2 is not active (blue) again.
All back to normal like in ROS6.
NoFailOver.png
But target-scope isn’t greater than scope ??
Unplugging the cable modem switches over to the LTE Backup and I still have internet access, Yeaahhhhhh :smiley:
But the route list in winbox looks weird:
FailOver.png
Some routes for the default ISP are now invalid, the backup route is still shown as not active, but it works somehow?
Plugging the cable back into the modem and everything is back to normal.

Is this how it is supposed to work or did I “Frankensteined” myself a Config that will break with the next update?