[j-nsp] Junos 10.4R8 on MX (PR 701928)

[Paul Goyette]

We expect that this will be fixed in 10.4R9 when it released.

We cannot, of course, recommend that you upgrade to 10.4R9 until
after it has been released.  This is expected to occur within a
very few weeks.

I am working to confirm which components are affected and to get
the on-line information corrected.


> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> bounces at puck.nether.net] On Behalf Of OBrien, Will
> Sent: Monday, January 23, 2012 7:21 AM
> To: bas
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Junos 10.4R8 on MX (PR 701928)
> 
> I opened a TAC case on this as my production boxes are on 8.5 now.
> I'm told that this does affect 10.4r8.5.
> It's been recommended to go to r7.5 for now if I want to stick with
> 10.4.
> 
> Thoughts?
> 
> 
> On Jan 23, 2012, at 9:16 AM, bas wrote:
> 
> > Hi,
> >
> > On Mon, Jan 23, 2012 at 3:57 PM, Daniel Hilj <daniel.hilj at ipnett.se>
> wrote:
> >
> >> This is a critical defect which effects only DPC, and not MPC.
> >> Customers with DPC is discourage using Junos 10.4R8, 10.4S8(A), and
> >> 10.4S8(B).
> >
> > Strange, I see:
> >
> > ---
> > SYNOPSIS 	MPC may restart with backtrace in ia_wpkt_next() routine
> > RELEASE NOTE 	Introduced in Junos software version 10.4R8, a DPC
> may
> > restart unexpectedly [snip]
> > ---
> >
> > So the Synopsis mentions MPC..
> >
> > Bas
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> Will O'Brien
> University of Missouri, DoIT DNPS
> Network Systems Analyst - Redacted
> 
> obrienh at missouri.edu
> 
> 
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp