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/configuration/guide/2_xe/irg_xe_book/irg_slow_peer_xe.html Okay, so maybe not recently... Mark. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
