Agreed...could be cable. Also could be dirty patch panel (if there is one) or a faulty SFP on either end. I have also seen this with mismatched SFPs and cable type. IE, when you have 1310 nm SFPs with multi mode cable.
If you think you can live with it, you can configure the port to ignore them. There is a default setting (that you can't change) where if you get x amounts of errors in a 5 minute period, the port shuts down. You can just ignore them with the command:
switchport ignore bit-errors
I would keep an eye on the port through syslog (or perhaps SNMP traps if configured properly) as they will raise bit-error related messages even though you told the port to ignore them.
I have found the cables (including fobot ports/cables) to always be the problem here. Don't just fiddle with the cables, replace them. SFPs are not generally the cause of the problem and I have never seen a storage array front itself cause any problems.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...