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.

- Mike

Thanks all for replying to this post.

However, I have verified each one of the components SFIPs/cables/patch panels,switch port etc. Although, the error is rare but it does comes on and off on various ports at times.

Do you guys think this error could also relate to the end devices/port cfg on the devices/data from the devices etc?

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:

config

interface

switchport ignore bit-errors

exit

exit

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.

Stephen

the SFP could be failing. you might want to replace that and see if the problem still exists.