[j-nsp] L3 incompletes

[Paul Goyette]

L3 incomplete means that the datagram received by layer 2 does
not have enough data to match the l3 header.

For example, if you get a 64-byte Ethernet packet where the IP
header says length is 200 bytes, that's L3 Incomplete.

Most frequently seen in ATM where a missed cell causes a short
packet;  usually but not always the AAL5 CRC will catch it...

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net]On Behalf Of Eric Van Tol
Sent: Monday, December 08, 2003 6:37 AM
To: juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] L3 incompletes


Policed discards are the CDP packets.  CDP is a layer 2 protocol, not
layer 3.

-----Original Message-----
From: Christopher Morrow [mailto:morrowc at ops-netman.net] 
Sent: Sunday, December 07, 2003 10:39 PM
To: jeff at groth.com
Cc: 'Phil Rosenthal'; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] L3 incompletes



On Dec 8, 2003, at 2:26 AM, Jeff Groth wrote:

> That was my understanding as well.  CDP packets.
>
> Jeff
> (currently on Juniper withdrawal)
>
>

Could you not log based on packet size SMALLER than the limit that 
would equal the 'incompletes' size and see what got logged?

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

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