OSPF broadcast mode wasn't designed for a hub and spoke topology. It was designed only for full mesh topologies - or at least one where a DR and BDR can be manually selected. Of course, at a minimum they both have to have full connectivity to each other and every other router in the network.
So your phantom BDR is probably trying to elect itself as the BDR, not knowing that someone else won the election. Hmmm...... I'd get some lawyers involved. Cisco Nuts wrote: > > Hello,In an OSPF broadcast mode in a FR hub-and-spoke topology, > the spoke > router that is the DROTHER shows up as being in a BDR state > when issuing > the #sh ip os int s0 command? Should it say Drother state or > BDR state? RTB#Process > ID 100, Router ID 5.5.5.5, Network Type BROADCAST, Cost: 64 > Transmit Delay is 1 sec, State BDR, Priority 1 The hub router > lists it > as being a Drother router:RTA#sh ip os neiNeighbor ID Pri > State Dead Time Address Interface > 7.7.7.7 1 FULL/BDR 00:00:31 > 192.168.10.243 Serial0 > 5.5.5.5 1 FULL/DROTHER 00:00:39 > 192.168.10.242 Serial0 The > BDR router shows up as being in a BDR state which is > correct:RTC# Process > ID 100, Router ID 7.7.7.7, Network Type BROADCAST, Cost: 64 > Transmit Delay is 1 sec, State BDR, Priority 1 Now when I > configure the > priorities on the spoke routers as 0, then they correctly show > us as > being in a Drother state:RTB# Process ID 100, Router ID > 5.5.5.5, Network > Type BROADCAST, Cost: 64 > Transmit Delay is 1 sec, State DROTHER, Priority 0 Any reason > for this > behavior or does it just work this way?? Thank you.[FORM NOT > SHOWN] > > ------------------------------------------------------------------------ > > Join the worlds largest e-mail service with MSN Hotmail. Click > Here > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=33783&t=33640 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
