Updating CPLD via Powershell

[fgiestl]

Hi @ALL,

I'm currently trying to update the CPLD on a list of Synergy-Servers via powershell, using both the oneview- and the ilo-cmdlets.

My query is the following: Update-HPEiLOFirmware -Connection <connection> -Location <location> -confirm:$false

Connection to the iLO is possible, but the update-query always fails at the same point. I've tried to get behind it using Enable-HPEiLOLog to get a better view of the error, but unfortunately I get nothing that I really understand.

The error in powershell: 

Update-HPEiLOFirmware : [10.117.128.155]: Object reference not set to an instance of an object.
At line:1 char:1
+ Update-HPEiLOFirmware -Connection $testconnection -Location $testpath ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (:) [Update-HPEiLOFirmware], Exception
+ FullyQualifiedErrorId : HPE.iLO.Cmdlet.UpdateHPEiLOFirmware

The iLOLog seems fine until that point:

2022-02-18 09:32:27,430 INFO - [Update-HPEiLOFirmware][10.117.128.155][Redfish][ValidateRecord]: Checking for TPM Status.
2022-02-18 09:32:27,437 INFO - [Update-HPEiLOFirmware][10.117.128.155][Redfish][GetODataIdFromResourceDirectory]: Begin
2022-02-18 09:32:27,442 INFO - [Update-HPEiLOFirmware][10.117.128.155][Redfish][GetODataIdFromResourceDirectory]: Getting url value from resource instance.
2022-02-18 09:32:27,448 INFO - [Update-HPEiLOFirmware][10.117.128.155][Redfish][GetODataIdFromResourceDirectory]: End
2022-02-18 09:32:27,769 ERROR - [Update-HPEiLOFirmware][10.117.128.155][Redfish]:

ExceptionMessage:Object reference not set to an instance of an object..
InnerException:.
StackTrace: at HPE.iLO.Communication.Redfish.RedfishCommunication.CheckTPMStatus(iLORedfishConnection redfishConnection, CmdletRecord cmdletRecord, String ODataType, String query, Boolean TPMFlag)
at HPE.iLO.Communication.Redfish.Model.UpdateModel.ValidateRecord(CmdletRecord cmdletRecord)

Seems like there is some problem in the validating process, but I can't really figure out why. 

If there is anything wrong with my post, sorry, first time posting here. Thanks in advance!

Best regards

Florian Giestl

[support_s]

Hello,

Hope this helps.

https://support.hpe.com/hpesc/public/docDisplay?docId=sf000046896en_us&docLocale=en_US

https://support.hpe.com/hpesc/public/docDisplay?docId=c03334058 [page 60]

Thanks.

[fgiestl]

Hi,

thanks for the reply.

Unfortunately that doesn't really help. Both documents you sent are regarding iLO4, but im talking about Synergy, so iLO5. But I don't really know if that makes a difference scripting wise.

The bigger problem is, while I'm using powershell to try to automate the updates, I can't find anything about powershell in those documents.

Best regards

Florian Giestl

[PatrickLong]

There were also Gen9 w/ iLo4 availble in the Synergy compute module lineup, but I agree that the automated responses from the support_s SYSTEM RECOMMENDED bot are not usually helpful   Also, I'm not sure that automating this CPLD firmware over large swaths of your server environment is going to be a good idea, because it requires a reboot immediately after updating AND it will force an auxiliary power reset on the compute module which removes it from OneView and re-adds.  Do too many of those at once and you could overwhelm your Composer (I have dated Composer1's, so more of a concern...).  That being said, what is the current firmware version of your iLo5?  The latest supported on Synergy is 2.60a; there is a newer 2.63 available, BUT per the Release Notes "Is not supported for HPE Edgeline, Synergy Gen10 and Gen10 Plus systems.") 

Also, what version of HPEiLOCmdlets do you have installed?   Get-Command Update-HPEiLOFirmware

[DanCernese]

Engineering testing prior to the release of the CPLD update demonstrated there are issues with this (typically "factory-only" piece of firmware) in HPE OneView, SUM, SUT, and iLO.  There was no viable process using OneView .  That's why the published advisories do not mention using it to deploy on a large scale.  Those issues will all be addressed quickly, but it will be a couple month(s) before we hit the next release cycle.

The iLO powershell might work.. ..but there was both explanable and unexplainable behavior in iLO so that method was also not documented in favor of the iLOrest tool, which always worked.