I tried to update only one package (iDRAC from version 3.30 to 3.42) and I still get "Package Verification Failed"

Any ideas?

Hey Raj,

I tried updating my M610x and it failed again. Here's what it's tryng to update:

BIOS (from 6.1.0 to 6.3.0)

Diagnostic  Application (from 5154A0 to 5157A0)

LifeCycle Controller Application (from 1.5.1.57 to 1.5.5.27)

M610x_Lifecylce Controller Application (from 6.5.3 to 7.1.1)

iDRAC (from 3.30 to 3.42)

When I start the update and I loof at the queue job, all 5 jobs appear in the queue and they all have the same job's name (ex.: update:DCIM:INSTALLED:NONPCI:"some_number":"version_already_installed".....3.30 for the iDRAC version, 6.1.0 for the BIOS, etc...)

After a few minutes, all the jobs are tagged as "Failed" with "Package verification failed" for Job Status. The update task fails but OME thinks it has been updated and the serve ris moved under the "Compliant Systems" section which is incorrect since the server still has the exact same version than before the update task (something to look for a future release maybe?). The only way I found to make OME put that server back in the non-compliant mode is to make it point to a FTP server that doesn't exist (which will cause the import to fail) and re-import the proper SUU.

One thing I realized is that the update job name for the Diagnostic Application doesn't display its current version number (should be 5154A0 but instead, it only displays "0").

I'll try to apply these updates without the Diagnostic Application and update this post after.

Thanks

Jerome

Team,

We've gotten a bit more information on the update package file that may be useful to some in this thread.

See below.

Rob

--

******

You need to upgrade to the following firmware versions *first* before updating any other components.  This is due to some changes in the certificates on the update package.

• iDRAC6/LC Firmware Release Information

o Rack/Tower (monolithic) – v 1.85

o Blades (modular) – v3.35

• LC 1.5.2

More information to follow

******

Hello,

Just to follow up on Rob's response. He is correct about having to update iDRAC first. If the current iDRAC version on your system is less than 1.85 (or 3.35 on blades) and you try to update any firmware today, you'll run into the issue seen here.

To resolve, simply add one step. Update iDRAC only to version 1.85 (or 3.35 on blades). Wait for job to complete.  This step can be done in OME to apply to multiple servers. Thereafter, you can update the rest of the components to latest.

Hope this help and here's a reference:

en.community.dell.com/.../how-to-resolve-errors-when-updating-firmware-via-wsman-in-idrac-with-lifecycle-controller.aspx

Good day,

I tried to update the iDRAC version from 3.30 to 3.42 using OME but it failed with the exact same error message (Package Verification failed). I believe OME is trying to update using the correct file (ESM_Firmware_PW2GX_WIN32_3.42_A00) which is theUpdate Package for Microsoft® Windows®).

Does that mean I have to update the iDRAC manually and then try to load my updates using OME?

Thanks

Hello Jay,

About the Job, a successful result of the "clearall job" command request will leave exactly one entry in the enumeration. That one entry has a name value of "CLEARALL". The properties PercentComplete and JobStatus are intentionally not updated and should not be interpreted in this case. Looks like your clear job is successful.

Thanks for the reply Chris.

However, why upgrading from iDRAC 3.30 to 3.42 using OME still fails? Do I have to upgrade iDRAC to 3.42 manually and then proceed with the rest of my upgrades?

You need to upgrade iDRAC from 3.30 to 3.35 first.  For details about this requirement, see the 3.35 README.txt file. This step can be automated similar to any update methods available to iDRAC OOB interface. I think this step can be done in OME through Remote Task or customizing the catalog, but I'll let the OME experts speak for it.

Once you have iDRAC at 3.35, you should be able to use OME update as usual.

Chris/Rob,

I was able to apply my updates with iDRAC v3.35 and LCC v1.5.2 so thank you guys for that. Only the Broadcom Netxtreme II Gigabit Ethernet failed to upgrade. I tried it on a both a M610x & a M610 (trying from v5.0.12 and from v6.2.15). The error message I got was "the package specified does not match the target". Are you aware of any problems updating this type of NIC?

Thanks

Jay

Jay,

I'd recommend using this blog as a guide for package errors during update:  http://en.community.dell.com/techcenter/b/techcenter/archive/2012/11/16/how-to-resolve-errors-when-updating-firmware-via-wsman-in-idrac-with-lifecycle-controller.aspx

What is the update package file name you are using?

Hey Chris,

The update package is for the Broadcom NetXtreme Gigabit Ethernet (Embedded 1-1) v7.2.20.

The name of the package I'm trying to apply is Network_Firmware_1KT2C_WIN32_7.2.20_A00.exe. It is detected by OME.

Thanks

Jerome

So I was able to update the network firmware using OME. It looks like I had to ONLY select that update in order for the update to succeed. I'll try to do more tests and try to determine what caused it the fail in the first place and update this thread when I have more details.

Thanks.  That will be really helpful.  Keep us posted.

Rob

UPDATE!

Looks like LCC 1.5.2 won't let you update the Broadcom NetXtreme Gigabit Ethernet II drivers (even if you have iDRAC 3.35)

The only way I could do it was to have v1.5.5 installed.

Cheers

Jay