[j-nsp] Junos BGP update generation inefficiency -cause for concern?
Adam Vitkovsky
Adam.Vitkovsky at gamma.co.uk
Mon May 18 08:39:14 EDT 2015
> From: Mark Tinka [mailto:mark.tinka at seacom.mu]
> Sent: 18 May 2015 13:23
>
> On 18/May/15 14:11, Scott Granados wrote:
> > I'm not sure exactly what you're looking for but the peer group system
> under JunOS is fairly efficient. If you set your export and import policies per
> group the bgp process will place these in a peer group and dynamically break
> off slow members in to their own groups so that one slower peer won't
> cause the other members in the same peer group to synchronize as slowly.
> Cisco does not or at least did not do this as I understand things. In the cisco
> case if a peer group member lags it causes the other members of the same
> peer group to lag and doesn't allow updates until the slowest member
> catches up. Since BGP under Junos breaks this slow guy off on it's own you
> don't have the same limitation. This all happens dynamically.
>
> If memory serves, Cisco recently developed some kind of feature to deal
> with slow peers to fix this very issue:
>
> http://www.cisco.com/c/en/us/td/docs/ios/ios_xe/iproute_bgp/configurati
> on/guide/2_xe/irg_xe_book/irg_slow_peer_xe.html
>
> Okay, so maybe not recently...
>
> Mark.
Hi Mark,
Haaha yeah that one has been around for some time already :)
adam
---------------------------------------------------------------------------------------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------
More information about the juniper-nsp
mailing list