Reset Search
 

 

Article

i2c errors are logged for several optics

« Go Back

Information

 
Titlei2c errors are logged for several optics
Symptoms
The following i2c errors are logged for multiple transceivers connected in an Extreme Device
<Erro:HAL.Port.ReadOpticDDMIDataFail> Reading of DDMI data failed on the optical module in port 2:3.
<Erro:HAL.Port.Error> summitCardPortGetTransceiverInfoSfp: Unable to read DDMI info from Transceiver for port 2:3

<Erro:Kern.Card.Error> shid_ctrl_ioctl:5597 shidGbicReadI2CNb() returned -145
<Erro:Kern.Card.Error> shid_ctrl_ioctl:5597 shidGbicReadI2CNb() returned -145
<Erro:HAL.Sys.Error> summitReadSfpEepromDdmi: error reading i2cdev 0x51 nbytes 128

<Erro:HAL.Sys.Error> summitReadI2CDevMem: Read DevMem Failed for Gbic eeprom on port 10: shidFd 11 rc -1 bytes read 128



 
Environment
X670V
EXOS ALL
Cause
  • Third Party Optics
  • A bad transceiver
  • Faulty Switch
Resolution
  • Remove all third party optics and re-sit all Extreme certified optics.  Non Extreme Certified transceivers have been known to lock up the i2c, preventing other devices from accessing it
  • Run an extended diagnostic on the switch to test the integrity of the hardware.  On the off chance, the actual switch is faulty, an extended diagnostic test will show what is broken.  More information on how to run a diagnostic test can be found here:  How to Diagnose-hardware failures using EXOS
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255