02-05-2009 10:12 AM - edited 03-04-2019 01:07 AM
My first question is this
IS phase 3 supported on a 7206VXR running
(C7200-ADVENTERPRISEK9-M), Version 12.4(20)T1 ???
And if it does is this the correct config for the HUB tunnel
interface Tunnel10
description Primary INT for DMVPN
bandwidth 100000
ip address xxx.xxx.xxx.xxx xxx.xxx.x.x
no ip redirects
ip mtu 1400
no ip next-hop-self eigrp 1
ip nhrp authentication xxxxx
ip nhrp map multicast dynamic
ip nhrp network-id xxx
ip nhrp holdtime 300
ip nhrp nhs xxx.xxx.xx.xxx
ip nhrp shortcut
ip nhrp redirect
ip virtual-reassembly
ip tcp adjust-mss 1360
no ip split-horizon eigrp 100
tunnel source GigabitEthernet0/1
tunnel mode gre multipoint
tunnel key xxxx
tunnel protection ipsec profile xxxx shared
Or should I remove the "no ip next-hop-self eigrp 1"
02-05-2009 11:07 AM
Hello Brent,
configuration looks like fine
the right command should be
no ip next-hop-self eigrp 100
if 100 is the EIGRP AS number in use
this command is used to provide spoke to spoke dynamic tunnel setup
FN
http://www.cisco.com/go/fn')">www.cisco.com/go/fn
platform 7200
release 12.4T
12.420T1
advanced services
provides
DMVPN - Hub Support by QoS Class
DMVPN Manageability Enhancements
Hope to help
Giuseppe
02-05-2009 11:15 AM
Hey Giuseppe thanks for the quick reply, but if I'm trying to go to DMVPN phase 3 should I remove the "no ip next-hop-self eigrp 100" entry from the tunnel interface?
From what I've read there are two opinions on it.
Thanks,
Brent
02-05-2009 11:25 AM
Hello Brent,
I'm not sure what you mean with DMVPN phase3.
However, without that command when using EIGRP spoke to spoke dynamic tunnels cannot be setup.
see for example
So the choice depends on what you want to achieve:
if all traffic has to go through hub/central site remove the command
if you want to offload direct spoke to spoke traffic on dynamic tunnels keep it
Hope to help
Giuseppe
02-05-2009 11:27 AM
02-05-2009 11:45 AM
Hello Brent,
thanks for the link it is very good.
at the end of the document there is a link to Cisco site about migration from phase 2 to phase3
the explanation is very clear about NHRP redirect message, introduction of prefixes and prefixes lengths in NHRP messages.
if you move to phase3 you don't need that command anymore see
To enable NHRP shortcut switching:
⢠All spokes need to have the commands ip nhrp shortcut and the ip nhrp redirect added to their tunnel interfaces. For the hubs use only ip nhrp redirect.
⢠For EIGRP, in the hub side only:
- Remove: no ip next-hop-self eigrp
- Leave: no ip split-horizon eigrp
- Add as needed: ip summary-address eigrp
Hope to help
Giuseppe
02-05-2009 11:47 AM
Yeah, I read that and thought to myself .. hmmmm I better get a second opinion LOL
Thanks a ton
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide