NCM's Firmware Upgrade takes seven hours to time out when transferring IOS to a node fails. What can I do to reduce that seven hours?

If NCM Firmware Upgrade's file transfer from NCM to the network node times out (using tftp), it takes NCM seven hours to decide the job has failed.

What can I do to NCM to shorten that time-out / failure discovery and get NCM to stop the job and let me troubleshoot it?

Find more posts tagged with

firmware_upgrade

Accepted answers

All comments

jlinkowsky

rschroeder Here I thought it was just me. Mine took 10+ hours to time out before telling me "oh, I failed." Really not good. SW - please address this issue.

rschroeder

I applied hot fixes to all my SW modules and APE's six days ago. I haven't tested to see if that fixed this particular issue, but I DO note many other things that were problematic have been repaired. Fingers are crossed that this is no longer an issue after the HF's, too.

rschroeder

After all the hotfixes were applied, most all my complaints were resolved. Except this one. I've created a new Discussion for the topic here:

How does one modify NCM's Firmware Upgrade Operation so it recognizes there is enough free space to proceed?

rschroeder

And I've even built a feature request for it here: