topic Re: Synergy Custom SPP 2020.07.01 not named properly when imported into Composer Firmware Bundles in HPE Synergy

Synergy Custom SPP 2020.07.01 not named properly when imported into Composer Firmware Bundles

PatrickLong — Tue, 18 Aug 2020 17:17:05 GMT

I just downloaded the HPE_SYNERGY_CUSTOM_SPP_2020.07.01_Z7550-96923.ISO and uploaded it into my Composer's firmware bundle location. *During* the file upload, the bundle does show up in Composer with the Name, "HPE_Synergy_Custom_SPP_2020.07.01_Z7550-96923.iso" , however after the upload is complete and the file contents are enumerated, The Name, Version, and Description fields do not show up with the same format as previous Synergy Custom firmware bundles. In fact, the Name shows "Service Pack for ProLiant" which is somewhat misleading. The Version format has changed to "SY-2020.07.1" which by the SY prefix I suppose is an indicator that this version is Synergy-specific? and the Description field appears to have come from the standard SPP for ProLiant Gen9/10 servers. Can someone from HPE confirm that the changes to the bundle Name/Version/Description are by design? Or is this something that slipped by QA with this release? View the differences below during upload and after enumeration of contents:

Re: Synergy Custom SPP 2020.07.01 not named properly when imported into Composer Firmware Bundles

DanCernese — Tue, 18 Aug 2020 17:50:16 GMT

This is intentional. The upcoming Customer Notice of publication includes this

NOTE: After it is loaded into HPE OneView, the new firmware bundle will no longer identify itself as an HPE Synergy Custom SPP. The bundle will be identified as a "Service Pack for ProLiant."

Re: Synergy Custom SPP 2020.07.01 not named properly when imported into Composer Firmware Bundles

PatrickLong — Tue, 18 Aug 2020 17:52:38 GMT

Excellent - thank you Dan!

Re: Synergy Custom SPP 2020.07.01 not named properly when imported into Composer Firmware Bundles

rmay_bk — Tue, 18 Aug 2020 19:15:16 GMT

@DanCernese wrote:
The bundle will be identified as a "Service Pack for ProLiant."

Odd, that. I thought HPE had moved to a unified SPP after reading that title. I tried booting a Proliant with that SPP and it yelled at me. So "Service Pack for Proliant" means "Service Pack not for ProLiant."

Re: Synergy Custom SPP 2020.07.01 not named properly when imported into Composer Firmware Bundles

PatrickLong — Wed, 26 Aug 2020 19:12:05 GMT

rmay_bk I agree, it seems an odd development in what has been to date a seemingly significant marketing investment in separating the Synergy branding from any connection whatsoever to the ProLiant name. Who knows, maybe we'll be calling our Synergy compute modules 'blades' again before too long Kidding, of course.

Re: Synergy Custom SPP 2020.07.01 not named properly when imported into Composer Firmware Bundles

DanCernese — Fri, 02 Oct 2020 17:25:42 GMT

2020.07.02 calls itself "Service Pack for Synergy"