Hi,
On Thu, Aug 09, 2018 at 09:36:46AM +0200, Melchior Aelmans wrote:
> 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.
"abysmally and close to useless slow" describes the "somewhat slower"
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.
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
Hi,
times will depend on the type of failure.
If the upstream router fails but your link does not go down (for example
if there is a switch between the routers), you will have a BGP session
timeout after 3 minutes (with default config) and then the router starts
to change the routes, which can
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
5 matches
Mail list logo
