[c-nsp] Gigabit Interface Input Errors

[Drew Weaver]

Thanks for responding,

As far as you're aware is there a way to check the hardware buffer to see if this is the case, and is this buffer usually per line card, or per slot (both/either?)

-Drew


From: Darin Herteen [mailto:synack at live.com]
Sent: Thursday, November 05, 2009 1:54 PM
To: Drew Weaver; cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] Gigabit Interface Input Errors

Drew,

Overruns are usually caused by the receiving hardware buffer being "flooded" for lack of a better term because the input rate exceeded the receiver's ability to handle the traffic.

Darin

> From: drew.weaver at thenap.com

> To: cisco-nsp at puck.nether.net
> Date: Thu, 5 Nov 2009 13:41:16 -0500
> Subject: [c-nsp] Gigabit Interface Input Errors
>
> Hi,
>
> I noticed I'm seeing some Input errors on a gigabit ethernet interface:
>
> 70 input errors, 0 CRC, 0 frame, 70 overrun, 0 ignored
>
> the number of input errors seems to increment along with the overrun counter which I assume means that the actual errors are overrun errors.
>
> Does anyone have any tips on finding out what is causing it to overrun?
>
> My first inclination is to assume it is not a huge problem because of the amount of packets that are flowing through this interface:
>
> 2367831951 packets input, 247924231216 bytes, 0 no buffer 70 out of 2367831951 is a fairly small number but I wanted to check and see if you all had any thoughts.
>
> thanks,
> -Drew
>
>
>
>
>
>
> _______________________________________________
> 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/
________________________________
Bing brings you maps, menus, and reviews organized in one place. Try it now.<http://www.bing.com/search?q=restaurants&form=MFESRP&publ=WLHMTAG&crea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1>