06-16-2013 10:36 PM - edited 02-21-2020 06:57 PM
Hi all,
I need some clarification on dasy-chaining NHS servers in DMVPN, when and why I need to to this.
Is it in only phase 2 and only with particular types of design?
For example if I have a two hub's with only one DMVPN cloud each, were spokes have connection to both of these for redundancy.
Cheers
06-17-2013 09:58 AM
Mikael,
What problem are you looking to solve? Maybe it's better to use phase 3 design with (optional) redundancy on NHRP level?
M.
06-17-2013 11:50 AM
Hi Marcin,
Yes phase 3 would probably be the best, but this is more for me to understand the technology and be able to talk about why using or not using a design.
Cheers
06-17-2013 11:47 AM
Daisy chaining to my understanding may be required in single dmvpn cloud when some peers are registered with one nhs and some with the other. It's applicable to phase 2 when routing info (next hop ip) is preserved. So when one nhs has no info about NBMA addrress of some host it may query another nhs. I don't know why this might be used, cause there are better designes of dmvpn that doesn,'t require nhs-chaining.
Sent from Cisco Technical Support Android App
06-18-2013 12:42 PM
Ok, yes I thought so, just had to verify :-)
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