On Mon, Jun 27, 2011 at 11:05:48AM -0600, David Ball wrote: > I know it's unreasonable to have people continually posting to the > list asking about which code is best, but I know many were waiting for > a stable 10.4 revision (due in part to its' EEOL nature) but last I > heard, 10.4R2 (or was it R3) wasn't ready for primetime. Didn't find > much in the archives about 10.4R4.
10.4R4 has been the least problematic code on MX (either trio or ichip, but not mixed) that we've seen in a very long time, probably at least 1.5 years. There were a handful of mostly minor issues in it, but in theory they've been fixed in 10.4R5 (though we have only a couple of routers running R5 so far, so we don't have a massive experience base yet). As always it varies by your feature set, but for a v4/v6/mpls/bgp heavy core router things are finally starting to look up. About damn time too. :) -- Richard A Steenbergen <r...@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
