Firmwareupdate Error HPE DL380 Gen10 Eth 10Gb 2p 535FLR-T

[TQ12]

Hello
I get an update error if I try to update the firmware of an HPE Eth 10Gb 2p 535FLR-T in an DL380 Gen10.
It does not matter if I use the current SPP or if I try to update via iLO web.

Error message is: No matching target was for this update/upload

For the manual update I downloaded the same update file the SPP was trying to install from the HPE support website:
bcm226.1.107000.Optimized.pup.fwpkg

I also tried older versions then 226.1.107000. Resulted in the same error.
Installed firmware on the card is: 218.0.166000

Any ideas?
Thanks

[support_s]

System recommended content:

1. HPE ProLaint DL380 Gen10 Server Trusted Maintenance and Service Guide

2. HPE ProLiant DL380 Gen10-Datastores inaccessible after performing SPP SPP2021040.2021_0409.17 update via iLO Amplifier

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[shiva_jr]

Hi TQ12,
Installed model is supported by the Server ? 535FLR-T is not supported to DL380 Gen10 Server.
Following are the supporting Ethernet adapters for HPE ProLiant DL380 Gen10 Server. Refer quickspecs Page no. 60.
If the Model is supported by server.  Please provide the product number of Server and Ethernet adapter. We can dive in to the issue.

HPE Ethernet 1Gb 4-port FLR-T I350-T4V2 Adapter 665240-B21
HPE Ethernet 1Gb 4-port FLR-T BCM5719 Adapter 629135-B22
HPE FlexFabric 10Gb 2-port FLR-T 57810S Adapter 700759-B21
HPE FlexFabric 10Gb 2-port FLR-SFP+ 57810S Adapter 700751-B21
HPE Ethernet 10Gb 2-port FLR-T BCM57416 Adapter 817721-B21
HPE FlexFabric 10Gb 4-port FLR-T 57840S Adapter 764302-B21
HPE Ethernet 10Gb 2-port FLR-SFP+ BCM57414 Adapter P08440-B21
HPE Ethernet 10/25Gb 2-port FLR-SFP28 BCM57414 Adapter 817709-B21
HPE Ethernet 10/25Gb 2-port FLR-SFP28 MCX4121A-ACFT Adapter 817749-B21
HPE Ethernet 10Gb 2-port FLR-SFP+ X710-DA2 Adapter 727054-B21
HPE Ethernet 10Gb 2-port FLR-T X550-AT2 Adapter 817745-B21
HPE Ethernet 10/25Gb 2-port FLR-SFP28 QL41401-A2G Converged Network Adapter 867334-B21

Regards,
shiva_jr
Please mark as 'Accepted solution' if my post worked and award the 'Kudos'.

[thutchings]

Hello,

Can you provide some details on the currently installed firmware version on the NIC? The PLDM (FWPKG files) based updates will not work if the NIC is not already at the minimum required version:

Be noted that it needs the minimum version(NVM Image version 216.0.333011) for this firmware package, please refer to the following link to update firmware first.

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_c9c99d62694e4a6aa418b0a781

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_2502ce87e3ba481081daea7a6c

https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_0d5f5f72693848838710781e5e

Regards

[TQ12]

The card is of course supported in the server.
It came directly from HPE with the card installed.
You can find it listed in the options parts list.

[TQ12]

Thanks.
We checked that of course already.
We are in the 218 version.

I have opened a support call because I think something with the card is wrong.
Other 1:1 identical servers accept the firmware without any problem.

[Duke3d]

We experience the same issue, a support case is already open but so far no solution available. We have quite few of the DL380 GEN10 server with Windows Server 2016 and with the Eth 10Gb 2p 535FLR-T adapter installed. Some of the server will install the 226.1.107000 firmware (and newer) without any issue, and some of them don't. Any suggestions? Is a solution available now?

If it fails, we receive the error: The last attempt to update or upload firmware was not successful. Make sure you are using a valid, signed flash file and try again -and- The update failed with a component specific error. Retry the update after fixing the component error.

current adapter firmware: bcm 224.1.102000
new adapter firmware: bcm 226.1.107000 or newer

- update via iLO
- update via iLOrest and command line
- update with SSP 2023.09 (bcm 226.1.107000)
- update with SSP 2024.04 (bcm 228.1.111000)
- standalone package (executable) seems not available for windows server 2016 for newer firmware version (214.xxx)

all of them fail with more or less the same error, signature and/or component specific error.
*the 228.1.111000 fails with minimum requirements to be at least on 226.1.107000 firmware

[TQ12]

Hi there @Duke3d 
If I remember correctly, the instruction from HPE solved the problem for us:

1. Download https://support.hpe.com/connect/s/softwaredetails?language=en_US&softwareId=MTX_335a18b538b143d2a880688ca0
versions 223.1.96 and 227.1.111
2. Power drain the server for 10-15 minutes
3. Clear NVRAM (unplug the server from the electricity, open it and remove the BIOS battery for 20 minutes, then attach it back)
4. Install the package 223.1.96 via iLO
5. Reboot the server
6. If it was successful, install 227.1.111 and up

Let me know if that fixed your problem too!

Cheers

[Duke3d]

Thanks a lot! This procedure seems working for us as well. But so far we don't need to remove the BIOS battery. Just remove the power-plug for ~5 Minutes will do the job and the firmware on the network card can be upgraded afterwards! However our servers are spread across europe in several remote locations and we do not have on-site support and skilled personal on each site, would be nice to have another workaround at least for those areas.

Side Note: I noticed another topic by visiting one of the affected location, both server with this type of network card on each LOM port damaged themself somehow. The cooler plate on each network card is secured with small plastic pin and a metal spring, some of plastic pins are broken (in our case only one pin -out of four- is healthy on each server) and the metal spring caused short-circuit on the board (and the LOM port is without power now). Maybe it is just bad luck but I will check that topic on other locations.

[TQ12]

@Duke3d 
Good to hear!
As far as I can remember, we only removed the BIOS battery once and then realised that it also works without this step.

---

@Duke3d  wrote:

However our servers are spread across europe in several remote locations and we do not have on-site support and skilled personal on each site, would be nice to have another workaround at least for those areas.

---

This is a point at which remote manageable PDUs with switchable power connections become useful.
Cheers

[thutchings]

Hello,

If it has been confirmed that removing power from the server and reapplying does fix it, then issuing the following POST call using a redfish/REST client should have the same impact:

POST https://<iLO IP address>/redfish/v1/Systems/1/Actions/Oem/Hpe/HpeComputerSystemExt.SystemReset/

With the following body:

{
"ResetType": "AuxCycle"
}

When you perform the above it will "stage" an AUX reset. The next time the server is rebooted it will drop power for ~6 seconds instead of performing a normal reboot.

Regards

[TQ12]

True @thutchings 
I had seen a poweshell script for this at some point.
Here it is:
https://www.mydailyitlessons.net/2022/10/trigger-auxiliary-power-cycle-for-hpe-ilo/

Cheers

[Duke3d]

This seems helped a lot! We have resolved all component specific errors with the powershell script, unfortunately we had to slightly modify the script, for example the function within the script in the end was not closed (function Reset-HPEServer).

However, it works now! All network cards within the servers have been successfully updated to 228. version! Thanks a lot!

[TQ12]

@Duke3d 
Glad to hear that everything worked out and that you were able to revive your cards!
Maybe you can attach the customized Powershell script here? It might be useful for others who have the same problem.

Cheers

[Duke3d]

Powershell Script see below

The script basically asking you to enter:

- IP Address of the iLO
- Username & Password

function Reset-HPEServer
{

    [CmdletBinding()]
    Param
    (
        # iLO URL or IP
        [Parameter(Mandatory=$true,ValueFromPipelineByPropertyName=$true,Position=0)]
        [string]$ilo,
        
        # User credentials
        [parameter(Mandatory=$true)]
        [string]$username,

        [parameter(Mandatory=$true)]
        [string]$password
    )
   
    Begin
    {
        Write-Host "Starting Reset-HPEServer script..."
        # Approve self signed SSL certificate
        add-type @"
using System.Net;
using System.Security.Cryptography.X509Certificates;
public class TrustAllCertsPolicy : ICertificatePolicy {
    public bool CheckValidationResult(
    ServicePoint srvPoint, X509Certificate certificate,
    WebRequest request, int certificateProblem) {
    return true;
    }
}
"@
        [System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy
        Write-Host "Self-signed SSL certificates are now trusted."

        # iLO common API url
        $uri = "https://$ilo/redfish/v1"
    }
    Process
    {
        Write-Host "Attempting to log in to iLO at $ilo..."
        # Login and create webSession and authHeader
        $credBody = @{UserName = $username; Password=$password} | ConvertTo-Json
        $loginUri = "$uri/Sessions/"
        $hpeSession = Invoke-WebRequest -Uri $loginUri -Method Post -Body $credBody -ContentType 'application/json' -SessionVariable webSession -ErrorAction Stop

        # Check if login was successful
        if ($hpeSession.StatusCode -ne 201) {
            Write-Error "Login failed with status code $($hpeSession.StatusCode)."
            return
        }
        Write-Host "Login successful."

        $authHeader = @{"X-Auth-Token" = $hpeSession.Headers.'X-Auth-Token'}

        $AuxPowerCycleURI = "$uri/Systems/1/Actions/Oem/Hpe/HpeComputerSystemExt.SystemReset/"
        $AuxPowerCylceBody = @{ 
            Action = 'SystemReset' 
            ResetType = 'AuxCycle'
        } | ConvertTo-Json
        
        Write-Host "Sending reset command..."
        $Return = Invoke-WebRequest -Uri $AuxPowerCycleURI -Method Post -Headers $authHeader -Body $AuxPowerCylceBody -WebSession $webSession -ContentType "application/json"

        if ($Return.StatusCode -ne 200) {
            Write-Host "Got error Message, most probably you have to shutdown the server first"
            $return.Content
        }
        else {
            Write-Host "iLO reset command issued successfully. You might receive a timeout error, which is a good sign." 
        }
    }
    End
    {
        Write-Host "Script execution completed."
    }
}
Reset-HPEServer

Save the content as *.ps1