Proliant Gen10 v2 Plus ILO and Bios Cmdlets can't connect

[Leipold]

I wanted to use the HPEILOCMDLETS and HPEBIOSCMDLETS to get some server information.

Installed versions are HPEBIOSCmdlets 5.0.0.0 and HPEILOCmdlets 5.1.0.0

The connection works with all our gen10 server (gen10 or gen10 plus) except the gen10 v2 plus servers.

After the "[Redfish]: EISA Flow (Redfish) to determine target details" step

I'll get this error: "Server Information could not be determined for EISA ID: $0E110884"

BIOS versions are 3.62 and 3.72, ILO versions are 3.11 and 3.15. Redfish API is working (returns data in Browser with uri /redfish/v1)

Are there any issues known with that proliant series and the ilo/bios cmdlets?

[Mamatha_J]

Hi @Leipold 
Please try the below metioned steps. 
1. Enable verbose logging in iLO / BIOS cmdlets while attempting connection.

2. Test connecting with explicit parameters (if available) to override detection.

3. Use direct Redfish / REST calls to fetch server metadata for the “v2 Plus” model (e.g. GET /redfish/v1/Systems/1).

4. Update firmware for iLO and BIOS (if applicable).

5. Report to HPE (with logs, model, EISA ID) to request support / patch.
Please take a look at the documents,  you might find them useful. Thank you! https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-9cb80bdda3824b3d&tab=releaseNotes

https://support.hpe.com/connect/s/product?kmpmoid=1014673551&language=en_US&tab=manuals

Thanks & Regards,

Mamatha Ajaraddi

[Leipold]

1. I already enabled verbose output while using the cmdlets but the error I posted was the only one that was shown
2. don't know what you mean, didn't find such an override parameter

3. tested a quick script to connect and query the api without the cmdlets - that works without a problem

$credential = Get-Credential
$uri = "https://$($iloAddress)/redfish/v1/SessionService/Sessions"
$JsonBody = @{'UserName' = $credential.UserName; 'Password' = $credential.GetNetworkCredential().Password } | ConvertTo-Json -Compress
$result = Invoke-WebRequest -Uri $uri -Body $JsonBody -Method Post -UseBasicParsing -Headers @{"Accept" = "application/json" } -ContentType 'application/json'
$uri = "https://$($iloAddress)/redfish/v1/Systems/1"
$result2 = Invoke-WebRequest -Uri $uri -Credential $credential -Method Get -UseBasicParsing -Headers @{"Accept" = "application/json"; "X-Auth-Token" = $($result.Headers.'X-Auth-Token') }
$result2.Content | convertfrom-json | Select '@odata.type','@odata.etag',Model,SKU,BIOSVersion | fl * 

Result:
@odata.type : #ComputerSystem.v1_17_0.ComputerSystem
@odata.etag : W/"8B509615"
Model : ProLiant DL325 Gen10 Plus v2
SKU : P38471-B21
BiosVersion : A43 v3.72 (05/16/2025)
4. I'll report back when we have deployed the new spp. At the moment it is too early for us to deploy it on our production servers.

5. We'll see if the new versions will help. At the moment I use the api without the ps modules / cmdlets

[BPSingh]

Greetings!

New iLO Cmdlets 5.20 should fix this issue.