Just installed 14 x MX960s for a large Aussie Mobile company - The release train we've decided on is 10.4R2 for now, due to EEOL support; and the fact that 10.0 didn't support a few of the cards we added. (16x10GE Trio for example didn't come till 10.2).
I have also hear that 10.4 also included a mass re-write/re-development of a lot of the JunOS code; trying to bring it back within a manageable framework. (Note how it went from 10.2R3 to 10.4, skipping a 10.3 release for some platforms). Hence, 10.4 is the "new" code base. I don't know if this is a good thing or a bad thing initially, but should only improve with time. I'd like to standardize all the other devices in my network to 10.4; once the "suggest JTAC releases" goes past 10.2R3 for things like SRX platforms. - Chris. P.S. JunOS may go to 3 releases per year now as well, so there may only be an 11.1/.2/.3 for 2011. On 2011-03-15, at 7:13 PM, Keegan Holley wrote: > I know the subject of JunOS versions has been beaten to death, but I've > never seen this specific question asked or answered. I'm trying to decide > between 10.0 or 10.4 for a network of MX, M (10i, 120 and 40e) and J series > routers. I'd like to choose a train with extended support. I'm trying to > decide between the risk of undiscovered bugs in 10.4 and having to upgrade > sooner when 10.0 goes EOS. We run L3VPN, with some L2VPN and a shrinking > VPLS footprint. Most of the M's and MX's have a full table with some acting > as regional route reflectors. Just wanted to get the general opinion of > those running similar applications. > _______________________________________________ > 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
