Have you ever tried to implement a large-scale DMVPN or MPLS/VPN network using BGP as the routing protocol? If you tried to stitch more than ~1000 sites together you’re well aware of all the pain caused by a small range of private AS numbers defined in RFC 1930. We can kludge our way around the limitation by reusing the same AS number on multiple sites (and using allowas-in when we need full routing information on every site), but such a design clearly sucks.
Read more ...Thanks for reading my news about More private AS numbers 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 :
Extending MPLS/VPN to Customer Sites- Could you run an MPLS-TE-only MPLS/VPN network without LDP?
- BGP Best External Explained
- MPLS/VPN Carrier’s Carrier – Myth or Reality?
- Is it safe to run Internet in a VRF?
- Load Balancing Across Multiple MPLS/VPN Providers
- BGP route replication in MPLS/VPN PE-routers
- Could MPLS-over-IP replace VXLAN or NVGRE?
- Internet-in-a-VRF and LFIB explosion
- Beware of the pre-bestpath cost extended BGP community