Question 320
At a regional provider operating Junos-based branch routers, a Junos specialist investigates this scenario: OSPF adjacency troubleshooting reveals two different devices using the same router identifier. The team must validate neighbor state rather than assume basic IP reachability proves routing. Which limitation should guide the change control?
Explanation
Correct Answer
For a regional provider operating Junos-based branch routers, the relevant safeguard is: Coordinate identity changes because LSAs and neighbor databases can be rebuilt. It matters while implementing: Configure distinct stable router IDs and restart or refresh affected protocol processes as supported. The fault involves: The OSPF router ID uniquely identifies an originator of link-state information within the routing domain. The required acceptance result remains: Each OSPF peer reports a distinct expected router ID and adjacency state becomes stable.
Incorrect Answers
Neighbor compatibility depends on matching Hello and dead intervals for the participating link. The appropriate correction for the reported case is: Coordinate identity changes because LSAs and neighbor databases can be rebuilt.
A scoped OSPF default-route export can advertise 0.0.0.0/0 when the default is valid. Fixing that different mechanism would not address the current root cause: the OSPF router ID uniquely identifies an originator of link-state information within the routing domain.
OSPF can compute equal-cost paths; forwarding utilization depends on installed next hops and platform ECMP behavior. Its verification is distinct from the reported condition: OSPF adjacency troubleshooting reveals two different devices using the same router identifier. The team must validate neighbor state rather than assume basic IP reachability proves routing.