<div><span>I dont know the bird internals exactly, but iirc this is implemented to save tracking as you mentioned in the code.</span></div><div><span><br></span></div><div><span>According to</span></div><div><span><br></span></div><span>RFC 2918</span><div><br></div><div>Otherwise, the BGP speaker shall re-<br> advertise to that peer the Adj-RIB-Out of the <AFI, SAFI> carried in<br> the message, based on its outbound route filtering policy.</div><div><br></div><div>--> No withdraw mentioned</div><div><br></div><div>I think in some situations it makes sense to withdraw all known routes, but the still active ones to create a consistent table on the receiver side.</div><div><br></div><div>What is the peer device btw?</div><div><br></div><div>Rgds, SJ</div><div><br></div><div>P.S.: Sorry for TOFU</div><div><br><div class="gmail_quote"><div dir="ltr">Christos Trochalakis <<a href="mailto:yatiohi@ideopolis.gr" target="_blank">yatiohi@ideopolis.gr</a>> schrieb am Mo., 28. Dez. 2015 09:46:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Dec 10, 2015 at 12:10:35PM +0200, Christos Trochalakis wrote:<br>
>Hello all,<br>
><br>
>While debugging a route-refresh issue we discovered that when a route-refresh<br>
>is received, bird, instead of just sending an update containing the exported<br>
>routes, also withdraws **all known routes** from its peer. In our case, it<br>
>withdraws the whole FIRT sending multiple BGP updates. Is this the expected<br>
>behaviour? We are using bird 1.4.5.<br>
><br>
>We believe that the opposite router has trouble processing all those withdrawed<br>
>routes which leads to other connectivity issues.<br>
><br>
<br>
Any comments on that?<br>
<br>
Let me restate the issue, bird withdraws every route in its routing<br>
table despite the fact that those routes were never exported to that<br>
protocol. I am not familiar with bird internals so I don't know if bird<br>
keeps track of the exported routes per protocol.<br>
</blockquote></div></div>