As you know, I have several SuperMicro servers in the lab now. So quiet I have to look to see if they are on. I have some outstanding updates to do. Not quite sure how at first but I have found out how to do simple and easy firmware updates that include IPMI and BIOS. Got the idea from here, but below is how I do it.
I suggest you do the BIOS update of a host first, followed by the IPMI firmware update, and if necessary the redo of the BIOS settings. Then once both BIOS and IPMI updates are done move to the next host.
Get the bits here (pick Windows or Linux), and also, when they show up, ask for an eval license. The tool is called Supermicro Update Manager or SUM. You need to enable this method of updates. You can purchase the license too – 19US$ for each managed machine via WiredZone.
You can actually watch this link which is the home page for my model – X10SDV-TLN4F – and use the BIOS link to get the latest BIOS. But otherwise getting BIOS is actually a little hard from Supermicro. You need to watch this site, but also understand your SYS-5028D-TN4T is not really what SM uses for support but rather the X10SDV-TLN4F, and you search in the site mentioned above using X10SDV. Also watch for your processor type – which can be found in the vSphere Web Client where mine is D-1541. So use the first link. I have downloaded X10SDVF8_613.zip
X10SDVF8_213.zip X10SDVF7_919.zip X10SDVF6_A03.zip. I wish SUM downloaded stuff for us!
Making it work – License
I have the Windows bits extracted on my Windows desktop, and I have a license handy. Lets make it all work.
- First, we need to license. So access the iKVM, and note the firmware / BIOS information. We will need to compare against that when the update is done.
- We change to Miscellaneous and select Activate License.
- Now we need to add our license in. Be aware that the BMC MAC address matches the license.
- The first time I had nothing happen. Turns out the timeout for login expired. So I tried again.
- Second try worked. Notice above how you can see in bold Activated?
So we are ready for the fun stuff now!
What can we see?
Now we need to change to the folder where we extracted the Windows SUM files to. As a test before we do an upgrade, lets make sure we can see something.
Use the command:
sum -i ikvm_IP -u ADMIN -p password -c CheckAssetInfo
And hopefully you see something like:
And, then there is a lot of info. Much of what I don’t want to share. But, it is things like MAC addresses, memory information, serial number and baseboard info. But most important it does confirm that we can work with this host and that SUM is happy.
Another cool example of what you can do is make a text file copy of the BIOS info.
sum -i 10.10.10.9 -u ADMIN -p Password -c GetDefaultBiosCfgTextFile –file Bios.txt
And you will have a text file of your BIOS config. You can make a change and upload it too but I have not tried that.
BTW, you can replace CheckAssetInfo with CheckSensorData or CheckSystemUtilization options for quite different info.
So you have recorded the current firmware / BIOS info right? And you have downloaded the updates – right? I have extracted firmware update file in the same folder as SUM. Then I used this command to compare what was in the system board and what was in the file.
sum -i 192.168.9.14 -u ADMIN -p password -c GetBiosInfo –file X10SDVF6.A03
Make sure to use the BIOS file name you just downloaded. Note the double dash on file too. And below is what I get.
So it is sort of in code, but I see that the build date between motherboard and BIOS build is 2016/7/13 and 2016/10/3 so the BIOS file is newer. So now to apply it.
But, important note, is that we want to boot during the update. I will also have maintenance mode engaged too – since I am updating BIOS in a vSphere host.
sum -i 192.168.9.14 -u ADMIN -p password -c UpdateBios –file X10SDVF6.A03 –reboot
And we see the following.
After about 10 or 15 minutes I got this nice looking error.
But with the two most recent BIOS I got instead this screen.
The boot process seem to take a bit longer then normal. Not sure if this BIOS update will impact any boot settings or not.
But my server came up, and it did show the updated BIOS info. Most recently it was 1.2c and now 1.3. I checked via the UI.
So SUM can work to do a BIOS update. I think if you have only a few servers that logging into the iKVM might be easier but with any number of server this is better. Plus, it can change BIOS config pretty easy too (and more actually). So free tool – SUM, and free (1) license – or 19 per host per host is not too bad. So my hosts are now all the same BIOS level which is good.
Questions or comments always welcome!
- 9/23/18 – used this article to upgrade to 2.0 and it worked fine. I am still using 1.6.1 of SUM and one host at a time.
- 4/22/18 – I used this article to upgrade to 1.3 and it worked fine. I did do one server at a time, but I will see if I can do two at a time next time. I also used the same version of SUM as I did previously.
- 10/23/17 – Used this with 1.2c and did some slight improvements, including making screenshots easier to read. Suggest using –reboot to make things a little smoother. Some of the command line parameters use dash, and some – like file and reboot – use double-dash. Confirmed no password loss occurs.
=== END ===