cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Who Me Too'd this topic

DMVPN and %DMVPN-3-DMVPN_NHRP_ERROR: Tunnel0: NHRP Encap Error for Resolution Request , Reason: protocol generic error (7) Error

rmishra22
Level 1
Level 1

  %DMVPN-3-DMVPN_NHRP_ERROR:  Tunnel0: NHRP Encap Error for  Resolution Request , Reason:  protocol generic error (7)

I had pre-allocated tunnel ip's to remote spokes , some of them were implemented and put into production. Some of them got the config but the tunnel interfaces were left at shut.

Its because of this reason that the DMVPN HUB keeps getting nhrp request from one of the inactive spokes.  Following is the sh ip nhrp extract :-

10.x.x22/32

   Tunnel0 created 00:02:58, expire 00:00:06

   Type: incomplete, Flags: negative

   Cache hits: 7

I just cant seem to find the spoke WAN ip to identify it. I tried debugs but just cant get it.

From HUB:-

Nov 30 10:36:31: %DMVPN-3-DMVPN_NHRP_ERROR:  Tunnel0: NHRP Encap Error for  Resolution Request , Reason:  protocol generic error (7) on (Tunnel: 10.x.x.1 NBMA: 20.x.x.x)

Nov 30 10:36:32: NHRP: Send Resolution Request via Tunnel0 vrf 0, packet size: 86

Nov 30 10:36:32:  (F) afn: IPv4(1), type: IP(800), hop: 255, ver: 1

Nov 30 10:36:32:      shtl: 4(NSAP), sstl: 0(NSAP)

Nov 30 10:36:32:      pktsz: 86 extoff: 52

Nov 30 10:36:32:  (M) flags: "router auth src-stable nat ", reqid: 46113

Nov 30 10:36:32:      src NBMA: 20.x.x.x.

Nov 30 10:36:32:      src protocol: 10.x.x.1, dst protocol: 10.x.x.22

Nov 30 10:36:32:  (C-1) code: no error(0)

Nov 30 10:36:32:        prefix: 32, mtu: 17912, hd_time: 360

Nov 30 10:36:32:        addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 0, pref: 0 Nov 30 10:36:31: %DMVPN-3-DMVPN_NHRP_ERROR:  Tunnel0: NHRP Encap Error for  Resolution Request , Reason:  protocol generic error (7) on (Tunnel: 10.x.x.1 NBMA: 20.x.x.x)

So my question is , How do i find out the spoke wan ip , so i can do something about it.  For now, its just filling up my logs on HUb router...not good ;-))

Who Me Too'd this topic