Getting error hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail

[PdhineshK]

Hi Team,

Currently we are getting the below error continuously in the cisco 2960x switch.

Need your inputs and solutions how to fix this error.

IOS running : 15.29(2r)E1 

hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail
hulc_sfp_iic_intf_read_eeprom sfp _index 2 yeti_iic_read_retry fail

[shimenoy]

Hi :)
Is it really 15.29(2r)E1?
I feel that the version is different, but the following may be helpful.

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-2960-x-series-switches/118837-technote-catalyst-00.html

[PdhineshK]

Hi shimenoy,



Sorry for typo its 15.2(2r)E1

[shimenoy]

Then, It's highly possible that CSCur56395 is the cause.
It might be better to consider upgrading the switch to fix releases.

[PdhineshK]

Thanks for the information.



We have the same switch which is running in the same environment we don't have this error but this switch only having the issue.



What is the version need to be upgrade to fix this issue?



Any workaround other than upgrade to fix this issue?

[shimenoy]

The Fix version is 15.2(2)E2 or later, but as a workaround

> CSCur56395
> Workaround:Power-cycle the devcie to recover from the condition.

So, once it restarts and see how it goes, how about having an upgrade if it recur?

[PdhineshK]

Sure shimenoy we will do the upgrade also but my doubt how the issue cause only on this switch?



If we restarted we will not get the message temporarily right?

[shimenoy]

Sorry, I don't know much more than written in CSCur56395.

But if, only that switch is stuck, the stack may be bad ...
I don't know without looking at other switches etc.

The following will also be helpful.

https://supportforums.cisco.com/t5/cisco-bug-discussions/cscur56395-2960x-link-may-go-down-randomly-with-glc-t-in-uplinks/m-p/2656550
https://supportforums.cisco.com/t5/cisco-bug-discussions/cscur56395-2960x-link-may-go-down-randomly-with-glc-t-in-uplinks/m-p/2647854

[PdhineshK]

Hi shimenoy,



FYI the switch is not connected in stack its separate switch running in the network

[Leo Laohoo]

If you're going to reboot the switch then you might as well upgrade the IOS to something more recent.

[PdhineshK]

Thanks for your information.



We will try to upgrade the IOS to latest