try to re-export the catalog from Repository manager.  you can also connect to the Essentials server itself and try to import into the console locally to the essentials server (that way Essentials doesn't have to copy the catalog from your workstation back over to the essentials server.  )

Good morning,

Your solution worked. I had to move my catalog and the associated files to my VM on which Essentials is running and the import was successful. However, I ran into another problem.

I have a few servers that aren't compliant based on the catalog I imported. When I click on a server to see which updates I can apply, nothing shows up in the "Select Updates to Apply" pane at the bottom of the screen. I succeeded to import the catalog using all 3 methods but that's just as far as I get.

Any ideas?

More info: I'm using WS-MAN over iDRAC to discover/inventory my appliances and the preferred method for updating is iDRAC since the OS running on my servers can't run OMSA.

When importing the catalog from repository manager, please make sure to select Windows DUPs/packages. For pushing updates via iDRAC, OME needs Windows packages listed in the catalog.

If the catalog does not have Windows packages then you will run into this issue.

Thanks,

Raj Shresta

Hello Raj,

By all three methods, I meant trying to import using SUU, repository manager file and online source (in my case, it was my own FTP server).

If I look under the "Issues and resolutions" tab in Manage -> System Updates, there are no entries.

Any ideas?

You indicated that the catalog is imported using all 3 methods. Any reason why you would import catalog using different methods ? What was the last method used to import the catalog ?

Also, make sure to check "Issues and resolutions" tab in Manage -> System Updates. It will indicate any errors found for devices discovered/inventoried and provide recommendations.

If you are using repository managere, here is the recommended steps:

1. Disocovery/Inventory iDRAC using WSMAN  in OME

2. Launch Dell Repository Manager (installed on OME server).

3. Click on Create and Choose Dell OpenManage Essentials Repository

4. Enter name and description, click Next

5. Choose Dell online repository , click Next

6. Repository Manager (RM) will get OME inventory and all the devices are displayed in RM Click next

8. Choose save and download repository and click Finish

9. Choose the location to save catalog and DUPs

In OME console, from Manage -> System Updates, you should see the non-compliant devices along with available updates.

Thanks,

Raj Shresta

If you are using SUU, here is the recommended steps:

1. Mount SUU DVD or iso image

2. Launch OME console

3. Navigate to Manage -> System update

4. Click on “Select a catalog source”

5. Select a catalog source windows is displayed – Select “Use file system source(SUU)” option

6. Click on browse and navigate to the location where SUU is located

7. Select catalog.xml or catalog.cab file located in the repository folder of SUU

8. Click Import now to import catalog.

In OME console, from Manage -> System Updates, you should see the non-compliant devices along with available updates.

Thanks,

Raj Shresta

Hello Raj,

It wouldn't work cause I only had the Linux package in my repository.

Thanks for all your help!

Jay

Good day,

I followed the procedure on how to perform an upgrade using SUU. The good thing is that OME detects which updates have to be applied. On the other hand, everytime I try to apply the updates, it fails cause "the packages failed to download on target device"

I used iDRAC as a preferred way to update. I can launch a RAC console from OME to my server (PEM610x). When I start the task, OME copies the packages from the SUU folder to C:\Program Files (X86)\Dell\SysMgt\Essentials\SystemUpdate\Packages (I confirmed that the packages are there) but it can't upload them to the server.

Any ideas what could cause the update task to fail?

Thanks

Jay

Jay,

Based on the error reported it looks like packages are downloaded properly on the OME system but iDRAC failed to copy the package from OME system. Couple of things you could try:

Check the job queue on iDRAC by running this command from OME system using OS command prompt:

winrm e cimv2/root/dcim/DCIM_LifecycleJob -u: -p: -SkipCNcheck -SkipCAcheck -r:https:// /wsman:443 -auth:basic -encoding:utf-8

Expected Output –

Results should show only one job i.e. JID_CLEARALL job with status pending.

If it is showing multiple job, you can clear the job queue by running this command from OME system using OS command prompt:

winrm invoke DeleteJobQueue "cimv2/root/dcim/DCIM_JobService?CreationClassName=DCIM_JobService+Name=JobService+SystemName=Idrac+SystemCreationClassName=DCIM_ComputerSystem" @{JobID="JID_CLEARALL"} -r:https:// /wsman -u: -p: -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic -format:pretty

Note: make sure to replace , and with actual values.

Thanks,

Raj Shresta

Hey Raj,

Thanks for the response. I managed to clear the job queue. However, when I checked the queue after I cleared it, the JID_CLEARALL job status is "Pending" and the percent complete is at "0". I have rebooted my server after I cleared the job queue but I get the exact same thing.

Should I try to run the update job again or is it a problem that the JID_CLEARALL job is still "Pending"?

Thanks

Jay

Jay,

Before clearing the job queue, were there any other jobs in the queue other than JID_CLEARALL ?

Make sure to reset iDRAC (not the server) from iDRAC console or run this command from OME system:

winrm invoke RequestStateChange "cimv2/root/dcim/DCIM_SPComputerSystem?CreationClassName=DCIM_SPComputerSystem+Name=systemmc" @{RequestedState="11"} -r:https:// /wsman -u:USERNAME -p:Password -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic -format:pretty

Check the job queue to make sure it is empty and re-run update task from OME.

Thanks,

Raj Shresta

Hey Raj,

There were jobs in the queue so I ran the command to clear them all. I did a reset on the iDRAC using the command you provided. When the iDRAC came back, I still had a job in the queue

InstanceID = JID_CLEARALL

JobStartTime = Time_NA

JobStatus = Pending

JobUntilTime = Time_NA

Message = NA

MessageID = NA

Name = CLEARALL

PercentComplete = 0

Even if the update process failed, OME thinks that my M610x has been updated properly and shows up in the Compliant System and I can't get it to go back to the Non-Compliant Systems tab

Jay,

      iDRAC will always show CLEARALL job. As long as there are no other job, it can be assumed that the job queue is empty.

      The updates may already be deployed via iDRAC even though OME indicated a failure. Please note that updates such as BIOS, iDRAC firmware etc. will need a system reboot where as few other updates may not need a reboot. After OME deployed the updates, if the managed server was rebooted, all the updates would be automatically applied.  

You can also verify software inventory for each device in Manage -> All Devices. Select any device and review the info under "Details" tab.

Thanks,

Raj Shresta