Im doing some lab test on GNS3 for DMVPN before go into real implementation. in here, we have Single DMVPN cloud with 2 HUBs. Note here, those two HUB not for redundancy purpose. They both located at different location and both serving different Web application to branches. So instead of creating 2 DMVPN cloud (1 for each HUB), I combined them in single DMVPN. Both Hub will talk each other via Point-toPoint Link. I purposely not include HUB1 to HUB2 connection in DMVPN. I have no problem on connectivity between SOPKE to Both HUB or SPOKE to SOPKE. Everything jus worked fine. But SOPKE sees two NHS server, and send request for NHRP mapping for to both of HUB , and both HUB also replies to the request. In such case, SPOKE2 sees SPOKE1 LAN IP via 2 available path, but gateway is SAME.Below is the output on SOPKE2. Why is it in this way? Can I make it HUB1 is the only NHS server, while having static NHRP mapping for HUB2 in SOPKE routers.?
SOPKE1 : 10.0.0.3 LAN: 172.16.30.0
SOPKE2: 10.0.0.4 LAN : 172.16.40.0
HUB1 : 10.0.0.1 LAN : 172.16.10.0
HUB2: 10.0.0.2 LAN : 172.16.20.0
SPOKE2#sho ip route eigrp
172.16.0.0/24 is subnetted, 4 subnets
D 172.16.30.0 [90/310172416] via 10.0.0.3, 00:01:57, Tunnel0
[90/310172416] via 10.0.0.3, 00:01:57, Tunnel0
D 172.16.20.0 [90/297372416] via 10.0.0.2, 00:07:41, Tunnel0
D 172.16.10.0 [90/297372416] via 10.0.0.1, 00:01:57, Tunnel0
SPOKE2#sho ip eig topo
P 10.0.0.0/24, 1 successors, FD is 297244416
via Connected, Tunnel0
via 10.0.0.1 (310044416/15299840), Tunnel0
P 172.16.40.0/24, 1 successors, FD is 128256
via Connected, Loopback0
P 172.16.30.0/24, 2 successors, FD is 310172416
10.0.0.3 via 10.0.0.1 (310172416/15427840), Tunnel0
10.0.0.3 via 10.0.0.2 (310172416/297372416), Tunnel0
I understand why is it showing two available path to another SPOKE. So how do make it only HUB1 become NHS server while still having static NHRP mapping to HUB2. Enable Split-horizon on HUB2 will disable route update back to spoke, but its still serving as NHS server. How to achieve this?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...