Reset Search
 

 

Article

i2C-1 EEPROM related error message "Transceiver is not present on this port"

« Go Back

Information

 
Titlei2C-1 EEPROM related error message "Transceiver is not present on this port"
Symptoms
  • After upgrade random ports are down/not showing with transceivers information. These affected ports are in Ready state and traffic is not forwarded. 
  • Even if we move the existing connection to different ports, it will not solve the issue.
Following errors are seen in the switch logs:

01/04/2016 00:53:55.36 <Crit:Kern.Alert>      0.000439 0      : R 50 0000 6f 2
01/04/2016 00:53:55.36 <Crit:Kern.Alert>    117.300880 0      : R 50 0000 6e 2
01/04/2016 00:53:55.36 <Crit:Kern.Alert> === i2c-1 error dump ===

01/04/2016 00:53:55.36 <Erro:Kern.Error> i2c-1: bus busy after write, addr=0x74 cmd=0x0
01/04/2016 00:53:53.70 <Crit:Kern.Alert> i2c-1: disable error messages
01/04/2016 00:53:53.70 <Crit:Kern.Alert> i2c-1: enable error messages

01/04/2016 09:22:40.62 <Crit:Kern.Alert> i2c-1: enable error messages
01/04/2016 00:53:55.36 <Crit:Kern.Alert> === i2c-1 error dump ===
01/04/2016 00:53:55.36 <Erro:Kern.Error> i2c-1: bus busy after write, addr=0x74 cmd=0x0
01/04/2016 00:53:53.70 <Crit:Kern.Alert> i2c-1: disable error messages
01/04/2016 00:53:53.70 <Crit:Kern.Alert> i2c-1: enable error messages
11/12/2015 07:15:14.87 <Erro:Kern.Error> shid_ctrl_ioctl:5934 shidGbicReadI2CNb() returned -145
11/12/2015 07:15:14.77 <Erro:HAL.Sys.Error> summitReadSfpEepromDdmi: error reading i2cdev 0x51 nbytes 128                                      
11/12/2015 07:15:14.77 <Erro:HAL.Sys.Error> summitReadI2CDevMem: Read DevMem Failed for Gbic eeprom on port 1:shidFd 8 rc -1 bytes read 128  
                              
11/09/2015 01:01:10.01 <Crit:Kern.Alert> === i2c-1 error dump ===
11/07/2015 02:46:31.38 <Crit:Kern.Alert> i2c-1: disable error messages
11/07/2015 02:46:31.38 <Erro:Kern.Error> i2c-1: bus busy after first no-data transfer, addr=0x50 cmd=0x0
11/07/2015 01:41:58.17 <Crit:Kern.Alert> === i2c-1 error dump ===
11/07/2015 01:40:54.33 <Crit:Kern.Alert> i2c-1: disable error messages
11/07/2015 01:40:54.33 <Erro:Kern.Error> i2c-1: bus busy after first no-data transfer, addr=0x50 cmd=0x0
11/07/2015 00:22:03.50 <Crit:Kern.Alert> === i2c-1 error dump ===

11/07/2015 00:22:05.07 <Crit:Kern.Alert>      0.000439 1      : R 50 0000 68 2
11/07/2015 00:22:05.07 <Crit:Kern.Alert>      0.000440 1      : R 50 0000 67 2
11/07/2015 00:22:03.50 <Crit:Kern.Alert>    117.333915 1      : R 50 0000 66 2
11/07/2015 00:22:03.50 <Crit:Kern.Alert> === i2c-1 error dump ===
11/07/2015 00:21:20.04 <Erro:HAL.Port.Error> xcvr_read_eeprom: Failed read fd=74 errno=145(Connection timed out)                                          
11/07/2015 00:21:20.04 <Erro:HAL.Port.Error> xcvr_read_eeprom: Failed read fd=74 errno=145(Connection timed out)                                          
11/07/2015 00:21:20.04 <Erro:HAL.Port.Error> xcvr_read_eeprom: Failed read fd=74 errno=145(Connection timed out)

Kpg122d-dcs102.23 # debug hal show optic-info port 23
Port                       23
SFP or SFP+:               SFP
Signal:                    present
TX Fault:                  no
SFP/SFP+ Vendor:           WTD            
SFP/SFP+ Part Number:      RTXM191-552    
SFP/SFP+ Serial Number:    BP143700770390 
SFP/SFP+ Manufacture Date: 140915 
SFP/SFP+ Type:             SFP/SFP+
Connector:                 LC
GE Compliance:             1000BASE-SX
Wavelength:                850

Kpg122d-dcs102.5 # debug hal show optic-info port 16
Port                       17
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

pg122d-dcs102.8 #  sh port 15-19, 47, 48 transceiver information detail
Port :  15      
Error: Transceiver is not present on this port 

Port :  16      
Error: Transceiver is not present on this port


 
Environment
  • Summit X670-48x
  • 15.3.1.4
  • 15.7.2.9
Cause
  • The above reported error messages appears when I2C timeout happens while switch is trying to access it. The pluggable device inserted in switch (most probably the optics) could have locked the I2C bus and not releasing it properly.

Resolution
  • The reported issue can be cleared only by power cycling the problematic switch.
  • If you need further information, please contact GTAC for assistance.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255