Unsolved

This post is more than 5 years old

4 Posts

31298

March 18th, 2014 13:00

OME 1.3 - Updates Never work

I'm trying to push firmware updates to some R710 hosts, I have created a new SUU on a local server. Pointed to the SUU. Then inventoried the hosts and start the update process, and nothing ever seems to happen after the files are copied..

These are ESXi 5.5U1 hosts, and the updates are going thru the iDRAC6. Any suggestions to get this fixed?

4 Apprentice

 • 

2.8K Posts

March 18th, 2014 13:00

Hi there and thanks for the question.

What are the Task execution details?  When the task completes what does the execution details say?

Thx

Rob

4 Posts

March 18th, 2014 14:00

4 Apprentice

 • 

2.8K Posts

March 18th, 2014 15:00

Ok, this helps.

It looks like this shows maybe a Linux bin file trying to apply to an iDrac which won't work.

Can you confirm you are just discovering this iDrac with WSMan?

You might be using SUU64. You should use SUU32 or FTP and inventory with only WSMAN for the iDRACs that are being updated. The IDRAC will not support *.BIN packages

 Steps:

 -          Get a catalog source that is SUU32 or FTP site

-          Inventory the iDRAC with WSMAN only enabled.

-          Select iDRAC as preferred delivery mode

-          Update the iDRACs.

Let me know if that helps.

Rob

4 Posts

March 26th, 2014 15:00

I corrected the catalog to an SUU32 source, on our local OME server. Confirmed iDRAC is ONLY using WSMAN and receiving the following errors:

Results:  Timeout was reached for obtaining the software update status from the target device. Please verify  the credentials specified are valid and you can still connect to the device and re-run the inventory to determine if the update was successful.

I confirmed I can connect to the iDRAC using the provided credentials, and I re-inventoried the device, but the BIOS was not updated. This is a Dell R710.

2 Intern

 • 

615 Posts

March 26th, 2014 15:00

Try clearing the lifecycle controller job queue then running a soft reset of the drac then run the update task again.

You can view and delete the queue remotely using wsman from a linux server with these commands:

View Job Queue
wsman enumerate "http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LifecycleJob" -h DR.AC.IP.XX -V -v -c dummy.cert -P 443 -u root -p calvin -j utf-8 -y basic

Delete Job Queue
wsman invoke -a DeleteJobQueue "http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_JobService?SystemCreationClassName=DCIM_ComputerSystem,CreationClassName=DCIM_JobService,SystemName=Idrac,Name=JobService" -h DR.AC.IP.XX -V -v -c dummy.cert -P 443 -u root -p calvin -k JobID="JID_CLEARALL" -j utf-8 -y basic

If you don't have wsman you can do the queue view and clear from your OME windows server but I don't have the command line code for that.

2 Intern

 • 

1K Posts

March 26th, 2014 22:00

You may have to enable CSIOR as well on the target. You can get information on the same in this post:

http://en.community.dell.com/techcenter/systems-management/f/4494/p/19515744/20413397.aspx#20413397

2 Intern

 • 

1K Posts

March 26th, 2014 22:00

Hi.

Since it is an iDRAC6, can you try couple of things:

  • What do you see when you execute this command:

winrm e cimv2/root/dcim/DCIM_LifecycleJob -u:root -p:calvin  -r:https:// /wsman:443 -SkipCNCheck -SkipCACheck -SkipRevocationCheck -auth:basic -encoding:utf-8

  • If you see something, can you clear the job queue using this command:

winrm invoke DeleteJobQueue cimv2/root/dcim/DCIM_JobService?CreationClassName=DCIM_JobService+Name=JobService+SystemName=Idrac+SystemCreationClassName=DCIM_ComputerSystem @{JobID="JID_ "} -u:root -p:calvin -r:https:// /wsman:443 -SkipCNCheck -SkipCACheck -auth:basic -encoding:utf-8

Note : Giving JID_CLEARALL for Job ID will delete all the queued jobs. To delete a particular job, give the job ID of that particular job.

  • Also, can you do an iDRAC reset from the iDRAC console before trying again to perform a system udpate.

Please let us know if this helps.

4 Posts

March 28th, 2014 09:00

After turning the inventory feature on the host, rebooted and re-running the FW update process via OME the issue remains.

I have given up on the OME method and I think I'll take up the WinRM method, however I'm having trouble determining the scehma to use for the firmware update, the closest I've found is the software update schema.. Do you know of any sample scripts for this? I've also been unable to find any specific to WinRM, instead most are for WSman.

0 events found

No Events found!

Top