Reset Search
 

 

Article

Adding module to VSB Bonded system fails to initialize with heartbeat errors

« Go Back

Information

 
TitleAdding module to VSB Bonded system fails to initialize with heartbeat errors
Symptoms
  • Adding module to VSB Bonded system with different firmware version then existing chassis fails to initialize
  • CPU Led lights flass blue and green
  • hearbeat not responding errors seen from existing chassis modules logging buffer:
<163>Nov 5 10:24:41 172.16.2.2 FtmLi[3.tHBChk]heartBeatCheck: slot 5 has not responded for 10 periods
  • From local console on the board that will not boot, the following is seen:
<163>Nov 6 21:41:51 0.0.0.0 FileMgr[5.tNvFinIn]downloadImage: removing bad image file /flash0/images/S-77102-0005.....
<163>Nov 6 21:41:51 0.0.0.0 FileMgr[5.tNvFinIn]Couldn't download version 07.71.02.0005 from slot 2
<165>Nov 6 21:41:57 0.0.0.0 System[5]Shutting down non-volatile storage.
Environment
  • S-Series VSB Bonded Chassis
  • SK1008-0816
  • Firmware 07.71.02.0005
Cause
Known firmware issue that only occurs when the images involved are 07.71.xx or a greater than or equal version 07.72.xx
Resolution
Upgrade Chassis to 07.73.01.0003 or later
Additional notes
Release note entry explaining fix in 07.73.01.0003:
Adding a module to a Bonded system that boots with a version of firmware different 
than the active image may fail to initialize and reboot continuously on an image 
download failure. This failure will only occur when the images involved are 7.71, 
and a version greater than or equal to 7.72.
At the time of failure a message with format: "FileMgr[10.tNvFinIn]downloadImage: 
removing bad image file /flash0/images/S-77102-0005....." will be logged.

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255