From: Jens Petter Eikeland (jenseike@start.no)
Date: Sat Aug 27 2005 - 14:16:24 GMT-3
Hi ,
You will need the no ip next-hop-self eigrp <as> command on the hub router
to have the next hop be the orginal next hop.
Jens P
-----Opprinnelig melding-----
Fra: nobody@groupstudy.com [mailto:nobody@groupstudy.com] Pe vegne av M.
Mohan
Sendt: 27. august 2005 14:08
Til: CCIEGS
Emne: DMVPN and EIGRP
Hello all,
I have configured a basic DMVPN set up and running
EIGRP over the tunnel interfaces.
At the spoke routers, I see that the next-hop to reach
the networks beyond the other spoke points to the hub
router's tunnel interface. If I want to have
spoke-to-spoke tunnels, then I need to have these
next-hops point to the remote spoke routers' tunnel
interfaces.
According to the below document, to achieve this, I
need to use process switching on the tunnel
interfaces. (I am running 12.2(15)T)
http://www.cisco.com/warp/public/105/dmvpn.html#eigrp
I configured "no ip route-cache" on the tunnel
interfaces of the spokes to have it process switched.
But still I see that the spokes point to the hub
router's tunnel interface to reach the networks beyond
other spokes.
The other option is to run a different protocol, which
I am anyway going to try, but wanted to make this work
before I try that.
Anybody know how to make this work using EIGRP?
I have turned off the split-horizon at the hub
router's mGRE interface.
Thanks in advance,
Mohan
__________________________________
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:20 GMT-3