cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
633
Views
1
Helpful
13
Replies

DMVPN / EIGRP issue

Najib Akbari
Level 1
Level 1

Hi,

I have a hub and multiple spoke. spokes configs are identical and all running EIGRP. only one spokes keep loosing tunnel and EIGRP neighborship every 15-25 min. please assist. here is some logs on spoke and hub:

Hub:

NajibAkbari_0-1742945143906.png

Spoke:

NajibAkbari_1-1742945292077.png

 

13 Replies 13

Mostly it issue of DH or SA mismatch issue. 

Try use Eem ping to this spoke and check if there is reachbility or not. 

MHM

balaji.bandi
Hall of Fame
Hall of Fame

Do you have stable connectivity ? is the tunnel up when the eigrp gone down ?

 

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

sometimes EIGRP goes down first and most of the time tunnel goes down first. yes the link is stable

is this real environment or Lab ?

how is your network diagram looks like ? can you post below information

show dmvpn details

show ip interface brief

 

if this is only tunnel going down, then you need to troubleshoot ?

https://www.cisco.com/c/en/us/support/docs/security/dynamic-multipoint-vpn-dmvpn/111976-dmvpn-troubleshoot-00.html

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Najib Akbari
Level 1
Level 1

In addition to my initial post, Here is more details. also I inherited this setup and trying to wrap my head around it:

- the tunnel goes down every 10 min. exactly the time NHRP dy record expires!

- till today TAC engineer after hours of tshoot were saying based on logs the hub receives the DPD message from the spoke but for some unknown reason it does not respond and thats why the tunnel goes down for 10-15 seconds every 10 min

- then today after more debugging, to reach to the reason for that we found out on debug that the spoke  tries to reach out to HUB-A Tunnel IP but when it encapsulate the traffic it puts HUB-B NBMA IP instead of HUB-A NBMA-IP and that is the problem. well if its the design issue it might be related to NHS priority and cluster as both hubs are identical but then the golden question is why this is not happening on other spokes!

- so TAC says its DMVPN design config issue and sent me some docs to read, he said to test you can remove the second hub from s[poke config and see the result, set another session for tomorrow and left. i removed the second hub from the spoke config and its still happening haha
- this is the debug:

NajibAkbari_0-1743643046446.png

 

here is a bit info a bout the setup:

 - there are several spokes with identical config ( or I think they are ! ) and the issue only happens on one spoke!

- there are two Hubs A and B and overly EIGRP and prefer A over B

here is hub A and SPOKE ( with issue ), tunnel config:
hun-A:

NajibAkbari_1-1743643268987.png

 

 

Spoke:

NajibAkbari_2-1743643377619.png

 

 

Najib Akbari
Level 1
Level 1

and my finding is this and I think thats related to the issue is why spoke having a dynamic NHRP record of itslef!? it does not make sense to me: ( the last record )

NajibAkbari_3-1743643640617.png

 

I need two thing 

First topolgy 

Second the spoke config 

MHM

Najib Akbari
Level 1
Level 1

Here is the requested info and topology:

there are 2X Hub primary and secondary and the only difference is the overlay EIGRP delay that makes Primary Hub primary and no tunn config difference.

- just for security changed NBMA to : primary hub 1.1.1.1 sec Hub 2.2.2.2, SPOKE-1 ( with issue): 3.3.3.3  SPOKE-2 ( no issue): 4.4.4.4

Primary Hub Tunn:

interface Tunnel0
ip address 172.16.253.1 255.255.255.0
no ip redirects
ip mtu 1400
no ip split-horizon eigrp 100
ip nhrp map 172.16.253.254 2.2.2.2
ip nhrp network-id 12345
ip nhrp nhs 172.16.253.254
no ip nhrp shortcut
zone-member security LAN
ip tcp adjust-mss 1376
delay 10
tunnel source 1.1.1.1.1
tunnel mode gre multipoint
tunnel path-mtu-discovery
tunnel protection ipsec profile DMVPN

 

Secondary Hub:

interface Tunnel0
ip address 172.16.253.254 255.255.255.0
no ip redirects
ip mtu 1400
no ip split-horizon eigrp 100
ip nhrp map 172.16.253.1 1.1.1.1
ip nhrp network-id 12345
ip nhrp nhs 172.16.253.1
ip tcp adjust-mss 1376
delay 100000
tunnel source 2.2.2.2
tunnel mode gre multipoint
tunnel path-mtu-discovery
tunnel protection ipsec profile DMVPN

 

SPOKE-1:

interface Tunnel0
description
ip address 172.16.253.240 255.255.255.0
no ip redirects
ip mtu 1416
ip nhrp map 172.16.253.1 1.1.1.1
ip nhrp map multicast 1.1.1.1
ip nhrp map multicast 2.2.2.2
ip nhrp map 172.16.253.254 2.2.2.2
ip nhrp network-id 12345
ip nhrp nhs 172.16.253.1
ip nhrp nhs 172.16.253.254
tunnel source GigabitEthernet0/0/0
tunnel mode gre multipoint
tunnel protection ipsec profile DMVPN
end

 

SPOKE-2:

interface Tunnel0
ip address 172.16.253.10 255.255.255.0
no ip redirects
ip mtu 1416
ip nhrp map 172.16.253.1 1.1.1.1
ip nhrp map multicast 1.1.1.1
ip nhrp map 172.16.253.254 2.2.2.2
ip nhrp map multicast 2.2.2.2
ip nhrp network-id 12345
ip nhrp nhs 172.16.253.1
ip nhrp nhs 172.16.253.254
tunnel source GigabitEthernet0/0/0
tunnel mode gre multipoint
tunnel protection ipsec profile DMVPN
end

 

- yes this is in production, but only 1-3 users mostly using Internet and barely DMVPN

- sh ip int and DMVPN on:

primary hub:

NajibAkbari_1-1743703924798.png

NajibAkbari_0-1743703873249.png

 

from the spoke with issue:

 

NajibAkbari_2-1743704019971.png

 

 

Topology:

NajibAkbari_3-1743704038488.png

 

 

 

 

Sure it not work' there is must one tunnel for both hub' 

Router not accept two tunnel use same subnet.

Config one tunnel and use priority to make one hub as primary and other as backup.

MHM

can you elaborate a bit please? I am thinking to apply priority too but how this issue relates to that and if it is the how come not having any issue on the other spokes?

Najib Akbari
Level 1
Level 1

i think the issue related to this having an exra NHRP record on SPOKE-1 pointing to itself causing the issue but I can not explain it

NajibAkbari_0-1743707603584.png

 

I believe I found the source of issue the SPOKE-1 Tunn flapping every 10 min:

- on the previous comment I mentioned the SPOKE-1 is having an extra record on NHRP pointing to itself dynamic and when it expires the tunn flaps.

- Prim-Hub has a MAP to Sec-Hub and vise versa: I could not find any reason for it being like that. so I removed the mapping on each Hub pointing to one another and that stopped Tunnel flapping on SPOKE-1 and also removed extra NHRP record.

note: I can not have a proper technical explanation for that how it solved the issue or why it was not happening on other spokes with identical config, but Im sure it was related to the hubs mapping to each other and somehow created routing issue!

PLEASE chime in if you think of anything regarding this. Thank you!!!

Let I ask you simple Q, can I config two interface with same subnet?

No you can not. 

The config of tunnel in spoke 

Interface tunnel x

Ip nhs x.x.x.x

Ip nhs y.y.y.y

Ip nhrp map x.x.x.x X. X. X. X

Ip nhrp map y.y.y.y Y.Y.Y.Y

here one tunnel can reach two hubs

MHM