Loading...
Loading...
On HPE systems running iLO firmware versions prior to iLO 5 v3.21, iLO 6 v1.77, and iLO 7 v1.22, the targeted firmware update on a selected device fails for Universal Backplane Management (UBM), if the server is deployed with multiple UBM direct-attached NVMe devices. In this instance, the failure can be confirmed from the exception generated in the iLO Event log with internal error.This is due to Multiple UBM components sharing the same location information due to the underlying backplane topology and configuration. As the targeted firmware update relies on location information, iLO cannot uniquely identify an individual UBM when the location is shared.Consequently, all applicable UBM components associated with the same location may be selected for the firmware update.Figure 1: Five UBM6 firmware inventory entries, all running firmware version 1.04:Four entries are associated with Box-2One entry is associated with Box-3For Box-2, the PICs belong to the same backplane cage, are controlled by the same UBM manager, and share the same DeviceContext. Therefore, selecting any one of the Box-2 entries as the target will result in the complete Box-2 backplane being flashed. Individual PICs under the same DeviceContext cannot be flashed separately.For Box-3, only one firmware inventory entry is currently displayed because the remaining cables are not connected. Therefore, only the connected PIC is being reported for Box-3.Although Redfish Firmware Inventory can display multiple entries for the PICs, firmware update is determined by the DeviceContext. PICs sharing the same DeviceContext are updated together rather than individually.
Any HPE ProLiant DL Gen10, Gen10 Plus and HPE ProLiant Gen11 servers installed with multiple UBM backplane with an update to a selected discrete UBM backplane alone on iLO firmware versions earlier than iLO 5 v3.21 and iLO 6 v1.77 and iLO 7 v1.22.
To resolve this issue, update to iLO 5 v3.21, iLO 6 v1.77, and iLO 7 v1.22 respectively.To download iLO 7 v1.22, iLO 6 v1.77 (or later) or iLO 5 v3.21 (or later), perform the following steps:Click the following link:http://www.hpe.com/support/ilo7orhttp://www.hpe.com/support/ilo6orhttp://www.hpe.com/support/ilo5The page should refresh to display the "DRIVERS AND SOFTWARE" tab and the components that support the selected product. From the "DRIVERS AND SOFTWARE" expandable filter menus on the left side of the page:For further filtering if needed - Select the specific Operating System from the Operating Environment.Locate and select theHPE Integrated Lights-Out 5 v3.21 firmware, HPE Integrated Lights-Out 6 v1.77 firmware,orHPE Integrated Lights-Out 7 v1.22 firmware.click the Revision History tab to locate the latest version.For more important information, review the Release Notes tab.Click theDownloadbutton.When a UBM component has a unique location, iLO can uniquely identify and target that component for firmware update. When multiple UBM components share the same location, the available location information cannot uniquely identify an individual UBM component. Therefore, an individual UBM component cannot be independently targeted in such configurations.This behavior is dependent on the underlying backplane topology and the location information exposed for the UBM components.HPE recommends before initiating a targeted firmware update for a UBM component, verify that the intended component has unique location information in the Redfish firmware inventory.If the UBM component has a unique location, it can be individually targeted for firmware update.If multiple UBM components share the same location, do not perform a targeted update with the expectation that only the selected UBM component will be updated. Other UBM components associated with the same location may also be updated.IMPORTANT: A unique target ID alone may not be sufficient to uniquely identify a physical UBM component for targeted firmware update. Component location information is also used as part of device identification. For a UBM backplane, multiple firmware inventory entries may be reported in Redfish for the same backplane. When multiple entries belong to the same UBM backplane and share the same DeviceContext, they are treated as a single firmware update target. Therefore, selecting any one of these entries during a target-based Simple Update updates the entire UBM backplane associated with that DeviceContext. Individual entries sharing the same DeviceContext cannot be updated independently.
Operating Systems Affected:OS Independent
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.