[146260] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

R: Juniper MX960 Mqchip packet lenght error

daemon@ATHENA.MIT.EDU (Ferretti Antonio)
Tue Nov 8 10:34:01 2011

From: Ferretti Antonio <antonio.ferretti@telecomitalia.it>
To: "david.roy@orange.com" <david.roy@orange.com>, "nanog@nanog.org"
 <nanog@nanog.org>
Date: Tue, 8 Nov 2011 16:33:00 +0100
In-Reply-To: <19992_1320765182_4EB946FE_19992_10550_1_26812F15C2B5A8438D1C9BFCDEF73FEC2571539680@PMEXCB1A.intranet-paris.francetelecom.fr>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

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, Loopba=
ck: 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 packet=
s: 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 pa=
ckets
    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 w=
ay 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-----
Da: david.roy@orange.com [mailto:david.roy@orange.com]
Inviato: marted=EC 8 novembre 2011 16.13
A: Ferretti Antonio; nanog@nanog.org
Oggetto: RE: Juniper MX960 Mqchip packet lenght error

Hi,

See the PR587266. Maybe you have Syslog/log statement in a FW filter term.

Regards
David



David Roy
Orange - IP Domestic Backbone - TAC
Tel.   +33(0)299876472
Mob. +33(0)685522213
Email. david.roy@orange.com
Skype : davidroy.35
JNCIE-SP #703

Guest Haiku :
IS-IS screams,
BGP peers are flapping:
I want my mommy!



-----Message d'origine-----
De : Ferretti Antonio [mailto:antonio.ferretti@telecomitalia.it]
Envoy=E9 : mardi 8 novembre 2011 15:35
=C0 : nanog@nanog.org
Objet : Juniper MX960 Mqchip packet lenght error

Hi all,

After upgrading Juniper MX960 from 4x10Gbe DPCE to 16x10Gbe MPC, I see stra=
nge 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 per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne 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, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.

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


***************************************************************************=
*****
IMPORTANT.Les informations contenues dans ce message electronique y compris=
 les fichiers attaches sont strictement confidentielles
et peuvent etre protegees par la loi.
Ce message electronique est destine exclusivement au(x) destinataire(s) men=
tionne(s) ci-dessus.
Si vous avez recu ce message par erreur ou s il ne vous est pas destine, ve=
uillez immediatement le signaler  a l expediteur et effacer ce message
et tous les fichiers eventuellement attaches.
Toute lecture, exploitation ou transmission des informations contenues dans=
 ce message est interdite.
Tout message electronique est susceptible d alteration.
A ce titre, le Groupe France Telecom decline toute responsabilite notamment=
 s il a ete altere, deforme ou falsifie.
De meme, il appartient au destinataire de s assurer de l absence de tout vi=
rus.

IMPORTANT.This e-mail message and any attachments are strictly confidential=
 and may be protected by law. This message is
intended only for the named recipient(s) above.
If you have received this message in error, or are not the named recipient(=
s), please immediately notify the sender and delete this e-mail message.
Any unauthorized view, usage or disclosure ofthis message is prohibited.
Since e-mail messages may not be reliable, France Telecom Group shall not b=
e liable for any message if modified, changed or falsified.
Additionally the recipient should ensure they are actually virus free.
***************************************************************************=
*****


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne 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, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.



home help back first fref pref prev next nref lref last post