> Saku Ytti
> Sent: Saturday, July 30, 2016 11:48 PM
>
> This is all great. But I think either message customers send is misunderstood
> or correct fix is hard.
>
> Our main complain isn't that it takes long time to program FIB. Our complain 
> is
> that delta between software being updated and hardware being updated is
> too large. All the investments into redundancy are rendered useless when
> software starts sucking in traffic before it can forward it.
>
> HW and SW update times should be coupled. Of course fast FIB update is
> great and welcome, but it's far more important not to blackhole.
>
Now I have realized that there might be a problem which BGP PIC can't really 
solve.
And that's when the primary edge link/PE comes back online advertises it's 
prefixes to the rest of the AS and ingress PEs will actually install and start 
using these, sending traffic to egress PE sooner than it can actually forward 
it cause it's FIB is still being updated.
And for this specific case what you describe would be needed.

So essentially you're suggesting holding up BGP updates to peers until the 
router has it's FIB fully populated right?
I think that might be easier said than done, there would have to be a 
correlation between Protocol to RIB update job ID and RIB to FIB update job ID, 
so that each FIB update job is traceable back to the protocol which initiated 
it. Now what would constitute the job, single pfx a bulk of pfxes?

Anyways, till the triggered approach is implemented I think you can slow down 
iBGP update generation with the "out-delay" knob.
It's not as clear of a cut as with csco's "neighbor advertisement-interval" but 
looks like it can do the same thing.
https://kb.juniper.net/InfoCenter/index?page=content&id=KB26446&actp=search


adam









        Adam Vitkovsky
        IP Engineer

T:      0333 006 5936
E:      adam.vitkov...@gamma.co.uk
W:      www.gamma.co.uk

This is an email from Gamma Telecom Ltd, trading as “Gamma”. The contents of 
this email are confidential to the ordinary user of the email address to which 
it was addressed. This email is not intended to create any legal relationship. 
No one else may place any reliance upon it, or copy or forward all or any of it 
in any form (unless otherwise notified). If you receive this email in error, 
please accept our apologies, we would be obliged if you would telephone our 
postmaster on +44 (0) 808 178 9652 or email postmas...@gamma.co.uk

Gamma Telecom Limited, a company incorporated in England and Wales, with 
limited liability, with registered number 04340834, and whose registered office 
is at 5 Fleet Place London EC4M 7RD and whose principal place of business is at 
Kings House, Kings Road West, Newbury, Berkshire, RG14 5BY.
---------------------------------------------------------------------------------------
 This email has been scanned for email related threats and delivered safely by 
Mimecast.
 For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to