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

Tomas Caslavsky tomas.caslavsky at gmail.com
Mon Jan 23 10:26:03 EST 2012


HI,

yep we have same recommendation from Juniper.
New problematic feature can be disabled on FPC level by:

set ichip selfping disable

But it must be entered to every singe FPC (based on ichip ) if router or 
fpc is rebooted.

Regards

Tomas



Dne 23-Jan-12 16:20, OBrien, Will napsal(a):
> 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



More information about the juniper-nsp mailing list