350-501 · Question #472
Refer to the exhibit. During the last maintenance window, the network engineering team performed multiple software upgrades and enabled OSPFv3 for future use. However, when the network came up, the…
The correct answer is A. Change the hello and dead intervals on the interfaces on R1 and R2 to the same values. For OSPFv2 adjacencies to form, the hello and dead intervals must match on both routers. The issue in this scenario is that R1 is configured with a point-to-point network type, while R2 is configured as broadcast. These network types have different default hello and dead…
Question
Refer to the exhibit. During the last maintenance window, the network engineering team performed multiple software upgrades and enabled OSPFv3 for future use. However, when the network came up, the connection between HQ and the remote branch failed. A network engineer determined that routers R1 and R2 failed to establish an OSPFv2 adjacency. R1 was preconfigured with the point-to-point OSPF network type, and R2 as broadcast. The engineer confirmed that all connected interfaces are up, and the routers can reach one another via ICMP. Which action must the engineer take to resolve the issue?
Exhibit
Options
- AChange the hello and dead intervals on the interfaces on R1 and R2 to the same values
- BConfigure R1 and R2 with the same OSPFv3 router ID.
- CSet the same network statement under the OSPFv2 configuration on R1 and R2.
- DSet the R1 OSPFv2 process ID to match the R2 OSPFv2 process ID.
How the community answered
(34 responses)- A74% (25)
- B15% (5)
- C3% (1)
- D9% (3)
Explanation
For OSPFv2 adjacencies to form, the hello and dead intervals must match on both routers. The issue in this scenario is that R1 is configured with a point-to-point network type, while R2 is configured as broadcast. These network types have different default hello and dead interval values, causing the adjacency to remain in the INIT state.
Topics
Community Discussion
No community discussion yet for this question.