Unsolved

This post is more than 5 years old

35 Posts

147852

February 6th, 2014 11:00

system update tasks

I have OME 1.2.1. Everytime I try to run a system update task it fails. The copy portion is successful

Copied 3 of 3 packages to C:\Program Files
(x86)\Dell\SysMgt\Essentials\SystemUpdate\Packages on DURHAM-DELLOM.

however the task fails

The task failed for the target device.

Fail

 What's needed to make this work, the target machine's firewall is off, and the target is being inventorired fine.

Thanks

Eric

3 Apprentice

 • 

2.8K Posts

February 7th, 2014 08:00

Hi there,

Was this OME system recently upgraded.  Seems like the task could not acquire a target because the device group does not have an entry for that target. 

Can you try:

-        Restart All the OME services

-        Reset IIS

-        Try again

 

Thx

Rob

 

February 11th, 2014 14:00

Hello,

I'm getting something similar with a fresh install of 1.2.0.3441 on Server 2012. It seems that tasks using the iDRAC method work fine but those that need OMSA fail each time with:

Results:  File deploy command failed to execute with error message: Invalid combination of omfile and command.

The box has been restarted a couple of times in between attempts. Any advice here would be appreciated, it is likely something obvious that I've missed!

Thanks,

Matt

3 Apprentice

 • 

2.8K Posts

February 12th, 2014 08:00

Hi Matt,

A few questions:

What is the version of OMSA on the target?

Also what is the DUP being pushed via OMSA? This will clarify the issue for us.

Thanks,

Rob

February 12th, 2014 12:00

Hi Rob,


OMSA version is:

Dell OpenManage Systems Management Software (64-Bit) Version 7.3.0

(When I first started testing it was an earlier version and I upgraded to see if it would help -- still the same error on OMSA deployments though)

The packages vary but all require OMSA for deployment.

I did some further testing yesterday on another server and ran into the same message. Tried our local admin credentials and that seemed to get further (although some timeout errors on some) -- do spaces in usernames cause issues?

Many thanks,
Matt

3 Apprentice

 • 

2.8K Posts

February 13th, 2014 13:00

ah, yeah, spaces in user name may cause trouble with omremote.exe...can you test with another account?

Thx

Rob

February 13th, 2014 15:00

Thanks Rob.

Tried with another account, this one without spaces in either username and password. This allowed the tasks to complete (I get other errors but I think outside the scope of this thread).

In summary:


Username and Password both with spaces: "Results:  File deploy command failed to execute with error message: Invalid combination of omfile and command."

Username and only Password with spaces - time out errors, deployment fails.

Username and Password, no spaces - task completes.

Kind regards,

Matt

March 5th, 2014 15:00

Hi,

Recently I have installed OME 1.2.1 at Windows 2008 server. In need to upgrade firmware packages to DELL servers. While I am trying to copy the firmware files to C:\Program Files (x86)\Dell\SysMgt\Essentials\SystemUpdate\Packages folder, I cant find SystemUpdate folder in Essentials. How will it happen? Did I missed anything?

96 Posts

March 5th, 2014 21:00

Hi Muthusamy,

Thanks for your post.

"System Udpate" folder gets created by its own when you create an Update task using OME. So during the System Update process, packages are downloaded from the selected source and saved under the “Packages” folder under the “Essentials>System update".

So just browse to Manage>SystemUpdate>Non-Complaint, select the target device which requires firmware update and create an update task. Once you are done creating a task you must see "System Update" folder under C:\Program Files (x86)\Dell\SysMgt\Essentials\.

You can also refer: http://en.community.dell.com/techcenter/extras/m/white_papers/20234619.aspx

Hope this helps!

Thanks

Ranveer

 

March 6th, 2014 11:00

Thanks for your input. But I can't see my server under non-Complaint systems tab. It is available under Complaint Systems. How to move this from complaint to non-Complaint systems tab?

2 Intern

 • 

1K Posts

March 6th, 2014 11:00

The presence of your server under compliant system means OME thinks that all the firmware versions are up to date. If you feel that is not the case, you will need to download the latest catalog based on which the comparison is made.

Your OME server will need internet access if you want to download catalog from FTP or you can use a local repository as well through SUU or RM.

You can download the new catalog from the system update page itself. Just click on "Select a catalog source" and choose from where you want to update the catalog and click 'Import Now".

If your environment needs a proxy for internet access, you will need to provide your proxy details in the Preferences page. 

March 6th, 2014 12:00

Thanks. Based on on your steps, I have imported latest catalog. Also I have downgrade my iDRAC7 firmware to version 1.3 (latest 1.5). But still the server is not showing under non-Complaint systems.

March 6th, 2014 15:00

Thanks. I can see the systems under Non-Complaint system after I update latest catalog.cab. Now another problem is while push the firmware via OME1.2 thorugh RACADM (Commad line task). I am getting certificate error.

My command input : racadm update -f ESM_Firmware_JGG1X_WN32_1.51.51_A00.exe -s -u administrator -p passw0rd -l //x.x.x.x/ome

Where do I need to -s in RACADM command?

96 Posts

March 6th, 2014 20:00

Hi Muthusamy,

Thanks for the update.

I would recommend that you use the System Update feature in OpenManage Essentials to update the firmware of DRAC.

To create a System Udpate task using OME:

1. Browse to Manage>System Update>Non-Compliant.

2. Select your device for firmware update and the component which needs to be updated.

3. Click on "Apply Selected Updates" button on your right at the bottom of the page.

4. Select "Run Now" or you can also schedule the task to a later time by selecting "Set Schedule" option.

5. Select "Skip Signature and Hash Check" and provide the credentials for the target device.

After the task completes, OME will automatically trigger the inventory task which will refresh the inventory or you can also do it by doing right click on the device and select "Perform Inventory Now" or "Perform Discovery and Inventory Now".

You are done :) its easy and simple.

You can also get useful information from System Update whitepaper:

http://en.community.dell.com/techcenter/extras/m/white_papers/20217144.aspx

Also If you wana try using racadm command:

For Update you can use :

Command : C:\Program Files (x86)\Dell\SysMgt\rac5\racadm.exe

Argument : -r $RAC_IP -u $USERNAME -p $PASSWORD  fwupdate -g -u -a -d

To get the  Status :

Argument :  -r $RAC_IP -u $USERNAME -p $PASSWORD  fwupdate –s

Thanks

Ranveer

 

March 11th, 2014 08:00

Hi Ranveer,

I tried to reset the DRAC using remote RACADM and that is working properly but fwupdate throws error.

 

C:\Program Files\Dell\SysMgt\rac5>racadm -r 10.44.11.114 -u root -p passw0rd rac

reset soft

Security Alert: Certificate is invalid - Name on Certificate is invalid or does

not match site name

Continuing execution. Use -S option for racadm to stop execution on certificate-

related errors.

RAC reset operation initiated successfully. It may take a few

minutes for the RAC to come online again.

 

 

C:\Program Files\Dell\SysMgt\rac5>racadm  -r -s 10.44.11.114 -u Administrator -p

passw0rd fwupdate -g -u -a 10.44.34.190 -d C:\ome\FW 1.51.51\ESM_Firmware_JGG1X

_WN32_1.51.51_A00

ERROR: Unable to connect to RAC at specified IP address.

 

Not sure why is it not able to communicate during firmware upgrade whereas it can connect to reboot the DRAC.

March 11th, 2014 10:00

HI Jayakumar,

Few suggestions:

1. Remove "-s" from the command, as it would abort the command if the certificate is not proper.

2.  The image that you have to provide for firmware update is "firmimg.d7". You can download the firmware zip file from the Dell support site and this image will be bundled in the ZIP.

3. It is possible that after reset the IP address is changed for iDRAC. Could that be a possibility ?

4. Can you run a simple "getsysinfo" command on the iDRAC ?

Also, are you facing any issues updating using OME ? You don't need to use racadm really, as OME will do the updates internally.

You can refer the whitepaper link as mentioned by Ranveer in earlier post.

Thanks,

Ashish

Top