Juniper MX960 Mqchip packet lenght error

Mailman List Mirror (Read Only)
1

Hi all,

After upgrading Juniper MX960 from 4x10Gbe DPCE to 16x10Gbe MPC, I see strange log messages like this:

Fpc10 MQCHIP(0) LI Packet length error, pt entry 22

Seems to be only a "cosmetic" message, but today my team found some traffic dropped on interface on this card (before we only request check about log message).
Has anyone the same problem?

My software release is Junos 10.3R3.7.

Thanks in advance.

Antonio Ferretti
Network Engineer
Telecom Italia Sparkle
Backbone IP&Data Operations
Seabone 2nd Level Support
Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000001@TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non ? necessario.

logo Ambiente_foglia.gif

2

Thx David,

PR587266 seems to be related to "maximum-packet-lenght" command that is not present in my config.

Biggest problem in this case are dropped packet on interface:

Physical interface: xe-10/0/1, Enabled, Physical link is Up
  Interface index: 363, SNMP ifIndex: 645, Generation: 483
  Description: No Description
  Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, Loopback: None, Source filtering: Disabled,
  Flow control: Enabled
  Device flags : Present Running
  Interface flags: SNMP-Traps Internal: 0x4000
  Link flags : None
  CoS queues : 8 supported, 8 maximum usable queues
  Hold-times : Up 0 ms, Down 0 ms
  Current address: 00:24:dc:49:be:73, Hardware address: 00:24:dc:49:be:73
  Last flapped : 2011-10-27 03:11:07 UTC (1w5d 12:18 ago)
  Statistics last cleared: 2011-11-08 13:15:03 UTC (02:14:38 ago)
  Traffic statistics:
   Input bytes : 4674308593808 5182909688 bps
   Output bytes : 6092283580895 6656998280 bps
   Input packets: 8393093736 1149495 pps
   Output packets: 6971170539 941600 pps
   IPv6 transit statistics:
    Input bytes : 23569859
    Output bytes : 0
    Input packets: 197870
    Output packets: 0
  Dropped traffic statistics due to STP State:
   Input bytes : 0
   Output bytes : 0
   Input packets: 0
   Output packets: 0
  Input errors:
    Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,
    L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
  Output errors:
    Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0,
    MTU errors: 0, Resource errors: 0
  Egress queues: 8 supported, 8 in use
  Queue counters: Queued packets Transmitted packets Dropped packets
    0 be 6973872756 6887958719 85914037
    1 ef 25695717 25695717 0
    2 ef1 2062122 2062122 0
    3 ef2 21430966 21430966 0
    4 af 2605818 2605818 0
    5 af1 1577987 1577987 0
    6 nc 5928647 5928647 0
    7 nc1 24705296 24705296 0

I'm wondering if is something related to CoS that is managed in different way from the two type of linecard.

Regards

Antonio Ferretti
Network Engineer
Telecom Italia Sparkle
TIS.AD.NDO.O Backbone IP&Data Operations
Seabone 2nd Level Support
Via di Macchia Palocco, 223
00125 Roma, Italia
-----Messaggio originale-----

3

After upgrading Juniper MX960 from 4x10Gbe DPCE to 16x10Gbe MPC, I see strange log messages like this:

Fpc10 MQCHIP(0) LI Packet length error, pt entry 22

Seems to be only a "cosmetic" message,

PR/593386 "and others". Wenth thru that half a year ago. :slight_smile:

but today my team found some traffic dropped on interface on this card
(before we only request check about log message).
Has anyone the same problem?

Yes. We were told: cosmetic only, and we saw no impact.

Trigger was a "then log" in the lo0.0 firewall filter.

My software release is Junos 10.3R3.7.

Would match. Above PR is fixed in 10.3R4, 10.4R4, 11.1R2 and newer

Best regards,
Daniel