Question 130
A newly commissioned network, compute or storage service reports: Two Nexus switches share an OSPFv2 segment, but their neighbors remain stuck in ExStart immediately after one uplink was changed to a larger MTU. Which implementation action should the engineer take first?
Explanation
Correct Answer
The root problem is that The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. The selected change addresses it directly: Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency. Verify the outcome: Both peers reach Full state and exchange the intended routes without retransmission or MTU errors.
Incorrect Answers
This action concerns hsrp uplink tracking failover, where The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. The reported failure instead stems from The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably.
This action concerns mp-BGP evpn address family activation, where The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. The corrective response here is “Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency”; this alternative does not provide that response.
This action concerns ospfv3 ipv6 area consistency, where The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. The stem reports two Nexus switches share an OSPFv2 segment, but their neighbors remain stuck in ExStart immediately after one uplink was changed to a larger MTU; this control addresses a different failure condition.