How to update to Virtual Connect Firmware 4.62

[Eugen Rodekuhr]

Hello,

We have some existing C7000s in OneView (3.10.07-0310774) which are still running on VC 4.60, we could not downgrade due to the needed downtime. 

We have tried to update to VC 4.62 but where not successful for two reasons:

1. VCSU 1.13.0 does not allow to apply the firmware with the error – Enclosure is the Primary in the VC-Domain
2. Oneview does not accept the SSP 2018-03 with the error that the HPE firmware files for OA and VC do not have a valid HPE signature.
3. Could the update to OA firmware 4.80 the trigger for the incomliance?

Any Ideas?

Look forward to hearing from you.

[ChrisLynch]

Once a C7000 Enclosure has been added to HPE OneView that contains Virtual Connect, VCSU cannot be used to perform firmware update as Virtual Connect Manager does not exist.

I was able to successfully upload the 2018.03 SPP to a 3.10.04 appliance.  Please check to make sure your SPP ISO is not corrupt.  Validate the SHA256 value "870A7BA9BBCBCF061B1CBEDA1280DECE336C5477EA24A5BBD8B2199EEC75BD5F" of the "P05006_001_spp-2018.03.0-SPP2018030.2018_0226.84.iso" SPP.

[Haithem]

Hello,

3.00.xx is EOL, 3.10.08 is the supported version for 3.10.x and 4.00.07.2  for 4.00.x.

to update to SPP2018.03.0 you need one of these versions but you need to know also that this version of SPP do contain 4.50 and not 4.62 , OA 4.80 is part of this SPP. I would say that you need to create custom baseline online or thru OV GUI to include 4.62. 

Haithem,

[Eugen Rodekuhr]

So now we are stuck again.

The full SSP contains 4.62 but isd not signed from HPE.

The base bundle does contain VC firmware 4.5

The bin file can't be used as VCSU does not work wioth Oneview.

So how can I update to VC firmware 4.62 in an OneView environment?

[peyrache]

Create a custom SPP including
OA, VC ,ILO
Then update thru Oneview
JY

[Eugen Rodekuhr]

Thank you.

Will try that

[Eugen Rodekuhr]

Hello,

the creation of a custom SPP is not that straight forward. the first attemtps ended with a bundle which was not accepted by OneView for several reasons - like invalid, not signed etc.

However in the end we where able to generate a bundle which was accepted by OneView. The relase notes stating pretty clear that VC firmware 4.62 contains firmware 2.15 for 8GB/20Port Fibre Channel Modulen and the firmware 3.09 for the 8GB/24Port module.

If we try to upgrade to 4.62 Oneview state that FC firmware 3.05 or 3.08 is installed but does not offer to upgrade to 3.09.

Is that the correct display or is it just a bug in Oneview again and it states just a wrong version.

Any feedback is welcome

[peyrache]

When you connect to OA chassis
What are version specified in information Tabs for VC-FC ?

[Kerry Quillen]

I'm have similar issue.  I tried creating a SPP with just c7000 OA and VC firmware but Oneview complained so using SPP 2018.03 w/ the hot fix supplement bundle, I created a custom SPP using all same filters I've used in the past.  However when I uploaded to Oneview I got error "Unable to validate the signature for the HPE BladeSystem c-Class Virtual Connect Firmware, Ethernet plus 8Gb 20-port and 8/16Gb 24-port FC Edition Component for Linux component contained with the firmware baseline SPP-Gen9-2018-03-Full-Gen9-Synergy-A.iso. The component does not have a valid HPE signature."  Thinking it was me, I tried several more times selecting different filters but always got the same error.  So I downloaded the full SPP and tried to upload it to Oneview.  Nope, same issue.  

[Eugen Rodekuhr]

Hello All.

we have been able to create an custom SSP from the HPE SSP site, this bundle was accepted from Oneview and we could update our environment to the versions below:

•  HP ProLiant BL460c G9 BIOS to I36 22.01.2018
• HP ProLiant BL460c G9 FlexFabric 20Gb 2-Port 650FLB Firmware 11.4.1231.6
• HP ProLiant BL460c G9 HP QMH2670 16Gb FC HBA Firmware v2.1.57.1
• HP ProLiant BL460c G9 iLO-4 firmware 2.55
• C7000 Onboard Adminiastrator firmware to 4.80
• C700 Virtual Connect firmware 4.62 (Ehternet 4.62 / FC 8GB/20Port 2.15 - FC 8GB/24Port 3.09)

It seems that our original issue is solved now and after roughly one week we do not see any issues.

Seems that this version is running as needed.

Keep you posted about the outcome.

Regards

Eugen