nerdexam
Cisco

300-730 · Question #171

Refer to the exhibit. The network security engineer identified that the hub router cannot send traffic to the spoke router. Based on the provided output, which action resolves the issue? [Exhibit: Con

The correct answer is B. Correct the next hop server IP address on the spoke router.. The NHRP output showing 'req-failed 31' and 'repl-recv 0' means the spoke is sending NHRP registration requests that are never acknowledged, pointing directly to an incorrect NHS IP address configured on the spoke.

Troubleshooting VPNs

Question

Refer to the exhibit. The network security engineer identified that the hub router cannot send traffic to the spoke router. Based on the provided output, which action resolves the issue? [Exhibit: Console output showing show crypto isakmp sa, show crypto IPSEC sa, and show ip nhrp nhs detail from Hub-Router and Spoke-Router. Key lines include Spoke-Router#show ip nhrp nhs detail showing req-failed 31 repl-recv 0 and Pending Registration Requests.]

Options

  • APermit UDP ports 500 and 4500 between the hub and spoke.
  • BCorrect the next hop server IP address on the spoke router.
  • CEnsure the preshared key on the hub-and-spoke router matches.
  • DAdjust the ip nhrp network-id command on the hub router.

How the community answered

(25 responses)
  • A
    20% (5)
  • B
    64% (16)
  • C
    8% (2)
  • D
    8% (2)

Why each option

The NHRP output showing 'req-failed 31' and 'repl-recv 0' means the spoke is sending NHRP registration requests that are never acknowledged, pointing directly to an incorrect NHS IP address configured on the spoke.

APermit UDP ports 500 and 4500 between the hub and spoke.

Blocked UDP 500 or 4500 would prevent IKE SA formation entirely, which would appear as errors in 'show crypto isakmp sa' rather than NHRP-specific registration failures.

BCorrect the next hop server IP address on the spoke router.Correct

In DMVPN, the spoke uses the 'ip nhrp nhs' command to identify the hub's NHS address for registration. When this IP is misconfigured, registration requests are sent to an unreachable or wrong destination, incrementing 'req-failed' while 'repl-recv' stays at zero and registrations remain pending indefinitely. Correcting the NHS IP on the spoke restores the NHRP registration process and allows tunnel traffic to flow.

CEnsure the preshared key on the hub-and-spoke router matches.

A preshared key mismatch causes IKE Phase 1 authentication failure visible in the ISAKMP SA state, not in NHRP req-failed counters with zero replies.

DAdjust the ip nhrp network-id command on the hub router.

A mismatched ip nhrp network-id causes NHRP packets to be discarded locally, but the specific combination of req-failed incrementing with repl-recv at zero most directly indicates the spoke is targeting a wrong NHS destination IP.

Concept tested: DMVPN NHRP next hop server IP misconfiguration

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/sec_conn_dmvpn/configuration/xe-16/sec-conn-dmvpn-xe-16-book/sec-conn-dmvpn.html

Topics

#DMVPN#NHRP NHS#pending registration#hub-spoke

Community Discussion

No community discussion yet for this question.

Full 300-730 Practice