I am getting input errors/runts on 2 of my gigabit interfaces that connect to our WAN service provider's network. In relation to total packets, its not a large number, so its probably not a big deal, but I'd just like to find the source so I stop seeing the errors in Solarwinds. Our service provider says that they don't see any errors on their side, but the errors are incoming to us.
I've tried to capture the traffic with Wireshark, but discovered that often these packets are either discarded or padded by NICs so Wireshark will not see them, or at least will not see them as undersized.
Is there any other way I can capture these packets so I can find the source and figure out how to stop them? Our equipment is 3750G running 12.2(55)SE. Its not a trunk port. I know there was a bug in prior IOS that would cause some frames to be marked as runts even though they were forwarded successfully.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...