I just experienced different behaviour in OSPF - RouterOS vs. Cisco iOS according to GNS3 simulation.
I have few routers connected to switch. They are running OSPF broadcast network type with DR/BDR election. With RouterOS when DR router goes down, all other routers flush route table for dead-interval and then reinitialize. All these routers have working BDR, why this route flap?
With Cisco iOS in the same topology no route flap happen.
I just proved this issue with real devices - simple 4 routers star with switch in the middle.
R1 - PRIO: 200 - 192.168.0.1/24 - LOOPBACK: 192.168.1.1
R2 - PRIO: 190 - 192.168.0.2/24 - LOOPBACK: 192.168.2.1
R3 - PRIO: 180 - 192.168.0.3/24 - LOOPBACK: 192.168.3.1
R4 - PRIO: 170 - 192.168.0.4/24 - LOOPBACK: 192.168.4.1
Tested with default timers (hello 10s, dead 40s) and custom timers (hello 1s, dead 5s).
R1 is DR, R2 BDR. From R4 I’m pinging R2 loopback. Then I disconnect R1 and wait until dead-interval reached. R2 becomes DR, R3 BDR. Attaching screen record: https://youtu.be/jizkX_4a-CI
In GNS3 I had little bigger simulation with the same results. Attaching screenshot.
Well, quite a bit late. I am testing OSPF and BGP routing in new v7 and updating my training documents for v7. So I tried this and yes, routes flaps in v6 AND routes still flaps in v7 after DR goes down.
[Edited]
But, packets are lost in transit for several seconds in the change from BDR to DR. I’m testing it to verify if it is (still) a bug.
[/Edited]
[Edited 2]
Well, after deeper tests, the BUG is still present in OSPF for RouterOS v.7.1. Changing from BDR to DR is not always smooth. Sometimes the routes don’t flap and sometimes they do.
If the routes don’t flap, a continous PING between is broken for 5 seconds. If the routes flap, it takes 10 seconds.
[/Edited 2]