HP Integrity Superdome 2 Server - Manual (Page 176)

28 Updating Firmware
Introduction
Superdome 2 firmware update uses a smart analysis algorithm to assist and prevent disabling a
Superdome 2 through bad firmware update application.
Because there are still limitations in changing out firmware underneath a running partition (online
OS instance), it is important to understand these limitations to minimize downtime in any given
firmware update scenario.
Superdome 2 firmware can, at the topmost level, be applied in two different manners; partition or
complex. A variety of modifications can be made to both these applications to alter the firmware
update in offline and online situations.
Firmware update bundles
All Superdome 2 platform firmware is contained in a single bundle.
Firmware update commands for Superdome 2 generally process bundle updates targeted at the
complex or a partition, but will also support updating IOXs and Server blades in situations where
these components need to be updated so they can be added to a partition.
Smart analysis
Firmware update in Superdome 2 will not overwrite images that are already at the same revision
as in the bundle being applied unless the REINSTALL flag is used.
Mandates
Superdome 2 firmware updates operate under two mandates which are implemented in an ‘analysis’
phase at the time of update. By understanding these mandates, downtime can be minimized for
firmware update actions. The mandates are:
•
Never damage a running partition – any update action that could harm a partition either
currently running (online) or prevent partition reboot will abort the update.
•
Never install firmware that is not intended for the hardware [board/FRU] – any update action
that will incapacitate a board/FRU.
Offline partition update
Single partition update
To target a firmware update to a single offline partition, use one of the following commands.
Updating to a higher bundle revision
oa> UPDATE NPARTITION <nPar name or number> <uri>
Updating to a lower bundle revision
oa> UPDATE NPARTITION <nPar name or number> <uri> FORCE
Checking the Status of Bundle, no update occurs
oa> UPDATE NPARTITION <nPar name or number> <uri> NOEXECUTE
Overwriting a bundle of the same revision
oa> UPDATE NPARTITION <nPar name or number> <uri> REINSTALL
176 Updating Firmware