OPERATIONAL DEFECT DATABASE
...
...
In an HPE ProLiant Gen10 or Gen10 Plus environment, an attempt to update the firmware for any of the HPE Fibre Channel Host Bus Adapters (HBAs) listed in the Scope section below, using HPE Service Pack for ProLiant (SPP) version 2023.03.00.00, may not complete successfully. A similar failure may occur when attempting to update the firmware using the Linux Operating System (OS) based online smart component. The failure occurs because two different processes that affect the HBA are occurring at the same time; the update process is actively writing the updated image to the HBA NVRAM, and the server is performing a restart to the HBA. Depending on the progress of the image update process, the HBA may be left in a state where it cannot be represented correctly in the Unified Extensible Firmware Interface (UEFI) as well as the OS, or it may be unable to link into the fibre channel network. In the instance of a failed update, the host OS will record the following errors in the system logs: ESXi7.0 /var/run/log/vmkernel.log mb[0]=4006 mb[1]=2 mb[2]=9bb6 cmd=48 ****2023-05-02T17:34:48.934Z cpu22:525339)qlnativefc: (de:0.1): scsi(2): qlnativefcInitFirmware: failed=102 mb0=0x4006, mbx1=0x2, mbx2=0x9bb6 mbx3=0xe000. WARNING: qlnativefc: (13:0.0): scsi(6): scsi(6): Failed to initialize adapter - Adapter flags 2. RHEL / SUSE similar errors in /var/log/messages: Jul 3 12:02:33 f2watpa1 kernel: qla2xxx [0000:0f:00.0]-00d2:1: Init Firmware **** FAILED ****. Jul 3 12:02:33 f2watpa1 kernel: qla2xxx [0000:0f:00.0]-00d6:1: Failed to initialize adapter - Adapter flags 2. Alternatively, to help identify that the HBA is in a failed state after a failed firmware update and cannot connect to the Storage Area Network (SAN), enter the UEFI BIOS system configuration (using F9) for the Advanced settings of the affected HBAs. NOTE : The parameter values for Login Retry Count, Port Down Retry Count, and Link Down Timeout may occasionally reset to "0" (zero). This behavior is not consistent and may not occur in all instances. However, if this does occur, manually re-enter the original values to restore the intended configuration. NOTE : The expected values are 8, 30, and 30, respectively.
This advisory applies to any HPE platform running HPE Service Pack for ProLiant (SPP) version 2023.03.00.00 and configured with any of the following HPE Fibre Channel Host Bus Adapters: HPE SN1100Q 16Gb Dual Port Fibre Channel Host Bus Adapter ( P9D94A) HPE SN1100Q 16Gb Single Port Fibre Channel Host Bus Adapter (P9D93A) HPE StoreFabric SN1100Q 16Gb Dual Port Fibre Channel Host Bus Adapter/S-Buy (P9D96A) HPE StoreFabric SN1100Q 16Gb Single Port Fibre Channel Host Bus Adapter/S-Buy (P9D95A) These FC HBA cards are supported on the following servers: HPE ProLiant DL160 Gen10 server HPE ProLiant DL160 Gen9 Server HPE ProLiant DL180 Gen10 server HPE ProLiant DL180 Gen9 Server HPE ProLiant DL20 Gen10 Plus server HPE ProLiant DL20 Gen10 server HPE ProLiant DL325 Gen10 Plus server HPE ProLiant DL325 Gen10 Plus v2 server HPE ProLiant DL325 Gen10 server HPE ProLiant DL345 Gen10 Plus server HPE ProLiant DL360 Gen10 Plus server HPE ProLiant DL360 Gen10 server HPE ProLiant DL360 Gen9 Server HPE ProLiant DL365 Gen10 Plus server HPE ProLiant DL380 Gen10 Plus server HPE ProLiant DL380 Gen10 server HPE ProLiant DL380 Gen9 Server HPE ProLiant DL385 Gen10 Plus server HPE ProLiant DL385 Gen10 Plus v2 server HPE ProLiant DL560 Gen10 server HPE ProLiant DL560 Gen9 Server HPE ProLiant DL580 Gen10 server HPE ProLiant DL580 Gen9 Server HPE ProLiant ML350 Gen10 server HPE ProLiant ML350 Gen9 Server
If the affected host bus adapter (HBA) is in a failed or degraded state, HPE recommends performing a manual flash to attempt recovery of the adapter. If the manual flash is unsuccessful, contact HPE Services to request a possible replacement of the HBA. To address the timing conflict that occurs when updating the NVRAM after a firmware upgrade, recent smart components for firmware have been enhanced. HPE Fibre Channel HBA firmware version 02.02.05 includes these enhancements. A detailed list of the permitted upgrade paths for the adapter firmware is provided in the table below: Adapter version Required step Next version Updated method Notes v1.73.xx (or earlier) 1.75.07 v2.01.03 (or later) With RBSU, FMP using .bin file from Windows SmartComponent or with Windows OS use Windows SmartComponent via iLOREST or manual ILO operation using repository. (.exe and .compsig) PLDM update method not supported v1.75.07 v2.01.03 (or later) With RBSU, FMP using .bin file from Windows SmartComponent or with Windows OS use Windows SmartComponent via iLOREST or manual ILO operation using repository. (.exe and .compsig) PLDM update method not supported, SPP and Linux Smart Component not supported v1.77.12 v2.01.03 (or later) With RBSU, FMP using .bin file from Windows SmartComponent or with Windows OS use Windows SmartComponent via iLOREST or manual ILO operation using repository. (.exe and .compsig) PLDM update method not supported and SPP and Linux Smart Component not supported v2.00.01 v2.02.05 (or later) With RBSU, FMP using .bin file from Windows SmartComponent or with Windows OS use Windows SmartComponent via iLOREST or manual ILO operation using repository. (.exe and .compsig) PLDM update method not supported and SPP and Linux Smart component not supported v2.01.03 (and later) v2.02.05 (or later) Any supported OS update method PLDM update method not supported v2.02.05 next version Any supported OS update method PLDM update method not supported It is crucial to identify the initial version of the adapter before proceeding with any updates. For example, the update from firmware v1.75.07 to v02.02.05 MUST NOT be applied using a .rpm (Linux-based smart component) on supported ProLiant servers (listed in the Scope section). If upgrading the firmware from an existing version earlier than 1.75.07, an intermediate firmware jump to 2.00.01 using the UEFI/RBSU (F9) upgrade method is required. The firmware file for this upgrade method is the bk017507.bin file which can be extracted from the Windows smart component version cp048728.exe. The required smart component is available at the following link: HPE Firmware Flash for QLogic Fibre Channel Host Bus Adapters - Microsoft Windows Server 2012R2/2016/2019(x86_64) ) Firmware Management Protocol (FMP) Installation Instructions via RBSU : Download the .exe file for the desired firmware version (Windows-based smart OS online update version). See the link below for all versions. Extract the .exe file. (The option is presented when you run the smart component.) Place the .bin file on the USB, and mount it to the server, or use the iLO GUI .NET Console to mount the folder containing the required files. At the POST screen, press F9 to enter the ROM-Based Setup Utility (RBSU) BIOS. Select Embedded Applications . Select Firmware Update . Select the SN1100Q Controller , choose the appropriate .bin firmware file, and follow the on-screen update prompts. Reboot the server. Alternately, if an automated upgrade for multiple servers is required, the iLOREST tool may be used with the Windows OS-based smart component. For example, if the OS is Red Hat Enterprise Linux (RHEL), the iLO or iLOREST can be used to flash the firmware using the Windows OS-based smart component. The iLOREST command sequence will upload both the binary and signed file and will then add a task to the queue which you will see as pending until you reboot the host. Below is an example of the iLOREST script that can be used. ilorest login 10.3.47.158 -u xxxxxx -p yyyyyyyyyy << use username and password specific to target machine timeout 6 echo "SN1100q Firmware Update using Windows binaries to iLO” ilorest uploadcomp --component c:\files\cp058498.exe--compsig c:\files\cp058498.compsig <<< Use the appropriate version names of the files here timeout 1 ilorest taskqueue create cp058498.exe ilorest taskqueue ilorest reboot In extreme circumstances, to recover an adapter which is nonfunctional after an update attempt failed, (as noted in the Description section above), the use of a .bin file extracted from the windows.exe smart component kit can be used. For example, the "bk017507.bin" file can be extracted from the Windows smart component version cp048728.exe. Below is a list of the latest versions of the OS specific smart components as of May 20, 2025. Windows Smart Component: HPE Firmware Flash for QLogic Fibre Channel Host Bus Adapters - Microsoft Windows Server 2016/2019/2022 (x86_64) Red Hat Enterprise Linux (RHEL) Smart Component: HPE Firmware Flash for QLogic Fibre Channel Host Bus Adapters - Linux (x86_64) VMware ESXi Smart Component: HPE Firmware Flash for QLogic Fibre Channel Host Bus Adapters for VMware vSphere 7.0 IMPORTANT : The Platform Level Data Model (PLDM) smart component method for the firmware update (.fwpkg) may experience inconsistencies when updating the NVRAM flash and therefore will no longer be used as a firmware upgrade method for the SN1100Q adapter. All versions of PLDM files have been removed from the HPE Support Center listings. Any previously stored copies should be deleted to avoid issues. Revision History Document Version Release Date Details 6 June 26, 2025 System log errors were added to the Description sections, along with minor edits, and additional edits to content, table and links in the Resolution section. 5 June 24, 2025 Many changes to second paragraph of the Resolution section, adapter model# in Note, first bullet after Important Note to, "Once firmware version is at 2.00.01" and added update paths table.> 4 June 6, 2025 Updated the Resolution section to align with a change in the software smart components and the method of implementation for the firmware fixes 3 January 30, 2025 Updated the first sentence of each first and second bullet items in the Resolution section for clarity 2 October 23, 2024 Updated the root cause of the description section. Updated Scope section with the Host Bus Adapters affected. Updated Resolution section with the appropriate processes for firmware updates and replacement of failed units. 1 November 3, 2023 Original Document Release
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
