- Bronze, 100 points or more
I already posted this in the "Training" forum, figuring it was a question from someone who could stand a little more "Training" on this subject, but that forum doesn't seem too active. Here it is:
Four routers are connected via token-ring in Area 0. RID 220.127.116.11 is DR, 18.104.22.168 is BDR. DRothers are 22.214.171.124 and 126.96.36.199.
I powered 188.8.131.52 down. Switched it right the hell off. Felt no guilt; would do it again.
I was logged on, console-like, to Router G (184.108.40.206) with OSPF Adjacency debugging activated, and here's part of what I saw:
01:08:28: OSPF: 220.127.116.11 address 10.4.4.5 on TokenRing0 is dead
01:08:28: OSPF: 18.104.22.168 address 10.4.4.5 on TokenRing0 is dead, state DOWN
01:08:28: %OSPF-5-ADJCHG: Process 100, Nbr 22.214.171.124 on TokenRing0 from FULL to
DOWN, Neighbor Down: Dead timer expired
01:08:28: OSPF: Neighbor change Event on interface TokenRing0
01:08:28: OSPF: DR/BDR election on TokenRing0
01:08:28: OSPF: Elect BDR 126.96.36.199
01:08:28: OSPF: Elect DR 188.8.131.52
01:08:28: DR: 184.108.40.206 (Id) BDR: 220.127.116.11 (Id)
The router that went down was neither DR nor BDR. Why was there a DR election reported? Does this always happen when there's a neighbor change event on a multiaccess interface? That doesn't jibe with my training, which says that an election won't take place unless the existing DR goes down.