I cannot get switch to communicate via Fiber. As soon as sfp is plugged into port, error comes up.

https://www.experts-exchange.com/questions/21879463/CISCO-3550-Port-Error-Disabled.html

To reenable them just do a shut and no shut. You can configure it to come back automatically on some system, I have to check on that one. But that will only happen if the source of the problem is cleared.

Regarding how they got that way, there can be many reasons. Here are 3:
1. Too many errors received on the port
2. If portfast is enabled and something is connected that generates BPDUs, BPDU guard will do it.
3. If they were put in a port channel and there were problems with that

Make sure you have logging enabled. If you reenable the port and it error-disables again, a log entry may tell you the cause.

Hi,

It's alive! It's alive!

Well, it took a couple of commands and replacement of the SFP, but it now works. Seems that the Cisco 2Gb SFP's are NFG, The used Finisar 4Gb SFP's are working ok. Finisar is btw one of the 3 vendors that actually make SFP's for Cisco.

In addition, some commands had to be added to the switch:

coreGIG01(config)#service unsupported-transceiver
coreGIG01(config)#no errdisable detect cause all
coreGIG01(config)#no errdisable recover cause all

Thanks for your help and input.

Brent

So my response was correct in saying that the problem was caused by bad SFP modules, cabling etc.  The only problem with doing no errdisable is that if there are problems in the future it will not cause the interface to drop but instead cause latency and packet loss

My solution should be awarded the points.  I clearly pointed him in the correct direction and advised what was causing the trouble.  

RTh0037 should have the points. He did point me in the right direction.

Thanks All

Brent

After awarding the points this is closed.

Cheers,

Brent