experts,
we are experiencing a constant presence of L3 incomplete on a 1 Gige
PIC. This is ~1 every 5 mins. Any idea what can be the reason?
The Junos doc says This counter increments when the incoming packet
fails Layer 3 (usually IPv4) checks of the header. For example, a frame
with less than
-Original Message-
From: [EMAIL PROTECTED] [mailto:juniper-nsp-
[EMAIL PROTECTED] On Behalf Of Paul Goyette
Sent: Friday, June 13, 2008 10:12 AM
To: Lakshminarayanan P; juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] L3 incompletes
My 2 cents -
The most common reason for this
No, that should result in policed discards, not L3 incompletes.
This commonly shows up when the neighbor is from Brand-C and has
cdp enabled. :)
I'm hesitant to attempt to correct anyone with a
juniper.net address, but I'm not sure this is entirely
true. Discarded OSPF packets
No, that should result in policed discards, not L3 incompletes.
This commonly shows up when the neighbor is from Brand-C and has
cdp enabled. :)
Well, I have come across increase in L3 incomplete errors previously when
testing with a M320 connected back to back on Ethernet to another
If I understand what you are saying it seems that rancid may be the
answer you need. Check it out:
http://www.shrubbery.net/rancid/
2008/6/13 Joe Shen [EMAIL PROTECTED]:
Hi,
we want to monitor special E320 configuration
segment to avoid inconsistence between BRASes.
Searching with
5 matches
Mail list logo