Re: [j-nsp] Juniper route age reset behavior

Hello Magnus, I would also prefer the old behaviour was retained as default, and that a configuration knob was provided to enable the new behaviour. My arguments to Juniper would be: - It should be a low-cost effort to make the code change so that TWO timers are kept, as the code alrea

[j-nsp] Juniper route age reset behavior

Hi We have seen a change in how junos handles age in command "show route". In Junos 15.1R bgp routes age told you how long the route had been present in the routing table. If you have a dual homed customer bgp age timer showed how long time ago the customer advertised the route. Very practical to

Re: [j-nsp] Experience with MX10003

Hi Niall, The turbo fib is set of route convergence optimisations in rpd(kernel update thread), kernel and pfe(trio). Released in 15.1F6 with ~25k r/s, pe

Re: [j-nsp] Experience with MX10003

Hey, > Giuliano C. Medalha > Sent: Thursday, January 25, 2018 6:43 PM > > We are testing the MX10003 right now. > > It is a pretty amazing box. > > The routing engine is so power for control plane ... bgp, ospf etc > So it doesn't take several minutes to import local routes to a newly configur

Re: [j-nsp] Experience with MX10003

Agreed with Mark. I have the same discussion with Giuliano about that. Expensive line cards against 40/100 mx204 or MX10003. We are using QFX5110 and QFX5100 at transport layer (P) where (up to)40km is the distance. Keeping MX960 and MX480 delivering services (PE). The detail about those MXs,