Same story, here.. Upgraded to 10.4R3.4 on an MX480 with MX-MPC2-3D, here's what I've got:
Mar 30 06:30:05 sns480-re0 fpc0 MQCHIP(0) LI Packet length error, pt entry 14 Mar 30 06:30:06 sns480-re0 fpc0 MQCHIP(0) LI Packet length error, pt entry 0 Mar 30 06:30:40 sns480-re0 fpc0 MQCHIP(0) LI Packet length error, pt entry 10 Mar 30 06:30:41 sns480-re0 fpc0 MQCHIP(0) LI Packet length error, pt entry 0 Is it causing any adverse effects, or simply being annoying in the logs? Has anyone confirmed? I haven't filed anything with JTAC (..yet), but this router isn't in production (..yet) for IPv4, and this isn't my first issue with 10.4R3.4. -- Jonathan Towne On Fri, Mar 25, 2011 at 12:04:43AM +0100, Daniel Roesen scribbled: # On Thu, Mar 24, 2011 at 10:19:59PM +0100, bas wrote: # > 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 # # We see that on MX80 too, right since upgrading the (totally idle) box. # Pending JTAC response... # # Best regards, # Daniel # # -- # CLUE-RIPE -- Jabber: d...@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0 # _______________________________________________ # juniper-nsp mailing list juniper-nsp@puck.nether.net # https://puck.nether.net/mailman/listinfo/juniper-nsp # _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp