Reset Search



i2C EEPROM error messages during reboot

« Go Back


Titlei2C EEPROM error messages during reboot
  • i2C EEPROM error messages during switch reboot could cause poor traffic performance from 10Gig from 1Gig speed (10M SFP+ Cable (Vendor: Siemon) connected on a port could act has 1Gig). 
  • The output "debug hal show optic-info" will not display the optics connected on the suspected ports.

09/05/2015 06:07:10.56 <Crit:Kern.Alert> === i2c-1 error dump ===
09/05/2015 06:06:57.33 <Erro:HAL.Port.Error> xcvr_read_eeprom: Failed read fd=75 errno=145(Connection timed out)
09/05/2015 06:06:57.33 <Erro:HAL.Port.Error> xcvr_read_eeprom: Failed read fd=75 errno=145(Connection timed out)                                 
09/05/2015 04:57:50.21 <Crit:Kern.Alert> === i2c-1 error dump ===
09/05/2015 04:57:36.80 <Erro:HAL.Port.Error> xcvr_read_eeprom: Failed read fd=75 errno=62(Timer expired)                       
09/05/2015 04:57:36.80 <Crit:Kern.Alert> i2c-1: disable error messages
09/05/2015 04:57:36.80 <Erro:Kern.Error> i2c-1: bus busy after first no-data transfer, addr=0x50 cmd=0xf

“debug hal show optic-info”

Port                       26
SFP or SFP+:               SFP
Signal:                    present
TX Fault:                  no
SFP/SFP+ Vendor:           
SFP/SFP+ Part Number:      
SFP/SFP+ Serial Number:    
SFP/SFP+ Manufacture Date: 
SFP/SFP+ Type:             Unknown
Connector:                 Unknown
GE Compliance:             UNKNOWN (0x0)
Wavelength:                0

  • Summit X670-48x
  • 10M SFP+ Cable (Vendor: Siemon)
  • Reported error messages appears normally happens when an optic is not inserted properly.  This can cause the I2C bus to timeout  while the switch is trying to access it. It may occur that one of the pluggable device inserted in switch (most probably one of the optics) could have locked the I2C bus and not releasing it properly.

  • The above logs indicate that the SFP+ inserted in port could not be read and also it has locked the I2C bus. Either that SFP+ could have some problem or not plugged in well.



Kindly perform the following steps in suspected switch ports

  • Remove and re-insert the optics (passive copper cable) in suspected ports.  

  • Replace the optics (passive copper cable), if the above step doesn’t help.

If any issues persists, please contact GTAC for assistance.

Additional notes

If issues still occur after remove/re-insert the optics, collect the following outputs and check with GTAC:

  • show ports transceiver information detail
  • show ports <port number> configuration no-refresh
  • debug hal show optic-info
  • debug hal show optic-info eeprom port <port number>
  • show tech
  • show log messages nvram



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255