Q: 8
DRAG DROP Drag and drop the OSPF adjacency states from the left onto the correct descriptions on the right. 
Drag & Drop
Discussion
Init → router ID not in hello, 2-way → info exchange on multiaccess, Down → no hellos, Exchange → DBD packet comparison, ExStart → DR/BDR elected, Loading → neighbor requests missing. I don't think 'Exchange' should go with general info exchange, that's the trap here.
Exchange → Each router compares DBDs, 2-way → multiaccess info exchange, Loading → neighbor requests missing entries, ExStart → DR/BDR chosen, Init → router ID not in hello, Down → no hellos seen. Pretty sure this matches Cisco's OSPF state order, but Exchange and Loading can be easy to mix up here. Agree?
Init → OSPF router ID not in hello, 2-way → exchange info on multiaccess, Down → no hellos received, Exchange → routers compare DBDs, ExStart → DR/BDR election done, Loading → missing entries requested. Pretty confident since OSPF states are strict in order but if the descriptions hinted at 'first comparison' or LSDB sync phase specifically, Exchange and Loading could get swapped.
Init → router ID not in hello, 2-way → info exchange on multiaccess, Down → no hellos, Exchange → DBD packet comparison, ExStart → DR/BDR elected, Loading → neighbor requests missing entries. I don’t think Exchange should match "multiaccess" info-sometimes that one’s a trap.
Init → router ID not in hello, 2-way → multiaccess info exchange, Down → no hellos, Exchange → DBD comparison, ExStart → DR/BDR elected, Loading → neighbor requests missing. Saw a similar practice. Sometimes Exchange/Loading get mixed up if you focus too much on 'info exchange' wording.
Not quite, Exchange and Loading are the tricky ones here. Exchange is for DBD packet comparison, Loading is when missing LSAs are requested. Down can look tempting for Init but it’s really just ‘no hellos seen’. Anyone else agree?
Exchange → DBD comparison, 2-way → info exchange on multiaccess, Loading → missing entries requested, ExStart → DR/BDR elected, Init → router ID not in hello, Down → no hellos seen. Seen this mapping a few times so I’m pretty sure it’s solid. Disagree?
Exchange to DBD packets, 2-way for multiaccess info, Loading is missing entries, ExStart DR election, Init ID not in hello, Down means no hellos. Seen this before.
Exchange → DBD packets compared, 2-way → routers talk on multiaccess, Loading → neighbor asks for missing entries. ExStart is DR/BDR elected, Init means no router ID in hello, Down is zero hellos received. I think that's the Cisco order, but the Exchange/Loading split always makes me double check.
Exchange → Each router compares the DBD packets, 2-way → Routers exchange info with others in multiaccess, Loading → Neighbor requests the other to send missing entries. ExStart handles DR/BDR done, Init is missing router ID in Hello, Down is no Hellos seen. Pretty sure-easy to mix up Exchange/Loading descriptions if you're not careful.
Be respectful. No spam.
