ProLiant Servers (ML,DL,SL)
Showing results for 
Search instead for 
Did you mean: 

How to update firmware on redundant ROM

Tom Wolf_3
Valued Contributor

How to update firmware on redundant ROM


We just updated the ROM firmware on our Proliant BL469c G1 from version 2010.10.25 to 2011.05.02 via the HPSUM GUI that came with SPP 2012.08.0.

From the SMH we see that the redundant ROM is still running the old firmware version 2010.10.25

I don't see information in the HPSUM user guide about how to update firmware on the redundant ROM.

Could someone please explain how we would do this via the HPSUM GUI.


Thanks in advance.


Tom Wolf



Honored Contributor

Re: How to update firmware on redundant ROM



That's a good question. You can try to switch to redundant rom in RBSU and after that to perform the update. But why do you want to do this. The reason behind the redundant rom is to save the current rom as backup.





How to Say Thank You? Just click the KUDOS!
Honored Contributor

Re: How to update firmware on redundant ROM

The redundant firmware is not "running" in any sense of the word: it is just held in reserve, in case the active firmware turns out to be unusable for any reason. (I think you can use the DIP switches on the system board to switch to the redundant ROM if the primary ROM does not even get you as far as the BIOS settings.)


The normal update procedure will not touch the current active firmware: instead, it rewrites the redundant firmware and after the writing is completed, it switches the redundant firmware to the active state and vice versa.

It follows that if you wanted to update both ROMs, you would only need to update one firmware, reboot, and then run the same firmware updater *again* . There is no need to manually switch to the other ROM at any point - the upgrade procedure already does it for you.



(I did this once, years ago, after the new firmware version had been running for months, to satisfy myself that the old version with a particularly irritating bug was *gone* from the system, and to verify that I could bring both firmware sets to the same version if necessary. It worked.)


But please consider this: the fact that you could install the new firmware using the normal procedure is proof that the old firmware was/is at least good enough to allow you to successfully update to the new firmware - and that is all you really need.


If the new firmware turns out to be unbootable, you can switch to the redundant firmware and the server will still be functional. But if you update both firmware sets and the new version turns out to have a fatal bug, you'll have turned the server into a very expensive brick.