Network & Infrastructure / OSPF & Underlay Convergence
OSPF external forwarding addresses and inaccessible next hops
An external LSA exists in the database, but the destination is absent from usable routing. Its forwarding address can introduce a dependency that differs from reachability to the advertising ASBR.
Environment and inputs: OSPFv2 IPv4 underlays, with OSPFv3 explicitly identified where used; timers and diagnostics vary by platform. Diagnostic/design example; not tested on production equipment.
Collect the evidence
Inspect the external LSA, forwarding address, area route types and matching route to that address. Compare the database entry with the routing-table reason for noninstallation.
Explain the result
An LSA's presence does not guarantee a valid route calculation. The forwarding address must meet the protocol's reachability requirements; a fallback default may not satisfy them.
Plan the fix
Repair the supported topology and reachability for the forwarding address or correct redistribution behavior according to the design. Avoid forcing installation with unrelated static routes without understanding recursion.
Check the result and rollback
Verify installation and actual forwarding from every affected area. Roll back if the correction creates recursion, bypasses an intended security boundary or changes reachability outside the external prefix set.