Experincing issues with 2960X switch

[jlivingston]

Also seeing the same behavior, running same version of firmware.  Looking for answers.

Switch Ports Model              SW Version            SW Image                

------ ----- -----              ----------            ----------              

*    1 52    WS-C2960X-48TS-L   15.0(2)EX4            C2960X-UNIVERSALK9-M    

     2 52    WS-C2960X-48TS-L   15.0(2)EX4            C2960X-UNIVERSALK9-M

[Elton Babcock]

I think we are running EX3 and we aren't having this issue. We have a switch with with SFP modules installed up for a couple of months now with no issues.

Sent from Cisco Technical Support iPhone App

[pbooth230]

I have the same hardware with the same EX4 os, saw this error over the weekend.  I reseated the SFP and rebooted the switch.  Waiting for it to occur again.

[Krzysztof Jedraszek]

Do you have this issua on all stack members? I have it only on stack master. If i change stack master to other switch error ocures on next master but never on non master member.

Tomorrow i will downgrade IOS to EX3 and we will see what happens.

[nezz]

I too have started seeing this error today on the stack master. I swapped the transceivers onto the member switch and they are working ok so far. I'm running 150-2.EX3

[Ankur Arora · Accepted solution]

Adrian,

This error message is due to a bug, CSCul88801.

https://tools.cisco.com/bugsearch/bug/CSCul88801/?reffering_site=dumpcr

Downgrading the IOS to 15.0(2)EX3 should resolve the issue.

Thanks

Ankur

"Please rate the post if found useful"

[Lucas Hall]

Does anyone have a best practice for downgrading the IOS?  I have seen posts to use  the bin file and also posts to use to the tar file.  Is there a walktrough to change the IOS on a 2960X stack?

[Leo Laohoo]

Does anyone have a best practice for downgrading the IOS?  I have seen posts to use  the bin file and also posts to use to the tar file.  Is there a walktrough to change the IOS on a 2960X stack?

Won't make any difference whether or not you copy the BIN file across or unpack using the TAR file.  The main important thing is before you do anything is after you've downloaded either files you need to check the MD5 hash values of the file(s) you've downloaded against the MD5 hash value found on the Cisco website.

[Ankur Arora]

Lucas,

As far is the bin and tar files are concerned, use the tar file only if you use GUI access of the switch along with CLI.

Best practices would be:

Take a backup of the config before the upgrade.

Don't delete the old IOS image from the switch untill you have booted up the switch stack with the new image.

Verify the IOS image after copying it on the switch flash using the command: verify /md5

You can go through the below document for the IOS upgrade procedure:

http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a00804799d7.shtml

(The doc is for 3750 IOS upgrade, but the IOS upgrade procedure for 2960X stack is exactly the same)

Thanks

Ankur

"Please rate the post if found useful"

[Jason Williamson]

I have made it a practice to always use the tar files, as the tar files auto-run all the necessary scripts to complete the upgrades, etc.

[Tinya Cheng · Accepted solution]

Edit: Please see CSCur56395, resolved in 15.0(2a)EX5.

[Krzysztof Jedraszek]

Hi

After two weeks on EX3 there is no hulc error messages any more.

Everything seems to be ok.

[Lucas Hall]

EX3 also resolved the issue for me!  Thanks all!

[suriya charoenchutitavorn]

Hi Team

We happen case GLC-T with Catalyst 2960 Hang , It can't work 

We was reload switch but same ( GLC-T with Catalyst 2960 Hang)

and use command bellow  

Switch97#
Switch97#
Switch97#sh int gi 1/0/26 transceiver 5 transceiver de
Switch97#sh int gi 1/0/25 transceiver detail 
hulc_sfp_iic_intf_read_eeprom sfp _index 0 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 0 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 0 yeti_iic_read_retry failDiagnostic Monitoring is not implemented.

Switch97#
Switch97#
Switch97#sh int gi 1/0/25 transceiver detail 6 transceiver        de
Switch97#sh int gi 1/0/26 transceiver detail 
hulc_sfp_iic_intf_read_eeprom sfp _index 1 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 1 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 1 yeti_iic_read_retry failDiagnostic Monitoring is not implemented.

We try IOS Software EX3, EX4, EX5 and 15-2.2 but can't problem 

Please suggest case to me

[jackson.ku]

Do you mean you got the same issue at IOS EX3, EX4, EX5 and 15-2.2?

The issue was not resolved. The temporary workaround is not use GLC-T...

We have open TAC case, but TAC need more information while the issue occur again, but my customer not allow to reproduce this issue in production environment.

Can you provide me the following information while issue occur for reference?

-console log

-show clock

-show tech

-show log

-show interfaces / 3 times

-show interfaces X transceiver properties  / X is suspect port

-show interface X capabilities  / X is suspect port

-show inventory

-show idprom interface X  / X is suspect port

-show controllers ethernet-controller phy detail / X is suspect port