An administrator is troubleshooting two routers in an OSPFv3 network. They are trying to establish an OSPFv3 adjacency over an Ethernet link, but the adjacency is not forming. What are two possible reasons for this issue? (Choose two.)
- mismatched Area IDs
- mismatched network types
- mismatched global OSPV3 PID and the PID configured on the Ethernet interface
- mismatched link-local addresses
- mismatched global unicast addresses
- mismatched subnet masks
Explanation: When troubleshooting OSPFv3 adjacency issues between two routers over an Ethernet link, the following issues could be the possible reasons for adjacency failure:
- Mismatched network types: OSPFv3 supports different network types such as broadcast, non-broadcast, point-to-point, and point-to-multipoint. Both routers should have the same OSPFv3 network type configured on the Ethernet interface for adjacency to form.
- Mismatched link-local addresses: OSPFv3 uses link-local addresses to establish an adjacency between two routers over an Ethernet link. If the link-local addresses on both routers are not configured correctly, the adjacency will not form.
Therefore, both mismatched network types and mismatched link-local addresses could be possible reasons for the OSPFv3 adjacency not forming over an Ethernet link. The other options listed in the question such as mismatched Area IDs, mismatched global OSPv3 PID and the PID configured on the Ethernet interface, mismatched global unicast addresses, and mismatched subnet masks are not relevant to this issue.
Exam with this question: CCNP ENARSI v8 Final Exam Answers
Please login or Register to submit your answer