#BMC update issue after headswap...

1 messages · Page 1 of 1 (latest)

candid schooner
#

I have just replaced a dead controller in a HA-Cluster, it went OK and giveback etc. worked fine.
During the first boots of the "new" controller from NetApp many firmwares was updated, just fine, yet the BMC didn't and it doesn't see to want to update...
Autoupdate is enabled and it tries, but fails... I have tried to upload the latest BMC firmware to the cluster which copies it out onto all notes which I have verified with "node image package show"... I have tried "sp image update -baseline" which should be version 11.11 (the cluster is running 9.16.1) I then tried "sp image update -package ..." of cause with reboots in between... but nothing seems to work... the current SP firmware is 11.3P2... maybe the update jump is too large?

candid schooner
#

hmm managed to fix it by installing the firmware from the BMC.. and got this wonderful message as I updated,... BMC s01-01> bmc update http://10.0.2.29/SP_FW.tar.gz -f
Downloading package...
Uncompressing package...(md5sum=431026d75fbbe3550afbf982d1e55177)
Unarchiving package...
Confirming file sizes aren't suddenly larger...
Some binaries are unexpectedly large and may be corrupt. Continue? (y/n): y
Clearing the error to allow bmc update to proceed

toxic niche
#

Sometimes a good old reboot of the sp/bmc and a retry works. However, did you happen to check the intermediate releases?

Depending on the platform and version, you may need to do a couple of hops.

Go to the downloads. Start with the sp version you have. Then work your way to each subsequent release and look at the notes for each. One noticed a couple that required certain steps

prime mural
#

I've run into issues in the past where the BMC would not update if I had an active session established to the BMC. Now, once I confirm the ontap upgrade is successful on a node, I'll close the BMC session so that it will allow the BMC firmware updates to auto run.

toxic niche
#

Reboot-sp will take care of that in a heartbeat

pseudo vessel
#

This is your issue, you either need a step-upgrade through 11.6-10 before going to 11.11 if you want the autoupgrade to work. Or, you just do what you did, update through the BMC itself and manually override the error 🙂

candid schooner
# toxic niche Sometimes a good old reboot of the sp/bmc and a retry works. However, did you ha...

Yeah that was what I tought... but it ended up working from the BMC it self.. så serial into it (because I was unable to SSH into it), then Ctrl-G to get to the BMC, then from there do the update with the "-f" for forcing the update... after that it updated currectly to 11.11.. after a few hours the cluster complained that the SP was unable to autoupdate again... but that cleared up with another sp-reboot... and haven't heard anything from the system for 10 hours now 😉