HPE Ethernet 1Gb 4-port 331i Adapter - NIC Embedded LOM for Windows 2016

[Scott Caryer]

I have a DL380 Gen 10 server running on Windows Server 2016 (GUI). My Oneview profile is showing red becuase the firmware needs to be upgraded on the NIC (HPE Ethernet 1Gb 4-port 331i Adapter - NIC Embedded LOM) from 20.19.51 to 20.28.41. However, continously running the Gen10 Service Pack for ProLiant version 2024.04.00.00 via Oneview-FW option only, or  FW with Driver option, or booting the server to that SPP ISO. The firmware will NOT get upgraded for the NIC.

I try to manually download the driver and/or firmware manually on the OS from the various selections from HPe web site, the cp0xxxxx.exe indicates that the OS is not supported, or the device is not discovered on this system. I have had issues with this this NIC before on other HPe servers.

I am at loss... Any thoughts or direction on this issue???

Much appreciated...

[ChrisLynch]

As you have been able to likely deduce, this is an issue with the NIC firmware. Have you opened a support case?

[Scott Caryer]

Hey Chris, Yes I have opened a case (5384134417) with support. Naturally, the support tech is telling me that it is not supported on the Win2k16 OS. I then tell him the FW has nothing to do with the OS. Then he tells me to upgrade the OS. The OS is dependent on the applicatio, etc. This is why I go to the OV forums before I ever open a HPe case.... Just another day in the spin cycle....

Thanks, Scott

[ChrisLynch]

We do qualify firmware with operating systems, as there is an accompanying driver to be supported as well. And if the options team doesn't list the supported OS with the firmware release, we haven't qualified it with that OS and the driver.

[Scott Caryer]

When I boot the server directly to the SPP ISO to utilize SUM process, that should be agonstic to the OS system on disk though. So then, why does it not upgrade the NIC to the baseline FW version that OV indicates?  

[ChrisLynch]

Then you need to inform the support case engineer that is the scenario you are using. Yes, that process should be agnostic as SUM has no way to know the installed OS vendor and version. But it is still up to you to know the version of firmware isn't supported with the OS and accompanying driver.

[Sebasbin]

Hi,

Kindly check if you are able to update the firmware of the NIC from the OneView by selecting installation method "firmware only" method.

But while updating the firmware, it's crucial to ensure the driver version remains compatible

According to the below driver link, for the Windows server 2019 and 2022 OS,HPE recommending updating the driver also to the version 221.0.5.0 (D) or later to use with this firmware.

https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-1d81dab4bd3149b1&softwareId=MTX_65882d97b0254de8bf3178f939

This component ONLY support HPE ProLiant Gen10 server series.
HPE recommends HPE Broadcom NX1 1Gb Driver for Windows Server x64 Editions, version 221.0.5.0 (D) or later, for use with this firmware.

[its_me_leon]

I ran into the same issue. For 1 server I was able to do the fw upgrades through the tool that is part of the online Windows component. When you extract the CPXXXXX.exe bundle you will find a bcmnicfwupg.exe file that you can run. It will upgrade the firmware.

However it only ill let you make one version step at a time. For another system I was not able to go higher than version 20.22.41. The next step to 20.23.41 fails with a similar message like this one:

I have not find a solution yet to upgrade to a higher level.

[schwengels]

Hello,

I have had similar issues where SUM or OneView would not deploy the firmware contained in the SPP, this was due to the previous version being several behind and the multi version jump didn't work. I had to manually install several older versions first in order to install the version contained in the latest SPP. Similar to what was mentioned. Hope that helps.

[pirx]

yep, had the same issue that installed fw was 5 or 6 versions older and I had to check release notes of the past versions to find out which intermediate step is needed. OneView was not able to solve this situation, I have this regularly (boot nvme, network adapter etc).