Hi Gert, > From: Gert Doering [mailto:[email protected]] > Sent: 03 May 2015 12:44 > Hi, > > On Sun, May 03, 2015 at 11:07:10AM +0000, Adam Vitkovsky wrote: > > If you have the choice I'd definitely recommend Internet in a VRF. > > It provides resiliency, fast convergence and plethora of option or great > freedom on how to implement internet services (think outside the box). > > Thinking *in* the box, mixing your IPv4 Internet routing with MPLS operation > provides a number of extra surprises where things can blow up (... like, > "the NOC forgetting to enable MPLS on that new link"...). > Well MPLS LDP-IGP Synchronization is there to save you in these cases. But I think it's only available in IS-IS or OSPF. > "Plain IP routing" *does* provide fast convergence, btw, you just need > to run EIGRP :-) *duck and run* (yes, I'm aware that things have vastly > improved in link state protocol land in the past 10 years, and stuff like > LFA is now even better) > Right, but I was talking about BGP convergence/resilience in environments using route-reflection which is I guess the majority of autonomous systems out there. Right you can distribute multiple paths for a given prefix using pure BGP RRs however that requires dividing the RR-infrastructure into logical/physical planes (one per path) or to introduce add-path. But with Internet in a VRF you get all the luxury to choose which paths and how many are going to be installed on any particular PE by design i.e. no need to add any additional complexity.
adam --------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com --------------------------------------------------------------------------------------- _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
