[j-nsp] 10.0 or 10.4?

[Paul Zugnoni]

After upgrading from 10.1 to 10.4R1.9 on a set of our dual-RE2000 MX960's we observed that the re1's fxp's were no longer IP-reachable. Console and session to "other-route-engine" both work fine, as does GRES. Same behavior on multiple dual-RE MXs. JTAC has confirmed the group config as OK, but hasn't been able to recreate the problem. I'd love to hear from anyone that has seen similar.

Paul Z

On Mar 17, 2011, at 16:52 , Keegan Holley wrote:

> Are these all 10.4R2 bugs or 10.2?
> 
>> 
>> PR588115 - Changing the forwarding-table export policy twice in a row
>> quickly (while the previous change is still being evaluated) will cause
>> rpd to coredump.
>> 
>> PR581139 - Similar to above, but causes the FPC to crash too. Give it
>> several minutes before you commit again following a forwarding-table
>> export policy change.
>> 
>> PR523493 - Mysterious FPC crashes
>> 
>> PR509303 - Massive SNMP slowness and stalls, severely impacting polling
>> of 10.2R3 boxes with a decent number of interfaces (the more interfaces
>> the worse the situation).
>> 
>> PR566782 PR566717 PR540577 - Some more mysterious rpd and pfem crashes,
>> with extra checks added to prevent it in the future.
>> 
>> PR559679 - Commit script transient change issue, which sometimes causes
>> changes to not be picked up correctly unless you do a "commit full".
>> 
>> PR548166 - Sometimes most or all BGP sessions on a CPU loaded box will
>> drop to Idle following a commit and take 30+ minutes to come back up.
>> 
>> PR554456 - Sometimes netconf connections to EX8200's will result in junk
>> error messages being logged to the XML stream, corrupting the netconf
>> session.
>> 
>> PR550902 - On a CPU loaded box sometimes BGP policy-statement evaluation
>> will simply stop working, requiring a hard clear of the neighbor (or
>> ironically enough, sometimes just renaming the term in the policy will
>> fix it :P) to restore normal evaluation.
>> 
>> PR521993 - Ports on EX8200 FPCs will sometimes not initialize correctly,
>> resulting in situations where for example ports 4 and 5 on every FPC
>> will be able to receive packets but never transmit them. If you continue
>> to try and transmit packets down a wedged port (such as would happen if
>> the port is configured for L2), it will cause the FPC to crash.
>> 
>> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp