I assume that means that if a peer drops out of sight then for two minutes some of the traffic will drop? As of now we use default routes. If a bgp session drops the traffic shifts over fairly fast (under 30 seconds).
Regards, Dovid -----Original Message----- From: "Tim St. Pierre" <t...@communicatefreely.net> Sender: "juniper-nsp" <juniper-nsp-boun...@puck.nether.net>Date: Tue, 26 Apr 2016 09:09:32 To: <juniper-nsp@puck.nether.net> Subject: Re: [j-nsp] Full routes on MX5 I have one in a very similar configuration, with three full feeds in IPv4 and IPv6. It generally works just fine, but convergence time is slow. It can take two minutes to process the full feed, and if you restart the box, it will take even longer. It's a good machine for a small ISP though. -Tim On 2016-04-26 08:33 AM, sth...@nethelp.no wrote: >> Has anyone ever tried full IPv4 routes on a MX5? We have 3 peers + iBGP. We >> were told in the past that when a BGP session drops the MX5 could lock up >> for up to 2 minutes. > We have MX80s (essentially the same box) with full Internet routing > table. It works but is not recommended: RE memory (2 GB) is rather > limited, and convergence time is not great. > > Steinar Haug, Nethelp consulting, sth...@nethelp.no > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp -- Tim St. Pierre System Operator Communicate Freely www.communicatefreely.net 289-225-1220 x5101 _______________________________________________ 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
