Question 130
At a healthcare organization connecting redundant facilities, a Junos specialist investigates this scenario: A team expects an IPv6 OSPFv3 next hop to appear only as a global unicast address. The correction must not expose administrative network prefixes. What is the most likely design-related cause?
Explanation
Correct Answer
For a healthcare organization connecting redundant facilities, the governing mechanism is: OSPFv3 neighbor exchanges and next-hop forwarding commonly use IPv6 link-local addresses on the adjoining link. It explains the reported symptom: A team expects an IPv6 OSPFv3 next hop to appear only as a global unicast address. The intended response is: Validate the IPv6 link-local adjacency and correct outgoing logical interface for the route. Verification: An IPv6 destination installs with an expected link-local next hop and forwards successfully.
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.
OSPFv3 is a distinct link-state protocol requiring correct interface and area enablement for IPv6 environments. Fixing that different mechanism would not address the current root cause: OSPFv3 neighbor exchanges and next-hop forwarding commonly use IPv6 link-local addresses on the adjoining link.
The OSPF router ID uniquely identifies an originator of link-state information within the routing domain. Its verification is distinct from the reported condition: A team expects an IPv6 OSPFv3 next hop to appear only as a global unicast address. The correction must not expose administrative network prefixes.