[j-nsp] Layer3 incompletes increasing

[Greg.Griffis at cox.com]

This sounds like an issue that Juniper reported as a cosmetic PR.  I
can't seem to find the PR number.  IIRC, it has to do with the fact that
the router is counting filter rejects/discards as L3 incompletes.  If
you are in a lab environment you may consider removing all filters
including "protect-re" and see if this stops the L3 incompletes.

Thanks,

Greg Griffis
Data Network Engineer - Backbone & Peering
Cox Communications
greg.griffis at cox.com
ASN 22773 <-> http://www.cox.com/peering

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Niels Bakker
Sent: Wednesday, May 11, 2005 12:49 PM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Layer3 incompletes increasing

Hi,

* efraim at clues.de (Alexander Koch) [Wed 11 May 2005, 17:57 CEST]:
>On Wed, 11 May 2005 17:41:37 +0200, Niels Bakker wrote:
>[..]
>> None of those are happening on my LAN.  I've sent JTAC pcap files
from a 
>> traffic analyser right between the switch and the router but they
don't 
>> seem to be able to figure it out either.
>Incidentally I see the L3 incompletes on a certain IX port 
>in Amsterdam as well. So that makes me even more clueless, 
>as I understand I cannot catch them on the Juniper as the 
>throwing- away is taking place before I can capture them.
>
>But then, it is definitely between 6.3R2 and 6.3-20050114.0 
>so it cannot be that hard to trace down...?!

I heard from other people that those started when they went from 5.x to 
6.3, they could've also been in 6.0, I don't recall exactly.


>> What I've found out so far is that nobody in the world really knows
when 
>> or why the "L3 Incompletes" counter increases; that it's 8-bits in
the 
>> hardware; but also that it and the "DA Rejects" counter step in close

>> harmony (at least in my case), which I'm still investigating.
>Yes, the 'DA Rejects' are increasing as well, I noticed that 
>as well.

Those are pretty much accounted for by unknown unicast getting flooded
by switches of a certain exchange point.  But those shouldn't be counted

as L3 incompletes (if they are, which I haven't had time to verify yet).


	-- Niels.

-- 
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp