OME System Update Failure

To troubleshoot the issue, create a separate system update task and select the two DUPS (BIOS, BroadCom NIC) mentioned above. Run the task against this target. After the task finishes, check if the system rebooted. Wait for 30 minutes and re-inventory the target from OME.

Yes, but I must ask, is this only for testing purposes?  Having to always do that greatly defeats the purpose of OME.

I'll test it now.

Thanks,

Jason

Dependency check failed for BIOS update when OME tried to apply it.

Can you manually copy and apply this update (BIOS_VHP27_WN32_1.11.0.EXE) on the system ?

This is only for testing purposes to determine the root cause.

Hey Raj,

I attempted to apply the BIOS update directly on the system, but I received the following error (see attached image).

Could you please attach the image again ?

I'm getting a failure on just the broadcom card across different servers. Network_Firmware_H15FK_WN_7.2.20_A00.EXE

PackageCode  1

PackageFileName  C:\Users\mhaas\AppData\Local\Temp\s3es\Network_Firmware_H15FK_WN_7.2.20_A00.EXE

PackageLog  << PACKAGE LOG (SelfExtractable) >>

==========> Update Result <==========================

Update was not applied

=========================================================================

Exit code = 1 (Failure)

2013-05-23 13:29:49

<< PACKAGE LOG (SelfExtractable) >>

Update Package finished.  Exit code = 1

PackageReleaseId  Not Available

PackageState  complete

PackageStatus  5

TotalStatus  One or more Update Packages failed during execution, but the update continued running to the end.

TotalStatusMessage  Software update complete.

System Name Importance Update Method Component Type Installed Version Upgrade/Downgrade Available Version Package Name

tradc5.lr.k12.nj.us Optional OMSA Broadcom NetXtreme I and NetXtreme II Driver Family Driver 0 Upgrade 17.2.0 Network_Driver_H8HTP_WN32_17.2.0_A00.EXE

it successfully applied when ran locally.

Hey Raj,

Not sure why the attachment didn't make it through.  Trying again...

Jason

Thanks Jason. I'll pass on the feedback internally to the Engineering team. Hopefully will have an update for you soon.

Jason,

   We need to capture BIOS logs to debug/root cause the issue. Please call Dell Tech Support (800-945-3355) and provide the logs by following these steps:

1.            Extract dup by running the command  “BIOS_VHP27_WN32_1.11.0.EXE /s /e=c:\extract_dir” .

2.           Change to extracted directory by running “cd c:\extract_dir”.

3.           Create an empty file called smaldebuglog [without extension] by running “echo “” > smaldebuglog” .

4.           Copy the payload directory up one level by running “copy payload\*.*   .  “

5.           run “biosie -u -d updatelog.txt > update.xml" for  update.

6.           Attach inv.xml, update.xml,updatelog.txt,  SMAL_DBG.log, package.xml and Dell customer logs from directories:

c:\ProgramData\Dell\UpdatePackage\log\ and

c:\ProgramData\Dell\UpdatePackage\log\support .

We have root caused the issue w/ Network_Firmware_H15FK_WN_7.2.20_A00.EXE to unsupported installation parameters. Dell internal team is working on this issue and should have an update in couple of weeks.

Thanks,

Raj Shresta

Hey Raj,

Is there anything I should reference, like a ticket number, when contacting support or will I need to start from scratch and explain what is going on?

Thanks,

Jason

Jason,

I don't think there is a ticket number per-se.  But if you reference this thread, it should help quite a bit.

Regards,

Rob