[j-nsp] L3 incompletes

[Jeff Groth]

That was my understanding as well.  CDP packets.

Jeff
(currently on Juniper withdrawal)




> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Chris Robb
> Sent: Saturday, December 06, 2003 4:03 PM
> To: Phil Rosenthal
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] L3 incompletes
> 
> 
> I believe we've always believed they were CDP packets. Dunno 
> where that  
> thought originated from, but I'd be interested if anyone else 
> has dug  
> any deeper.
> 
> -Chris
> 
> 
> On Dec 5, 2003, at 3:40 PM, Phil Rosenthal wrote:
> 
> > I noticed that all of my links between my Junipers and my Bigirons
> > that are doing vlan tagging have about 4 "L3 incompletes" 
> per second  
> > (monitor interface ge-x/y/z).
> >
> >
> > Per juniper:  
> > http://www.junipernetworks.lt/techpubs/software/junos/junos55/ 
> > swcmdref55-interfaces/html/vt-monitor2.html
> > 	◦ 	L3 incompletes
> > This counter is incremented when the incoming packet fails Layer 3  
> > (usually IPv4) sanity checks of the header. For example, a 
> frame with  
> > less than 20 bytes of available IP header would be 
> discarded and this  
> > counter would be incremented.
> >
> > Has anyone ever bothered to try to figure out what these 
> packets are?
> >
> > --Phil Rosenthal
> > ISPrime, Inc.
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> >
> >
> Chris Robb
> Indiana University Global NOC Engineer
> chrobb at indiana.edu  Desk: 812-855-8604
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>