Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

Switch logs generating i2c error and the PSU serial number is not displayed

« Go Back

Information

 
TitleSwitch logs generating i2c error and the PSU serial number is not displayed
Objective
  • Summit X670V-48x switch generating i2c error in logs and the PSU serial number is not displayed.

    ​-> show version        
    Switch      : 800399-00-12 1515N-44031 Rev 12.0 BootROM: 2.0.2.1    IMG: 16.1.3.6  
    PSU-1       : Internal PSU-1 NONE NONE
    PSU-2       : Internal PSU-2 800462-00-04 1336W-81727
    Image   : ExtremeXOS version 16.1.3.6 16.1.3.6-patch1-9 by release-manager
              on Mon Jul 18 10:45:49 EDT 2016
    BootROM : 2.0.2.1
    Diagnostics : 6.4
    
    as4-ids.summitx670v.sgeq1.6 # sh power 
    PowerSupply 1 information:
    State             : Powered On
    PartInfo          : Internal PSU-1 NONE NONE
    
    PowerSupply 2 information:
    State             : Powered On
    PartInfo          : Internal PSU-2 1336W-81727 800462-00-04
    Poll Interval     : 60 s
    Change Threshold  : N/A
    Change Action     : N/A
    
    as4-ids.summitx670v.sgeq1.10 # sh log
    04/11/2017 10:34:47.22 <Info:HAL.Sys.Info> Power usage data unknown for PSU Part name Internal PSU-1 NONE  in slot 1 due to Efficiency data lookup failed
    04/11/2017 10:34:47.22 <Info:HAL.Sys.Info> Input voltage to Internal PSU-1 is on. Output enabled.
    04/11/2017 10:34:31.22 <Info:HAL.Sys.Info> Input voltage to Internal PSU-1 is off. Output disabled.
    04/11/2017 10:34:31.22 <Info:HAL.Sys.Info> Internal PSU-1 is present.
    04/11/2017 10:33:45.19 <Info:HAL.Sys.Info> Internal PSU-1 is disconnected.
    04/11/2017 10:31:14.20 <Info:HAL.Sys.Info> Power usage data unknown for PSU Part name Internal PSU-1 NONE  in slot 1 due to Efficiency data lookup failed
    04/11/2017 10:31:14.20 <Info:HAL.Sys.Info> Input voltage to Internal PSU-1 is on. Output enabled.
    04/11/2017 10:30:58.31 <Info:HAL.Sys.Info> Input voltage to Internal PSU-1 is off. Output disabled.
    04/11/2017 10:30:58.31 <Info:HAL.Sys.Info> Internal PSU-1 is present.
    04/11/2017 10:30:27.22 <Info:HAL.Sys.Info> Internal PSU-1 is disconnected.
    04/11/2017 10:27:29.46 <Info:AAA.authPass> Login passed for user nhn_ids through telnet (10.64.62.226)
    02/20/2017 17:48:04.94 <Info:AAA.authPass> Login passed for user nhn_ids through telnet (10.25.194.17)
    02/20/2017 17:47:55.94 <Warn:AAA.authFail> Login failed for user nhn_ids through telnet (10.25.194.17)
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>   ack_error 1
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>   read_timeout 1
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>   busy 11
    02/15/2017 18:48:55.10 <Crit:Kern.Alert> Counters:
    02/15/2017 18:48:55.10 <Crit:Kern.Alert> silent 1, dumped 0, seq 2555384, busy (seq 2555374, sec 1062292, old 1)
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>     15.128657 1 BBSY : W 71 0000 00 1 4096
      02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.008797 0 BBSY : W 71 0000 00 1 0015
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.002263 0 RTMO : R 3e 0000 01 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.006494 0      : W 71 0000 02 1 fafa
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.000718 0      : W 71 0000 00 1 c096
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.002001 0      : R 3e 0000 03 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.006489 0      : W 71 0000 01 1 8011
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.000703 0      : W 71 0000 00 1 fafa
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.001999 0      : R 3e 0000 02 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.006479 0      : W 71 0000 01 1 8096
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.000645 0      : W 71 0000 00 1 8011
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.001999 0      : R 3e 0000 01 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.006588 0      : W 71 0000 01 1 fafa
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.000651 0      : W 71 0000 00 1 8096
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.001999 0      : R 3e 0000 03 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.006633 0      : W 71 0000 01 1 8011
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.000772 0      : W 71 0000 00 1 fafa
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.002772 0      : R 3e 0000 02 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.007071 0      : W 71 0000 01 1 c096
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.000664 0      : W 71 0000 00 1 8011
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.001999 0      : R 3e 0000 01 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>     14.880603 0      : W 71 0000 01 1 fafa
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.000682 1      : W 71 0000 00 1 8096
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.002025 1      : R 3e 0000 03 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.006453 1      : W 71 0000 02 1 a800
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.003534 1      : W 71 0000 00 1 fafa
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.001999 1      : R 3e 0000 02 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.006438 1      : W 71 0000 02 1 c096
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.000645 1      : W 71 0000 00 1 a800
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.001999 1      : R 3e 0000 01 3 
    02/15/2017 18:48:55.10 <Crit:Kern.Alert>      0.006473 1      : W 71 0000 02 1 fafa
    02/15/2017 18:48:53.42 <Crit:Kern.Alert>   1062277.446908 1      : W 71 0000 00 1 4096
    02/15/2017 18:48:53.42 <Crit:Kern.Alert> === i2c-1 error dump ===
    02/15/2017 18:48:38.28 <Crit:Kern.Alert> i2c-1: disable error messages
    02/15/2017 18:48:38.28 <Erro:Kern.Error> i2c-1: bus busy, addr=0x71 rw=0 cmd=0x0 size=1 retry=0
    02/15/2017 18:48:38.28 <Erro:Kern.Error> i2c-1: timed out for read 0 byte, addr=0x3e cmd=0x1
    02/06/2017 20:35:05.85 <Info:AAA.logout> User nhn_ids logout from telnet (10.64.62.227)
    
Environment
  • Summit X670V-48x
  • EXOS 16.1.3.6patch1-9
Procedure
Explanation:
  • The problem could be with switch such that the i2c channel might be busy or have got corrupted or stuck (causing read timeout) leading to the reported issue.
  • Also, it might be an issue with one of the optics is bad optics which is making the i2c bus busy.
​Next action:
  • Try to remove and re-insert the faulty PSU (If it has a redundant PSU).
  • Please collect the “debug hal show optic-info” output and try to figure out the bad optic (the optic with problem will probably have the optic type as unknown), if any of bad optics detected, remove that and check issue is still there?

as4-ids.summitx670v.sgeq1.20 # debug hal show optic-info port 17
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

  • If none of the optics detected as bad optics in “debug hal show optic-info” output, try to remove all the cables, optics one by one and check issue is still present. (Reboot after reinstalling the entire “GBIC")        Note:- Removing/re-inserting the GBIC's will cause traffic impact. Hence, perform the recommended troubleshooting during the scheduled maintenance window.
  • If the issue still present, run diagnostics test to check for any hardware failure.
  • Further information can be collected for investigation, 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