[quagga-dev 11979] Re: BGP graceful restart and FPM

J Yu jackiesyu at hotmail.com
Fri Jan 23 19:05:55 GMT 2015


If you can give me some pointers, would love to contribute! thanks!
Jacqueline

> Date: Fri, 23 Jan 2015 17:53:46 +0100
> From: equinox at opensourcerouting.org
> To: jackiesyu at hotmail.com
> CC: paul at jakma.org; quagga-dev at lists.quagga.net
> Subject: [quagga-dev 11976] Re: BGP graceful restart and FPM
> 
> On Fri, Jan 23, 2015 at 08:28:33AM -0800, J Yu wrote:
> > Given that, how could the graceful restart be handled in the forwarding 
> > plane? Any pointers/ideas?
> 
> Unfortunately, this needs additional code / an extension of the zapi
> protocol in order to signal EoR from the protocols to zebra.  This
> simply hasn't been implemented yet - GR support in Quagga is incomplete
> there.
> 
> ... patches welcome ...
> 
> 
> -David
> 
> 
> > > On Tue, 20 Jan 2015, J Yu wrote:
> > > > Need some help here --
> > > 
> > > > I am working on a project that uses FPM to receive the routing table 
> > > > update from various protocols, say BGP. In a BGP graceful restart 
> > > > scenario, there would be an "End-of-RIB" marker being received by the BGP 
> > > > protocol and how does that correlate to the FPM messages that I will be 
> > > > receiving? i.e., when would I know as plugged into the FPM for data plane 
> > > > forwarding table update to know that I could reconcile with the forwarding 
> > > > table?
> > Paul Jakma wrote:
> > > I don't know the details of the FPM interface, however, as its coming from
> > > zebra I don't think it has any knowledge of BGP EoRs in it.
> > > 
> > > The messages from zebra, either via ZServ or FPM, are not delayed or
> > > synchronised with routing protocol daemon events/states.
> 
> 
> _______________________________________________
> Quagga-dev mailing list
> Quagga-dev at lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-dev
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20150123/1bc5e29c/attachment-0001.html>


More information about the Quagga-dev mailing list