Question 60
At a national enterprise designing OSPF between offices, a Junos specialist investigates this scenario: A connected LAN should be advertised as internal reachability without forming OSPF adjacencies with attached hosts. The internal forwarding path must remain stable when one uplink fails. What is the most likely design-related cause?
Explanation
Correct Answer
For a national enterprise designing OSPF between offices, the governing mechanism is: A passive OSPF interface can advertise attached reachability while suppressing neighbor-discovery Hellos. It explains the reported symptom: A connected LAN should be advertised as internal reachability without forming OSPF adjacencies with attached hosts. The intended response is: Configure supported OSPF passive behavior on the host-facing interface. Verification: The subnet is reachable from OSPF peers while no neighbor forms on the passive port.
Incorrect Answers
OSPF neighbor discovery requires the relevant logical interface to participate in the correct routing instance and area. This alternative mechanism does not match the current fault.
Neighbor compatibility depends on matching Hello and dead intervals for the participating link. Fixing that different mechanism would not address the current root cause: a passive OSPF interface can advertise attached reachability while suppressing neighbor-discovery Hellos.
Junos OSPF export governs eligible external route origination while import filtering has different route-selection effects. Its verification is distinct from the reported condition: A connected LAN should be advertised as internal reachability without forming OSPF adjacencies with attached hosts. The internal forwarding path must remain stable when one uplink fails.