Running a recent snapshot (a few days ago) ospfd seems to have a problem with correctly joining an ospf area unless it's router-priority is 0 or higher than the current BDR. Ospfd is here connected to our ospf backbone wich is a mix of openbsd boxes running gated, Huawei 1760's and Cisco's running various versions of IOS. The first output below is after ospfd has been running with a router-priority of 1 for a couple of minutes, the second one is after a very quick restart (ie less than the dead time). It seems it get stuck in a state and doesnt proceed until it has been restarded. It's notable that on the other routers in the backbone the ospfd box appears as a full 2way/drother member while ospfd itself seems to think it's still in exstart. The output also states that the BDR is in FULL/DROTHER but sometimes it's the DR that shows up in that state. It's never both at the same time though.
# ospfctl sh n ID Pri State DeadTime Address Interface 203.65.245.3 1 EXSTART/DROTHER 00:00:32 203.65.245.3 sis0 203.65.245.6 10 FULL/DR 00:00:31 203.65.245.6 sis0 203.65.245.5 1 EXSTART/DROTHER 00:00:39 203.65.245.5 sis0 203.65.245.4 0 EXSTART/DROTHER 00:00:35 203.65.245.4 sis0 203.65.245.2 9 FULL/DROTHER 00:00:36 203.65.245.2 sis0 203.65.245.12 0 EXSTART/DROTHER 00:00:32 203.65.245.12 sis0 203.65.245.9 1 EXSTART/DROTHER 00:00:35 203.65.245.9 sis0 203.65.245.7 0 EXSTART/DROTHER 00:00:33 203.65.245.7 sis0 203.65.245.1 5 EXSTART/DROTHER 00:00:33 203.65.245.1 sis0 # ospfctl sh n ID Pri State DeadTime Address Interface 203.65.245.2 9 FULL/BACKUP 00:00:31 203.65.245.2 sis0 203.65.245.9 1 2-WAY/DROTHER 00:00:30 203.65.245.9 sis0 203.65.245.12 0 2-WAY/DROTHER 00:00:39 203.65.245.12 sis0 203.65.245.7 0 2-WAY/DROTHER 00:00:39 203.65.245.7 sis0 203.65.245.1 5 2-WAY/DROTHER 00:00:39 203.65.245.1 sis0 203.65.245.3 1 2-WAY/DROTHER 00:00:37 203.65.245.3 sis0 203.65.245.6 10 FULL/DR 00:00:36 203.65.245.6 sis0 203.65.245.5 1 2-WAY/DROTHER 00:00:34 203.65.245.5 sis0 203.65.245.4 0 2-WAY/DROTHER 00:00:32 203.65.245.4 sis0 --- Lars Hansson