You should Endeavor to keep the spoke to spoke tunnels up at all times then...
That's what I used to do -
Best way to do that - is just put the tunnel interfaces (which are ALL on the same subnet anyway) into Eigrp.
You are running EIGRP, right?
Or did you get fooled into running OSPF by one of the workbooks?
LOL
-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Tom Kacprzynski
Sent: Thursday, July 11, 2013 4:08 PM
To: Cisco certification
Subject: RSVP Split-Horizon and DMVPN Phase 3
Hello,
I'm running DMVPN with Phase 3 with RSVP enabled on tunnel interfaces. In phase 3 everything is initially routed through the hub, then redirected to spoke-to-spoke . The problem is that my DMVPN Hub will not forward the RSVP packets out the same tunnel interface it received the original message because of the RSVP split-horizon rule. If the spoke-to-spoke tunnel gets triggered by another traffic type, then RSVP works. The problem is that RSVP messages are send first before sending any voice RTP packets. If the RSVP reservation fails (cause of the split horizon rule) then there are no additional packets sent and spoke-to-spoke tunnels aren't dynamically created.
Has anyone else see something similar or would be able to help me resolve this issue?
Thank you,
Tom Kacprzynski
CCIE#36159
Blogs and organic groups at http://www.ccie.net
Received on Thu Jul 11 2013 - 21:25:37 ART
This archive was generated by hypermail 2.2.0 : Thu Aug 01 2013 - 08:45:50 ART