Question 630
Following a supported configuration correction, the original issue was: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. Which observation verifies success?
Explanation
Correct Answer
Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address. This confirms the approved response: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context. It is relevant because: IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.
Incorrect Answers
Valid component destinations work and an unassigned prefix does not loop indefinitely. This would validate ANOTHER scenario: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.
OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability. This would validate ANOTHER scenario: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.
The eBGP FSM reaches Established and the peer's AS is recorded correctly. This would validate ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.