Hey, Personally my strategy with software has always been:
a) start with latest long term release b) if you need bug fixes, update to rebuilds c) if you need new features, update to latest long term release I don't think software is like wine, I don't think it gets better as it ages. And Juniper has done lot of good work on quality which only applies to late releases. 15.1 will be EOL in under half a year. Just for support you want at least 16.1, but then why not jump straight to 17.3? What ultimately makes you experience positive or negative can be behind complex set of variables which poorly translates to other networks. Rarely there is some vintage release number which is universally good or universally bad. I'd start testing 17.3 and go from there. On 12 December 2017 at 11:52, Karl Gerhard <karl_g...@gmx.at> wrote: > Hello > > we've had very bad experience with Junos 15.1 on our switches (EX4550, > EX4300, EX4200). > Now we're getting new MX960s with 2xRE-S-X6-64G and unfortunately the minimum > required Junos version for this RE is 15.1. Can anyone share their experience > with Junos 15.1 on MX960? Is it as bad as it is on the switches? Would it be > wiser to jump directly to 16.1/16.2/17.1/17.2/17.3? > > We're especially interested in bugs/problems related to MC-LAG. > > Regards > Karl > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp -- ++ytti _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp