[j-nsp] Convergence time

[Melchior Aelmans]

Hi Dovid,

MX5 might not be the ideal platform handling multiple full table BGP
sessions. This is due to it's somewhat slower CPU compared to other MX
routers.
You might want to limit the amount of full table or flapping sessions or
get yourself another platform. For example MX150 or 204 wouldn't have any
problem converging this amount of full tables.
Does this help?

Regards,
Melchior

On Wed, Aug 8, 2018 at 9:14 PM, Dovid Bender <dovid at telecurve.com> wrote:

> Hi,
>
> We currently have two MX5's with three upstreams (two of which have a BGP
> session with each MX5). We wanted to get full routes from all upsteams but
> were told by a few people at the time that should one peer drop out it
> would take 2-3 minutes before the MX5 would pull the routes for the
> upstream from the routing table. Now I am being told that it's not correct
> and should I lose a peer any routes that we got from that peer would
> instantly be dropped from routing table and the traffic would go to any
> other upstream that gave me that route or my static route. Is there any
> truth to this?
>
> TIA.
>
> Dovid
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>