Updating firmware

Firmware bundles enable you to update firmware on managed servers, server blades, and infrastructure (enclosures and interconnects). You can choose to update all the resources within a logical enclosure, just the HPE BladeSystem Onboard Administrator firmware, the firmware within a logical interconnect, or firmware for a specific server using a server profile. When you choose to update all resources within an enclosure, all servers are updated even if they are not associated with a server profile.

User roles and firmware update

The Server administrator role can upgrade the firmware on the enclosure OA and servers.
The Network administrator role can upgrade the firmware on interconnects.
The Infrastructure administrator role can upgrade the firmware on all devices.

Ways to update firmware

Firmware updates can be initiated multiple ways:

For the logical enclosure, updates can be initiated from the Logical Enclosures screen.
For individual logical interconnects, updates can be initiated from the Logical Interconnects screen.
For individual servers, updates can be initiated either by assigning a firmware baseline to a server profile and then applying that profile or by including server hardware when you perform a logical enclosure update.

Most resources (OA, iLO, server, or Virtual Connect) go offline when you upgrade its firmware. Always perform the update during a maintenance window. To help minimize downtime during firmware activation, see Maintain availability during Virtual Connect interconnect firmware upgrades.

Resource	When the device is taken offline
Enclosures	The OA is taken offline when you update firmware for an enclosure.
Servers	Firmware updates require that you edit the server profile to change the firmware baseline. Offline firmware updates require that you shutdown the server to apply the profile, where online updates using Smart Update Tools (SUT) allow you to perform parts of the update while the server is online. However, most components still require a server reboot to activate the new firmware. Servers are also updated as part of a logical enclosure update, when servers are selected as part of that process.
Interconnects	An interconnect is taken offline when you: Update or activate firmware for a logical interconnect. Staging firmware does not require interconnects be taken offline. Update firmware for a logical enclosure, and select an option to update the logical interconnect. If an interconnect has firmware that has been staged but not activated, any subsequent reboot of that interconnect activates the firmware, which takes the interconnect offline. Order of firmware update matters You can prevent the loss of network connectivity for servers connected to a logical interconnect that has a stacking mode and a stacking health of `Redundantly Connected` by updating firmware using the following method: Stage the firmware on the logical interconnect. Activate the firmware for the interconnects in even-numbered enclosure bays. Wait until the firmware update to complete and the interconnects are in the `Configured` state. Activate the firmware for the interconnects in the odd-numbered enclosure bays.

Resource

When the device is taken offline

Enclosures

The OA is taken offline when you update firmware for an enclosure.

Servers

Firmware updates require that you edit the server profile to change the firmware baseline. Offline firmware updates require that you shutdown the server to apply the profile, where online updates using Smart Update Tools (SUT) allow you to perform parts of the update while the server is online. However, most components still require a server reboot to activate the new firmware. Servers are also updated as part of a logical enclosure update, when servers are selected as part of that process.

Interconnects

An interconnect is taken offline when you:

Update or activate firmware for a logical interconnect. Staging firmware does not require interconnects be taken offline.
Update firmware for a logical enclosure, and select an option to update the logical interconnect.

If an interconnect has firmware that has been staged but not activated, any subsequent reboot of that interconnect activates the firmware, which takes the interconnect offline.

Order of firmware update matters

You can prevent the loss of network connectivity for servers connected to a logical interconnect that has a stacking mode and a stacking health of Redundantly Connected by updating firmware using the following method:

Stage the firmware on the logical interconnect.
Activate the firmware for the interconnects in even-numbered enclosure bays.
Wait until the firmware update to complete and the interconnects are in the Configured state.
Activate the firmware for the interconnects in the odd-numbered enclosure bays.

When adding an enclosure with servers where the iLO firmware is older than the minimum supported version for HPE OneView, the firmware is automatically updated using the firmware bundle that contains the latest OA or iLO firmware while the enclosure is being added. If no firmware baselines are added to the appliance, however, such an enclosure cannot be imported. In this situation, first upload a recent SPP that is compatible with the current version of HPE OneView.
Before changing the iLO encryption mode, run the command SUT-deregister on the SUT command line in the OS where the SUT is installed. Changing iLO encryption mode to high security mandates configuring iSUT (Integrated Smart Update Tools) with iLO credentials. If you change the iLO encryption mode from Production to FIPS or CNSA, ensure that iSUT 2.4.0.0 or later is installed and configured with the iLO credentials. This step is a prerequisite for applying a profile and updating the firmware in HPE OneView. All previous installations of iSUT must be configured with the iLO credentials prior to updating the firmware using HPE OneView. For more information, see the Integrated Smart Update Tools User Guide for Windows, Linux, and VMware ESXi.