Question 420
At a healthcare organization connecting redundant facilities, a Junos specialist investigates this scenario: An OSPF neighbor remains in ExStart or Exchange although basic connectivity and Hellos work. The correction must not expose administrative network prefixes. What protocol behavior accounts for this failure?
Explanation
Correct Answer
For a healthcare organization connecting redundant facilities, the governing mechanism is: Database-description exchange can fail when peers disagree on the IP MTU for a common OSPF link. It explains the reported symptom: An OSPF neighbor remains in ExStart or Exchange although basic connectivity and Hellos work. The intended response is: Correct the relevant link MTU on both endpoints and restart adjacency safely if necessary. Verification: The neighbor leaves ExStart and reaches Full with synchronized link-state databases.
Incorrect Answers
A passive OSPF interface can advertise attached reachability while suppressing neighbor-discovery Hellos. This alternative mechanism does not match the current fault.
A not-so-stubby area allows local external routes using type-7 LSAs and an ABR can translate them toward other areas. Fixing that different mechanism would not address the current root cause: database-description exchange can fail when peers disagree on the IP MTU for a common OSPF 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: An OSPF neighbor remains in ExStart or Exchange although basic connectivity and Hellos work. The correction must not expose administrative network prefixes.