To reply to my own email. I tried running 10.4R3 on the MX960, but immediately it reported MQCHIP errors.
Mar 23 08:10:17 jun-tc2_re0 fpc4 MQCHIP(0) LI Packet length error, pt entry 9 Mar 23 08:10:18 jun-tc2_re0 fpc4 MQCHIP(0) LI Packet length error, pt entry 0 Mar 23 08:10:19 jun-tc2_re0 fpc1 MQCHIP(1) LI Packet length error, pt entry 28 Mar 23 08:10:20 jun-tc2_re0 fpc9 MQCHIP(1) LI Packet length error, pt entry 0 So we are back on 10.3R3 again, this time without rpd at 100% CPU. On the maillist of a large European Internet exchange there was a post of another network that had to downgrade to 10.3 due to a big issue with IPv6 that affects all 10.4 releases. (PR/593849) So it seems 10.4 is certainly a version to avoid for now. Dear Juniper, if you are reading this; Please, please pretty please deliver _one_ single version of Junos that can run plain v4/v6 ospf and bgp with MX/trio in a decent fashion. With sugar on top..... ? Bas On Tue, Mar 22, 2011 at 5:18 PM, bas <[email protected]> wrote: > Well, after this thread I still didn't know which version I should > choose for our 960 with MPC's only. > From what I read it was; In the field (Ras, Raphael) we see 10.3r3 as > the better choice, and people who talk to JTAC say 10.4r2 is the > better choice. > > (Of course it depends on configuration and config.) > > But we chose to upgrade to 10.3r3, and installed the version this morning. > The upgrade seemed to have gone smooth, but after all BGP sessions had > been re-established, and prefixes re-learnt the CPU stayed at 100%. > > Dropping to shell I saw rpd consuming 99% CPU. > Looking at task accounting and rtsockmon I saw no obvious causes. > A failover to the backup RE had no effect, the new master RE consumed > 100% within a couple of minutes. > > A colleague of mine did a trace of the process saw that the cycles are > being consumed by "getrusage" system calls. > > Tomorrow morning we'll try to restart routing, if that has no effect > we will try 10.4r2. > > I'll post tomorrow our findings.. > > Bas > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
