OSPF ignoring Priority?

Hi,

Running ROS 6.44.5 long term on CHR, trying to set it as a DR server but seems OSPF is ignoring the Priority, i.e. on the interface, I set Priority for the device I want to be the DR to 255 and others are set to 1, but it stays as BDR / Backup?

Disabled Instances, Networks, rebooted device, no changes.

How do I set device to be DR?

Have you logged into the device that is elected as the DR and verified that it is set for 1 and not 255 as the priority?

Note: If the election is already done, adding a new router with 255 is not going to automatically trigger a new election (at least not in my experience).

DR priority is set as 1. I restarted the device which surely should start the election process?

You restarted the device currently acting as the DR?

I’m not sure whether a brief outage of the DR will result in a re-election. It may require an outage of both the DR and BDR to trigger a re-election.

Apologies, made a typo in my previous post.

The BDR is set as 1 and DR set as 255. Surely restart of just one device of these that formed adjacency should be enough to start election process. Else if the DR goes down and comes back up again, it will stay BDR?

I am pretty sure standard OSPF behavior is to only trigger a re-election if both the DR and BDR go down at the same time. I believe on Cisco routers you have to restart the OSPF process entirely to get them to re-evaluate the DR vs BDR, if it is just interface down and up the router will prefer what it had before. I’m guessing MikroTik is similar.

Edit: It might be that it is not brought down for enough time - if the device is down for less than the dead interval ie. <40s (by default) it may not trigger re-election. So it might be that you need to ensure the DR is down for at least 40 seconds in order for the BDR to get promoted.