[j-nsp] PSN-2010-12-112

Thomas Eichhorn te at te3networks.de
Sat Jan 29 05:40:55 EST 2011


Well, not really, I have had the problems on MPC-Only systems,
and they still have some quirks in it - I'm really waiting for
10.2R4 in which they promised to have fixed all of 'my' bugs..

Tom

Am Fri, 28 Jan 2011 16:22:06 -0600
schrieb Richard A Steenbergen <ras at e-gerbil.net>:

> On Fri, Jan 28, 2011 at 04:32:06PM +0000, Bill Blackford wrote:
> > Anyone on list know whether this only applies to DPC MPC line cards
> > on chassis-based MX's (240, 480, 960) or would this include the
> > MX80 as well?
> 
> They're talking specifically about bugs related to the interoperation
> of DPC (I-chip) and MPC (Trio) cards. MX80 is all Trio, so you don't
> have those bugs specifically, but there are many other issues not
> covered by this bulletin which should send you running from
> 10.2R1/R2/R3 and 10.3R1 on Trio in general. As I just said in another
> email, 10.3R2 has been much better than all of our 10.2 MX/Trio
> deployment experiences, though it's far from perfect. I can't speak
> to 10.2S5, but I do know 10.2S6 has a major issue that makes it easy
> to kernel panic. :)
> 



More information about the juniper-nsp mailing list