BGP Routing in DMVPN Networks
Once you decide to use BGP as the routing protocol in your DMVPN network, you face a few more design choices:
- Should you use IBGP or EBGP?
- Should you use a unique AS number for every DMVPN site, or the same AS number on all spoke sites?
The BGP Routing in DMVPN Access Networks ExpertExpress case study describes these dilemmas in more details.
Recent posts in the same categories
design
- EVPN Designs: EBGP Everywhere
- One-Arm Hub-and-Spoke VPN with MPLS/VPN
- EVPN Hub-and-Spoke Layer-3 VPN
- Hub-and-Spoke VPN on a Single PE-Router
- Hub-and-Spoke VPN Topology
- EVPN Designs: Scaling IBGP with Route Reflectors
DMVPN
- Building a DMVPN Test Lab with netlab
- Use Existing (DMVPN) Device Configurations in netlab
- Feedback: DMVPN Webinars
- Open-Source DMVPN Alternatives
- DMVPN or Firewall-Based VPNs?
- Another DMVPN Routing Question
Do you have any estimations regarding the number of BGP peers (spokes) per Hub?
Some years ago our company designed DMVPN with BGP, but Cisco experts put a veto, because of number of peers we were expecting.
We had to go into production with EIGRP that time.
Thanks.
It lends itself easily to address families/VRFs but the only way I could control my own AS numbers was with the replace-as function which feels dirty.
You might need a transport VRF though.