Question 90
At the Cedarbrook hospital, two DMVPN devices share a reachable underlay yet their NHRP configuration reports incompatible network identifiers. Which operational change most directly addresses the fault described?
Explanation
Correct Answer
The fault at the Cedarbrook hospital has a specific cause. The NHRP tunnel interfaces are not configured to participate in the same logical NHRP network. Set matching NHRP network identifiers on tunnel interfaces participating in the same DMVPN cloud. Confirm success against this result: NHRP registration and resolution succeed in the intended cloud without joining a separate cloud.
Incorrect Answers
This could help where dmvpn spoke registration to hub is the issue, but not for the evidence reported at the Cedarbrook hospital. The NHRP tunnel interfaces are not configured to participate in the same logical NHRP network.
That change targets dmvpn nhrp authentication mismatch, not the reported dmvpn nhrp network id mismatch fault at the Cedarbrook hospital. The NHRP tunnel interfaces are not configured to participate in the same logical NHRP network.
This is appropriate for a different routing or network-control issue: The origin spoke has not obtained the peer resolution needed to build an appropriate direct path. The stated evidence at the Cedarbrook hospital instead concerns dmvpn nhrp network id mismatch.