Input errors: Gives the total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so this sum might not balance with the other counts.
Overruns: Gives the number of times that the serial receiver hardware was incapable of handing received data to a hardware buffer because the input rate exceeded the receiver's capability to handle the data.
Input errors: Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input error count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.
Overruns: Shows the number of times that the receiver hardware was incapable of handing received data to a hardware buffer because the input rate exceeded the receiver's capability to handle the data.
Its very much important to check for how long the errors are been occuring. You need to clear the counters for the serial or fast eth and check if these errors are on regural basis or on daily.
The input errors will incerese when there is loss in packet transmition. If this is high you may notice a degradiation in the line or interface.
below are the links for serail and eth troubleshooting.
besides encapsulation,L1/L2 error...you can control, something you can not control, one of the things is DDOS, I am not sure what happened there, but I guest when the traffic and error number increase abnormally, pls check on input packet whether there are lots of packet that only size 1K or maybe hundreds bytes and they are all aim at a destination IP.
whether lost packets when you Ping peer?
did you use "IP route-cache flow" on the interface?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...