MX80 (5-10-40) is a very old platform with a cpu less powerful than your cell phone. 2-3 minutes seems to be a very good performance for this platform :)
I had a customer with 2* MX80 with peering and 4 full feed (95% or ram used !), and I have seen more than 8 minutes during a flap. Convergence is a pain on this hw. Unless you really need to have the full feed, you should consider to get a default route from your upstream and filter greater than /22 (or 21). MX204 will be the best choice (mx150 is a cpu based platform) Raphael Envoyé de mon iPhone > Le 8 août 2018 à 21:15, Dovid Bender <do...@telecurve.com> a écrit : > > 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@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
