OSPF instance disabled, but OSPF populates routing table

RouterOS Forwarding Protocols
1

I've been having weird OSPF issues on one of our backup routers, so I turned off the OSPF instances. However, ospf routes still seem to be populating the routing table. I dont see this with any other routers. Has anyone seen this before

[admin@DunHubRT02] > /routing/ospf/instance pri
Flags: X - disabled, I - inactive
0 X name="default-v2" version=2 vrf=main router-id=10.10.15.12 redistribute=connected,static,ospf,vpn,dhcp,modem

1 X name="default-v3" version=3 vrf=main router-id=main

[admin@DunHubRT02] > ip route pri
Flags: D - DYNAMIC; I - INACTIVE, A - ACTIVE; c - CONNECT, s - STATIC, o - OSPF; H - HW-OFFLOADED; + - ECMP
Columns: DST-ADDRESS, GATEWAY, DISTANCE

DST-ADDRESS GATEWAY DISTANCE

0 As 0.0.0.0/0 10.2.0.193 1
DAo + 10.2.0.48/30 10.10.15.1%vlan40 110
DAo + 10.2.0.48/30 10.123.80.1%vlan44 110
DAo + 10.2.0.48/30 10.123.90.73%vlan46 110
DAo + 10.2.0.48/30 10.123.90.69%vlan47 110
DAo + 10.2.0.48/30 10.123.90.185%vlan89 110
DAo + 10.2.0.52/30 10.10.15.1%vlan40 110
DAo + 10.2.0.52/30 10.123.80.1%vlan44 110
DAo + 10.2.0.52/30 10.123.90.73%vlan46 110
DAo + 10.2.0.52/30 10.123.90.69%vlan47 110
DAo + 10.2.0.52/30 10.123.90.185%vlan89 110
DAo + 10.2.0.56/30 10.10.15.1%vlan40 110
DAo + 10.2.0.56/30 10.123.80.1%vlan44 110
DAo + 10.2.0.56/30 10.123.90.73%vlan46 110
DAo + 10.2.0.56/30 10.123.90.69%vlan47 110
DAo + 10.2.0.56/30 10.123.90.185%vlan89 110
DAo + 10.2.0.60/30 10.10.15.1%vlan40 110
DAo + 10.2.0.60/30 10.123.80.1%vlan44 110
DAo + 10.2.0.60/30 10.123.90.73%vlan46 110
DAo + 10.2.0.60/30 10.123.90.69%vlan47 110
DAo + 10.2.0.60/30 10.123.90.185%vlan89 110
DAo + 10.2.0.64/30 10.10.15.1%vlan40 110
DAo + 10.2.0.64/30 10.123.80.1%vlan44 110
DAo + 10.2.0.64/30 10.123.90.73%vlan46 110
DAo + 10.2.0.64/30 10.123.90.69%vlan47 110
DAo + 10.2.0.64/30 10.123.90.185%vlan89 110

any help to understand this would be appreciated

Jonathan

2

After upgrading to 7.13, I encountered the same OSPF issue. Even though the interface was shut down, the routing entries still existed, and the same entry was added multiple times in the routing table and marked as DAo+(ecmp). My total number of routing table entries was only 700, and over time, the total number would accumulate to over 10000 (those same entries would be added infinitely). Moreover, when there were multiple paths, I set different costs for different paths, but this did not work. All of them were still activated and marked as DAo+

[admin@R6] > int  pr where name~"l2tp"
Flags: X - DISABLED
Columns: NAME, TYPE
#   NAME                   TYPE    
0 X to-bb-cloud-1111-l2tp  l2tp-out
1 X to-bb-cloud-1112-l2tp  l2tp-out
2 X to-bb-cloud-1113-l2tp  l2tp-out
3 X to-bb-cloud-1114-l2tp  l2tp-out
4 X to-bb-cloud-1115-l2tp  l2tp-out
[admin@R6] > ip rou pr where dst-address in 10.199.0.0/16                                                                    
Flags: D - DYNAMIC; I - INACTIVE, A - ACTIVE; o - OSPF; H - HW-OFFLOADED; + - ECMP        
Columns: DST-ADDRESS, GATEWAY, DISTANCE
      DST-ADDRESS      GATEWAY                             DISTANCE
DAo + 10.199.0.0/16    172.21.192.254%vlan2600                  110
DIoH  10.199.0.0/16    100.64.133.1%to-bb-cloud-1112-l2tp       110
DAo + 10.199.0.0/16    172.21.192.254%vlan2600                  110
DIoH  10.199.0.0/16    100.64.129.1%to-bb-cloud-1111-l2tp       110
DAo + 10.199.0.0/16    172.21.192.254%vlan2600                  110
DAo + 10.199.127.0/30  172.21.192.254%vlan2600                  110
DIoH  10.199.127.0/30  100.64.133.1%to-bb-cloud-1112-l2tp       110
DAo + 10.199.127.0/30  172.21.192.254%vlan2600                  110
DIoH  10.199.127.0/30  100.64.129.1%to-bb-cloud-1111-l2tp       110
DAo + 10.199.127.0/30  172.21.192.254%vlan2600                  110
DAo + 10.199.127.8/30  172.21.192.254%vlan2600                  110
DIoH  10.199.127.8/30  100.64.133.1%to-bb-cloud-1112-l2tp       110
DAo + 10.199.127.8/30  172.21.192.254%vlan2600                  110
DIoH  10.199.127.8/30  100.64.129.1%to-bb-cloud-1111-l2tp       110
DAo + 10.199.127.8/30  172.21.192.254%vlan2600                  110

L2TP-client was disabled,but the routing entries still existed , The same entry has been added multiple times

3

upgrading to 7.13.4
The problem has been resolved

4

I encountered same behaviour with RIP. It looked like RIP process was crashing each time new set of entries appeared.

routing/stats/process/print

would indicate these crashes by changed PID of corresponding process.

I was fighting this problem with RIP and downgrades from 7.13.5 down to 7.10.2 did not brought any changes. I gave up and switched to OSPF - which looks to be working OK for now on 7.10.2. It is good to know that it might work OK on 7.13.4 (and hopefully on 7.13.5) as well…

5

The same problem has arisen again on 7.13.4
The routing table has been filled with a large amount of abnormal ECMP data
DIo 10.195.154.0/24 100.64.129.1%to… 110
DAo + 10.195.154.0/24 172.21.192.254%… 110
DIo 10.195.154.0/24 100.64.129.1%to… 110
DAo + 10.195.154.0/24 172.21.192.254%… 110
DIo 10.195.154.0/24 100.64.129.1%to… 110
DAo + 10.195.154.0/24 172.21.192.254%… 110
DIo 10.195.154.0/24 100.64.129.1%to… 110
DAo + 10.195.154.0/24 172.21.192.254%… 110
DIo 10.195.155.0/30 100.64.129.1%to… 110
DAo + 10.195.155.0/30 172.21.192.254%… 110
DIo 10.195.155.0/30 100.64.129.1%to… 110
DAo + 10.195.155.0/30 172.21.192.254%… 110
DIo 10.195.155.0/30 100.64.129.1%to… 110
DAo + 10.195.155.0/30 172.21.192.254%… 110
DIo 10.195.155.0/30 100.64.129.1%to… 110
DAo + 10.195.155.0/30 172.21.192.254%… 110
DIo 10.195.156.254/32 100.64.129.1%to… 110
DAo + 10.195.156.254/32 172.21.192.254%… 110
DIo 10.195.156.254/32 100.64.129.1%to… 110
DAo + 10.195.156.254/32 172.21.192.254%… 110
DIo 10.195.156.254/32 100.64.129.1%to… 110
DAo + 10.195.156.254/32 172.21.192.254%… 110
DIo 10.195.156.254/32 100.64.129.1%to… 110
– [Q quit|D dump|up|down]