Re: [j-nsp] under the hood of MP-BGP

Jeff, > > Jeff Haas [mailto:jh...@juniper.net] > > Sent: Tuesday, January 03, 2017 3:18 PM > > > > This step is actually why I posted the question. We encountered a > > problem where it takes 5-10 minutes for local routes, that are already > > installed in other VRFs on the PE, to get installed

Re: [j-nsp] under the hood of MP-BGP

Adam, On Jan 3, 2017, at 10:10 AM, adamv0...@netconsultings.com wrote: But what happens next or in parallel? Does BGP parse through the local MP-BGP table first in attempt to import at least the local routes into the NEW VRF as soon as possible? If there's

Re: [j-nsp] under the hood of MP-BGP

Hi Jeff, I was actually of hoping you'll chime in for this one :-). Thank you very much. > From: Jeff Haas [mailto:jh...@juniper.net] > Sent: Tuesday, January 03, 2017 1:45 PM > > Adam, > > > On Dec 23, 2016, at 4:24 AM, adamv0...@netconsultings.com wrote: > > Does anyone know any details

Re: [j-nsp] under the hood of MP-BGP

Adam, > On Dec 23, 2016, at 4:24 AM, adamv0...@netconsultings.com wrote: > Does anyone know any details about what's going on under the hood of MP-BGP > when a new VRF is configured? > > > > I'm only clear about this part: > > When a new RT import is configured or when the RT import is

[j-nsp] under the hood of MP-BGP

Hi folks, Does anyone know any details about what's going on under the hood of MP-BGP when a new VRF is configured? I'm only clear about this part: When a new RT import is configured or when the RT import is removed, a route refresh is sent from the PE to RRs for the affected address