System Update module problem after updating to OME 1.2

Can we get more information about the setup ?

Was it an upgrade from OME 1.1.1 to OME 1.2 ?

Is it a local or remote database  (SQL Express or SQL Server?) ?

What is the Catalog version, date, prior to upgrade and after upgrade ?

After the upgrade was discovery+inventory task run on all the devices (discovery ranges)  ?

What is the operating system in which OME 1.1.1/1.2 was installed ?

How many devices are being managed (Ex: 9G, 10G, 11G, 12G Servers) ?

How are these devices discovered (Ex: SNMP, WSMAN etc protocols) ?

Does all these servers have OMSA installed ?

Are any of iDRAC 6/7 discovered+inventoried using WSMAN protocol ?

Thanks,

Raj Shresta

Hi there,

Looks like some folks are seeing this.  Please review this thread.  If you have confirmed you've re-run discovery AND inventory, you may need to open a ticket.  We're looking at it.

Thx

Rob

en.community.dell.com/.../19515744.aspx

Sure, and sorry for the double post:

About version yes, it was 1.1.1 to 1.2.

Remote SQL Server 2008 R2.

The catalog hasn't changed since previous version.

Yes, all the ranges were re-discovered re-inventoried.

OS is Win 2008 R2.SP1

30 devices since a PE 2950 to R720 and some blades: M610, M710 and M910

Win server are being discovered using WMI and a ESXi 5.1 using WS-Man

All servers have OMSA 7.3

WS-Man is used for ESXi 5.1 running on a R710 /iDRAC6 (1.95.00 Build 5)

I forgot to add: I have PowerVaulds MD3000 and MD3200 discovered by array discovery.

And ML6000 discovered by SNMP.

Weird things are that a R720 is not detecting service tag (appears as unknown) (same for its OMSA 7.3)

The ML600 is not displaying any service tag at all.

yeah, review that other thread and we can work it over there.  But we might need a ticket ultimately.

BTW, ML6000 tape devices don't display service tag.  I don't think the SNMP agent supports that field.

On your R720, please run the Dell Troubleshooting tool against the server. If it is SNMP + OMSA, run the SNMP test and let me know if the result set displays the "Server Administrator" version in the result table.

Rob

Hi,

We have work arounds for this. We will dig deep and come up with a fix but the workaround as of now is as follows:

After upgrading from previous version to 1.2:

• Get the latest SUU dvd. Mount it on the OME server.
• Launch OME and navigate to system update tab
• Click on Select a catalog source
• Provide the path to the catalog in the SUU dvd. The catalog.cab or catalog.xml file can be found in the repository folder of the dvd
• Click on Import now.
• Once the catalog is imported, wait for some time for the compliant and non-compliant list to be populated. Depening on the number of devices, the time for compliance report to be generated may vary from 10-25 minutes.
• Once the report is generated, you will be able to see all your devices under proper groups of compliant and non-compliant systems.

Do you have a URL to retrieve this working catalog file rather than messing with a DVD?

Why is the default url location used by OME not updated as that would fix it for everybody?

ftp.dell.com/.../catalog.cab

Ah thanks for the clarification Rob!

Hi cameron.

I don't think the problem is that the default url location needs to be updated.  The problem might be that during the upgrade process (for some folks, not all), the catalog manifest entry in the database gets corrupted.

This SUU workaround has the side effect of re-building the manifest header in the database.  Again, I'm not positive as we are looking at this issue aggressively.  

But this is the most up to date at the moment.  We'll continue to post to this thread as we come up with additional work-arounds.

Regards,

Rob

Excellent, I created SUU dvd from repository manager and it now correctly identifies updated and non-updated devices.

Thank you very much!