In the Redundant DMVPN Design, Part 1 I described the options you have when you want to connect non-redundant spokes to more than one hub. In this article, we’ll go a step further and design hub and spoke sites with multiple uplinks.
Public IP addressing
Fact: DMVPN tunnel endpoints have to use public IP addresses or the hub/spoke routers wouldn’t be able to send GRE/IPsec packets across the public backbone.
Read more ...Thanks for reading my news about Redundant DMVPN designs, Part 2 (Multiple Uplinks) at my blog Bros Droid if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.
More Articles :
Long-Distance Workload Mobility in Perspective- Can I download the webinar recordings?
- Could MPLS-over-IP replace VXLAN or NVGRE?
- Legacy Protocols in OpenFlow-Based Networks
- Equal-Cost Multipath in Brocade’s VCS Fabric
- Does TRILL make sense at all?
- ARP reply with multicast sender MAC address is indeed illegal
- Does CPU-based forwarding performance matter for SDN?
- Analyst-driven IPv6 deployment
- QFabric Lite