Unanswered Question
May 18th, 2009
User Badges:

Has anybody encountered this kind of error "bitErrRTThresExceeded" for a port (connected to a server/storage)?

When we bounce the port the port comes up "on" but again goes down after a while with the above error.

Any ideas?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (2 ratings)
techcrazzy Mon, 05/18/2009 - 22:52
User Badges:

Hi Pavan,

it is the indication of link error.

check for the port errors.

I had similar issue and cable replacement resolved it..

Good luck.


Michael Brown Wed, 05/20/2009 - 07:13
User Badges:
  • Cisco Employee,

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

m-donnelly Tue, 06/02/2009 - 18:22
User Badges:

patch cables.

things to do:

1. check to make sure all patch cables and seated correctly. unplug and replug in.

2. clean the cables ends if you have the "special" cleaner pads

3. if you have a fiber power lose meter (dB) you could check the cables with that.

4. replace the patch cord.

pavanksharma Tue, 10/20/2009 - 10:58
User Badges:

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?

stephen2615 Tue, 10/20/2009 - 13:59
User Badges:
  • Bronze, 100 points or more

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.


m-donnelly Sun, 09/04/2011 - 21:56
User Badges:

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

Kris Vandecruys Mon, 09/05/2011 - 07:10
User Badges:
  • Cisco Employee,


BitError Threshold Exceeded means that you had more than an acceptable number of incoming CRC errors in a short timespan on an interface.

This is usually indicative of a bad fiber, or a bad SFP (optics/gbic) on either side of the link.

you can get a good indication of the quality of the link with the following command:

# show interface fcX/Y transc det

where fcX/Y is replaced by the interface you want to check out

It will show you the min and max alert and alarm values, so you know what your actual value should fall between.


This Discussion



Trending Topics: Storage Networking