[j-nsp] EX4200 JunOS Recommendation
juniperdude at gmail.com
Mon Nov 8 16:46:54 EST 2010
We've now settled on 10.2R3 on our EX4200s, and EX2200s. When I tried to do "upgrades" to the "JTAC recommended releases" I managed to almost brick my EX2200's in the process. (i.e. when booting, they simply waited 15 mins for mgd to settle, amongst other nasty deadlocking situations in the boot process. Had to Ctrl-C the boot process a few times on a few different EX2200s and EX4200s on the "Juniper's Recommended Releases".
Again, this is just what is working for us....
There's a nasty known-bug with 10.2R3 on MXes, but that's not related to the EX line (I hope); as it's MPC/DPC related (and not just to Trio cards, ras =)).
> From: Richard A Steenbergen <ras at e-gerbil.net>
> Date: November 9, 2010 6:59:13 AM GMT+11:00
> To: Mehmet Akcin <mehmet at icann.org>
> Cc: juniper-nsp <juniper-nsp at puck.nether.net>
> Subject: Re: [j-nsp] EX4200 JunOS Recommendation
> .... You'd have better luck picking good versions of code with a magic
> 8ball. Unfortunately I can't tell you specifically what works best for
> L2 on EX4200 because we use none of the first and very little of the
> second, but I can give you a very very long list of reasons why 10.2R3
> is (at this exact moment) the best choice for EX8200 doing routing.
On 2010-11-09, at 6:31 AM, Keegan Holley wrote:
> Greetings all,
> I'm looking for a code recommendation for EX4200's. I'm planning some
> network wide upgrades and I have an idea of what I want to run, but I was
> curious what the list would recommend. Most of the switches will be layer-2
> only with, 10G or AE uplinks, VC of course. We've run into some
> pretty significant bugs in the past, just wondering what everyone else is
More information about the juniper-nsp