On 22/Jul/15 02:59, Chris Kawchuk wrote: > I know that a ton of fixes on BGP convergence time son MX80 is definitely a > reason to be 'moving up'... however as you're on RE-2000s on MX480 may not be > applicable. > > I see you're running DPC cards, have you considered shifting those links onto > an MPC/Trio Card? (newer chip, more RAM, more horsepower, yadda yadda yadda > =)..) DPC was EOL a while ago, and everything has been Trio (and now Trio-NG > on the new -NG cards coming out now). As the FIB is pushed to hardware, it > may be some silly DPC thing you're running into. > > For things like Fusion or BNG or any other > new/advanced/this-is-what-PLM-is-thinking functions, we're already putting in > 14.2 on any new device we turn up, and have already started testing 15.1 for > the new NG cards we will likely be buying. Rest of our network is now on > 12.3R8 or 13.3 in many cases. (lots of BFD bugs have been squashed, some HQoS > issues fixed, host-outbound-traffic for BFD keepalives now honour the c-o-s > knobs, and are finally out of Queue 3 and into the Queue we want (7), etc... > preventing starvation if you happen to have re-used Queue 3 as "not-so-high" > priority, etc)... the list goes on. > > It's not a case of "if it aint broke, don't fix it" once you get 4-5 years > behind. You'll benefit from the years of "Oh, we finally fixed LLDP ascii > decoding" stuff that ends up getting traction; plus JTAC would really really > like it if you weren't on 11.4 =)
We've been on 14.2 for a while now, and settling into 14.2R3.8. Happy, to be honest. Only real problem is policing on LAG's, but it's manageable. Mark. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
