3 errors out of 1346614 packets... that's only 0.0002%. Less than 1% is acceptable (although not desirable). If the errors don't count up regularly, it could be leftover from when the cable was connected (sometimes when you connect a cable spurious errors are generated).
Maybe your thresholds are set too low in DFM (that was DFM output in your other email, right?). You could ratchet them up to over 1% of packets and it would reduce your alerts.
If the input errors count up regularly, check/replace the cable just to be safe. Also ask the SP to provide you with similar output to see if they see errors on their side. This may point to the cable or something generated by your router that you can't see (i.e. bad network card).
BTW, is there any performance degradation across this link? I wouldn't expect any problems with so few errors.
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...