tag:blogger.com,1999:blog-23021255.post1712597223305250641..comments2012-01-17T08:02:17.624+01:00Comments on ipSpace.net: Redundant DMVPN designs, Part 1 (The Basics)Ivan Pepelnjakhttp://www.blogger.com/profile/13457151406311272386noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-23021255.post-23265310676245672642012-01-17T08:02:17.625+01:002012-01-17T08:02:17.625+01:00addition to my early post - can provide configurat...addition to my early post - can provide configuration examples <br />also, this scheme working good with linux (but in static tunnel end-poing configuration with linux host. not found the time and desire to properly configure NHRP daemon on linux sideKAVnoreply@blogger.comtag:blogger.com,1999:blog-23021255.post-56040185222342322292012-01-17T07:55:51.815+01:002012-01-17T07:55:51.815+01:00simpler solution:
have multiple dmvpn hubs and s...simpler solution: <br /><br />have multiple dmvpn hubs and spokes and multiple ISP on each side <br />to connect it together we need dedicated VRF for each ISP (outside VRFs) and dedicated VRF for each tunnel-interface (inside VRFs). then, configuring each tunnel-interface as usual and redistributing routes between inside VRFs via BGP. <br /><br />with this scheme we have all possible connectivity between any number of hubs and spokes with any number of ISP connections each. <br /><br />P.S.: sorry for bad english.KAVnoreply@blogger.com