[c-nsp] dealing with MAC/IP length inconsistencies

[Jared Mauch]

On Tue, Nov 07, 2006 at 11:43:43AM -0800, Sukumar Subburayan wrote:
> There are ways to find out what packets are being dropped. But, it 
> involves some debugging commands to set some ASIC registers etc and use a 
> dummy span session to capture this. Because this is bit complicated and 
> involves careful setting of registers etc, I would suggest opening a TAC 
> case and have the TAC engineer walk through the steps.
> 
> We have enhancement bug open to make this debugging more customer 
> friendly.

	Yes, what's the bugid, and are either of the severities
above the level of 6?  What about some of the more critical DoS types
of issues, are those going to be addressed?

	It's starting to get frustrating to have all sorts of wonky
stuff impacting the box.

	- Jared

> On Tue, 7 Nov 2006, matthew zeier wrote:
> >Jared Mauch wrote:
> >>On Tue, Nov 07, 2006 at 12:26:48AM -0800, matthew zeier wrote:
> >>>Short of SPAN'ing every port on my switch with wireshark, is there a 
> >>>good way
> >>>to figure out which port's causing
> >>>
> >>>%MLS_STAT-SP-4-IP_LEN_ERR: MAC/IP length inconsistencies
> >>>%EARL_L3_ASIC-SP-3-INTR_WARN: EARL L3 ASIC: Non-fatal interrupt Packet 
> >>>Parser
> >>>block interrupt
> >>>
> >>>errors?
> >>>
> >>>I suspect not - is there a good wireshark/tcpdump filter to make this 
> >>>easier?
> >>
> >>	no mls verify ip ...
> >
> >Hurm.  That just masks the problem...
> >_______________________________________________
> >cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-nsp
> >archive at http://puck.nether.net/pipermail/cisco-nsp/
> >

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.