Question 350
At a regional provider operating Junos-based branch routers, a Junos specialist investigates this scenario: A pair of OSPF speakers exchanges packets but reports timer mismatch and no stable adjacency. The team must validate neighbor state rather than assume basic IP reachability proves routing. Which technical mechanism most directly explains the symptom?
Explanation
Correct Answer
For a regional provider operating Junos-based branch routers, the governing mechanism is: Neighbor compatibility depends on matching Hello and dead intervals for the participating link. It explains the reported symptom: A pair of OSPF speakers exchanges packets but reports timer mismatch and no stable adjacency. The intended response is: Align supported OSPF Hello and dead intervals on both neighboring interfaces. Verification: show ospf neighbor reaches Full and periodic Hellos remain within the agreed dead interval.
Incorrect Answers
Junos routing traceoptions can record protocol events for focused diagnosis when enabled carefully. This alternative mechanism does not match the current fault.
OSPFv3 is a distinct link-state protocol requiring correct interface and area enablement for IPv6 environments. Fixing that different mechanism would not address the current root cause: neighbor compatibility depends on matching Hello and dead intervals for the participating link.
OSPFv3 neighbor exchanges and next-hop forwarding commonly use IPv6 link-local addresses on the adjoining link. Its verification is distinct from the reported condition: A pair of OSPF speakers exchanges packets but reports timer mismatch and no stable adjacency. The team must validate neighbor state rather than assume basic IP reachability proves routing.