Refer to the exhibit. A customer has a DMVPN establishment problem between a hub and a spoke router. To troubleshoot this problem, the network administrator checks the traffic counters of the tunnel and notices that return traffic is not coming back from the other end of the tunnel.
```
SPOKE#show ip nhrp rhs detail
Legend: Ex-Expeding replies, R=Responding
Total: 10.10.1.1 E rec=30 req=30 req-failed 30 repl-recv 0
Pending Registration Requests:
Registration Request Reqid 4371, Ret 64 NHS 10 10 1 1
```

Question

Accepted Answer

C. Configure the correct NHS. With req=30, req-failed=30, and repl-recv=0, the spoke successfully sent 30 NHRP registration requests to NHS 10.10.1.1 but received zero replies, which is the definitive symptom of an incorrect or unreachable NHS address. Correcting the NHS IP on the spoke tunnel interface will allow registration replies to return and complete the DMVPN adjacency.

Answer

A. Make the tunnel source and destination reachable. Basic tunnel reachability is confirmed as a prerequisite by the fact that 30 requests were transmitted; if the tunnel were down, no requests would be sent at all.

Answer

B. Implement the NHRP shortcut. NHRP shortcuts facilitate spoke-to-spoke direct paths and have no effect on the spoke-to-hub registration process shown failing in the exhibit.

Answer

D. Replace the network-id. A mismatched NHRP network-id prevents a spoke from joining the NHRP domain entirely rather than causing selective reply drops against a specific NHS.

Refer to the exhibit. A customer has a DMVPN establishment problem between a hub and a spoke router. To troubleshoot this problem, the network administrator checks the traffic counters of the tunnel…

Question

Options

How the community answered

Why each option

Topics

Community Discussion