Oneview DL380 Gen10 Update Firmware

[Brentos]

We are testing out Oneview using the 60 day trial. I was able to update a server using a fimrware bundle that I uploaded but when I try to use updates the oneview has downloaded it gives me:

Unable to generate the install set due to a problem with the HPE Support Center user token. (CDS_059)

I have replaced the token, does the same thing. Could it be a license issue or something with my HPE account? IS this something the trial license does not allow?

[TKop]

Licensing shouldn't be affecting this case.  That is from an error returned from the HPE backend when validating the user token to determine if the account is OK/valid.  The resolution should have a HPESC response code at the end?  What is that value?

[Brentos]

I see

HPESC response: 311.

[TKop · Accepted solution]

Thanks, that code indicates an incomplete profile for the account.  It has been seen when some of the fields in the profile are not filled in.  Not totally sure what all the support center needs but filling in all the fields, including name, country, address (maybe phone number) has been found to fix this particular code. 

(looking to enhance the resolution message for that particular code in the future)

[Brentos]

That seems to work great. Quick question as I am new to Oneview, if this a new out of box server should I do the fimrware bundle then an update or will the update contain anything the fimrware bundle will.

Thanks!

[ChrisLynch]

OneView will update all that is needed. You do not need to update the server prior to adding it to OneView. Simply use the Update Firmware feature and the rest is handled. Just know that the Updates Bundle (which uses a web backend) is not available within the server profile resource yet. You will still need a legacy SPP ISO image to update firmware with server profiles.

[TKop]

Good to hear it worked! 

I assume the FW bundle you used was the full SPP downloaded from HPE?  If so, using the FW bundle or the Update of the same version are equivalent, or as you phrased it, the Update will contain the same components in the FW bundle.  These are two different approachs to providing FW components for OV to utilize. The SPP downloaded from the support center and the Update used on the appliance are "defined" from the same meta data - if the versions are the same of course.  

The FW bundle approach in OV involves you first retrieving the bits somewhere outside of OV, often a full or custom generated SPP, and then uploading those bits (often a large iso) into OV to be used as the FW update.

The Update approach in OV streamlines the experience and of course does not require any upload.   Through this flow, OV retreives only the components it needs for the FW update from HPE based on the inventory of the server.  Just the needed components are directly downloaded into the OV FW repository and then OV uses them for the FW update.