Using HP SUM to upgrade firmware

If you have lots of physical servers, I totally understand if you don’t want to talk about “upgrading” them. But you need to upgrade, at least the device firmware’s should be decent so you don’t see weird errors on higher levels.

Well ok, you probably will see some weird things anyway but if you upgrade, the vendor won’t be poking you with “please upgrade to latest firmware” for every problem.

This post is about HP servers. There is a tool for firmware management by HP, SUM (Smart Update Manager). You can find the download from google (otherwise it’s not possible, because HP has the flagship of ‘Hardware vendors must have a terrible website’ rule).
You can install provided RPM or run it from a Windows box. You should consider a server which has some way to access all others (preferably ssh). After you run hpsum with no parameters, it’ll prompt the port it’s running (63002), you can access it via browser. Login with the credentials from installed server, don’t search for a default password.

First you should add a “baseline” from baseline library section. Just extract the latest SPP medium HP provided on somewhere and point it as baseline. SUM will scan and detect applicable packages inside. Then you can add nodes you want to check/upgrade. SUM can connect directly to OS, which is my preferred method. You can of course connect it to ILO, in this case it’ll only check/upgrade the ILO version. After connection, you should run “inventory” to see current situation on the server. An inventory report will come and you will be selecting components you’d want to be upgraded. Be sure to check reboot options section. You can reboot right after upgrade (if needed) or wait for a more appropriate time and do it manually.

A side note: Run the inventory again after you’ve upgrade/reboot. Sometimes there might be some “middle steps” between firmware versions. If you like to be quick or want to perform some bulk actions (like adding/deleting nodes/baselines), just use parameters for hpsum. It’ll make your life easier:

Edit: Of course you can see this software crash after a period of frequent usage (maybe also a HP standard). If you see nonsense behaviour, just clear everything with “clean-cache.{sh,bat}” from installation directory.


378 Words

2016-02-24 07:02 +0100