Reset Search
 

 

Article

'SPI-ROM' related error logs post bootup in a Summit X670V-48x.

« Go Back

Information

 
Title'SPI-ROM' related error logs post bootup in a Summit X670V-48x.
Symptoms
Post reboot the below logs are observed. 
06/20/2017 11:00:52.12 <Crit:Kern.Alert> 84740: p=20 SPI-ROM load: Bad Checksum (0x0)
06/20/2017 11:00:52.12 <Crit:Kern.Alert> Updating firmware on spi-rom from 0x105 (via mdio) to 0x105 on u=0 p=20 ...
06/20/2017 11:00:52.12 <Crit:Kern.Alert> 84740: p=20 SPI-ROM: Bad Checksum (0x0)
06/20/2017 11:00:52.12 <Crit:Kern.Alert> 
06/20/2017 11:00:52.12 <Crit:Kern.Alert> 84740: p=19 SPI-ROM load: Bad Checksum (0x0)
06/20/2017 11:00:52.12 <Crit:Kern.Alert> Updating firmware on spi-rom from 0x105 (via mdio) to 0x105 on u=0 p=19 ...
06/20/2017 11:00:52.12 <Crit:Kern.Alert> Otherwise the port being programmed may become unusable.
06/20/2017 11:00:52.12 <Crit:Kern.Alert> Please do not power off the switch during this process.
06/20/2017 11:00:52.12 <Crit:Kern.Alert> 84754 firmware update required. Installing version 0x105.
06/20/2017 11:00:52.12 <Crit:Kern.Alert> 84740: p=19 SPI-ROM: Bad Checksum (0x0)

06/20/2017 11:00:50.76 <Noti:ACL.Policy.UnCondPmtCanCauseLoop> ACL policy UPlinkacl: An unconditional PERMIT action on an EAPS or STP blocked port can cause a loop.
06/20/2017 11:00:50.76 <Info:pm.config.loaded> Loaded Policy: UPlinkacl number of entries 5
06/20/2017 11:00:50.76 <Info:pm.config.openingFile> Loading policy UPlinkacl from file /config/UPlinkacl.pol
06/20/2017 11:00:48.62 <Info:EPM.wdg_enable> Watchdog enabled
06/20/2017 11:00:45.74 <Noti:DM.Notice> Node State[3] = OPERATIONAL
06/20/2017 11:00:45.45 <Info:telnetd.info> **** telnetd started *****
06/20/2017 11:00:45.34 <Noti:SNMP.Subagent.MstrRestrt> snmpMaster process has been restarted.
06/20/2017 11:00:45.01 <Info:SNMP.Master.InitDone> snmpMaster initialization complete
06/20/2017 11:00:44.48 <Info:HAL.Sys.Info> Internal PSU-2 is disconnected.
06/20/2017 11:00:44.48 <Info:HAL.Sys.Info> Internal PSU-1 is disconnected.
06/20/2017 11:00:43.98 <Info:tftpd.info> **** tftpd started *****
06/20/2017 11:00:43.78 <Info:DOSProt.Init> DOS protect application started successfully
06/20/2017 11:00:43.49 <Info:SNMP.Subagent.InitDone> snmpSubagent initialization complete
06/20/2017 11:00:43.29 <Info:nl.init> Network Login framework has been initialized
06/20/2017 11:00:42.24 <Noti:DM.Notice> Node State[2] = STANDBY
06/20/2017 11:00:42.24 <Info:DM.Info> Node INIT DONE ....
06/20/2017 11:00:41.58 <Noti:DM.Notice> Node State[1] = INIT
06/20/2017 11:00:41.46 <Info:HAL.Sys.Info> Hal initialization done.
06/20/2017 11:00:40.37 <Info:HAL.Sys.Info> Internal PSU-2 is powered off.
06/20/2017 11:00:40.37 <Info:HAL.Sys.Info> Internal PSU-2 is present.
06/20/2017 11:00:40.37 <Info:HAL.Sys.Info> Internal PSU-1 is powered off.
06/20/2017 11:00:40.37 <Info:HAL.Sys.Info> Internal PSU-1 is present.
06/20/2017 11:00:40.04 <Noti:HAL.Sys.Notice> Module in fan slot 3 is inserted
06/20/2017 11:00:39.86 <Info:telnetd.info> telnetd listening on port 23
06/20/2017 11:00:39.70 <Noti:HAL.Sys.Notice> Module in fan slot 2 is inserted
06/20/2017 11:00:39.12 <Noti:HAL.Sys.Notice> Module in fan slot 1 is inserted
06/20/2017 11:00:38.17 <Info:HAL.Sys.Info> Starting hal initialization ....
06/20/2017 11:00:37.56 <Noti:NM.StrtProc> The Node Manager (NM) has started processing.
06/20/2017 11:00:37.48 <Noti:DM.Notice> DM started
06/20/2017 11:00:37.12 <Noti:EPM.start> EPM Started
06/20/2017 11:00:36.92 <Noti:EPM.wd_warm_reset> Changing to watchdog warm reset mode
06/20/2017 10:57:56.89 <Warn:EPM.all_shutdown> Shutting down all processes
06/20/2017 10:57:56.78 <Warn:EPM.reboot> Rebooting with reason User requested switch reboot.

> The above logs may cause ports to fail. 
Environment
  • Summit X670V-48x
  • EXOS 
Cause
These error messages appear when SPI-ROM(where port's firmware is loaded) is corrupted. 

 
Resolution
The most immediate workaround is to repair the SPI-ROM by running the below command in pacman debug-mode. 

'debug hal configure ports 1-48 update-rom'




 
Additional notes
If the errors reappear post re-writing the SPI-ROM then the only option is to RMA the switch. 

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255