[j-nsp] EX 10.0S10.1
Keegan Holley
keegan.holley at sungard.com
Wed Nov 17 16:38:56 EST 2010
On Tue, Nov 16, 2010 at 4:44 PM, Bill Blackford <BBlackford at nwresd.k12.or.us
> wrote:
> So I recently updated almost everything to 10.0R4.7 (I still have some
> stuff on 10.0S1.1). I'm not experiencing any issues, that I'm aware of. I
> would like to see the IGMP snooping issues ironed out, but for the most
> part, I'm content.
>
> My question is should I wait 'til the next recommended release, or is there
> a compelling reason I should update everything again, now? I am a little
> concerned about the [PR/546674 EX4200 Virtual Chassis problem not passing
> traffic] issue.
>
> Do you have more info on this bug? I searched the PR database but the bug
with that ID only lists the following.
**
*JUNOS PROBLEM REPORT NUMBER : 546674*
*JUNOS Problem Report Information*
*NUMBER*
546674
*SEVERITY*
critical
*CATEGORY*
sw
*STATE*
open
*SYNOPSIS*
pfem core 0x018f599c in nh_composite_add (nh_params=0x9068ed48,
nh=0x906d6bb8)
*ARRIVAL DATE*
2010-08-24 23:29:04
*LAST MODIFIED*
2010-11-11 18:10:22
*CLOSE DATE*
-
*RELEASE NOTE*
The PFE core-dump may happen due to the case of having non-existent l2
unicast-nh. This core dump will not be seen with the fix.
More information about the juniper-nsp
mailing list