Question 1130
At Main Data Center, two aggregation switches report OSPF Init and Down cycles after one interface timer change. Which check provides the most useful information for fixing this deployment?
Explanation
Correct Answer
For Main Data Center, the decisive mechanism is OSPF hello and dead timers. OSPF timer mismatches can prevent reliable adjacency even when IP connectivity exists. Inspect received hello timers and neighbor reset reasons is the most direct way to isolate this particular failure before making a change.
Incorrect Answers
This is relevant to First-hop gateway election, where VRRP abstracts the default gateway across eligible routing devices In the Main Data Center case, Those observations could be normal while the stated fault persists. The specific mechanism is oSPF timer mismatches can prevent reliable adjacency even when IP connectivity exists
This is relevant to IPv6 OSPFv3 adjacency, where oSPFv3 exchanges IPv6 routing information through a separately configured protocol process In the Main Data Center case, Those observations could be normal while the stated fault persists. The specific mechanism is oSPF timer mismatches can prevent reliable adjacency even when IP connectivity exists
This is relevant to ECMP next-hop selection, where eCMP typically spreads flows over equal-cost next hops, not necessarily one flow packet by packet In the Main Data Center case, Those observations could be normal while the stated fault persists. The specific mechanism is oSPF timer mismatches can prevent reliable adjacency even when IP connectivity exists