What is the likely cause of this issue?

Refer to the exhibit.

A spoke site that is connected to Router-A cannot reach a spoke site that is connected to Router-B,
but both spoke sites can reach the hub. What is the likely cause of this issue?

Refer to the exhibit.

A spoke site that is connected to Router-A cannot reach a spoke site that is connected to Router-B,
but both spoke sites can reach the hub. What is the likely cause of this issue?

A.
There is a router doing PAT at site B.

B.
There is a router doing PAT at site A.

C.
NHRP is learning the IP address of the remote spoke site as a /32 address rather than a /24
address.

D.
There is a routing issue, as NHRP registration is working.



Leave a Reply 3

Your email address will not be published. Required fields are marked *


ak

ak

Cisco says correct answer is B, which I think is mistake.
Option A should be the answer.

Router-A recognizes that 172.16.2.1 is claimed by Router-B.
But the actual source address of nhrp registration is 144.254.21.2.
These facts show that Router-B is under PAT router.

Theo

Theo

If router B is doing the address translation, there is no way that router A could know it, all it will know is the “public” address. Since router A knows the actual and the claimed address then router A must be doing the address translation.