Hi KBeau,

Some clarifications here

1. Servers listed in devices tab show the health status of them and not there compliant status.

2. Check the issues and resolutions section in System Update Portal, if devices are absent there also then we need to know with which protocol servers are discovered.

Yes, to add to what Amit mentioned.

The warning mark in the device tree is not related to system update. It is the health state of the server which is returned either by OMSA or iDRAC. It may be because of multiple things like power redundancy lost, or chassis intrusion, etc.

Make sure you have the latest catalog downloaded for verifying the compliance of servers.

I'm sorry, I should have mentioned that I checked all of the servers with the warning mark and they were all needing firmware/driver updates.  No physical problems at all.

I do indeed have the latest catalog.

I understand now that there is a difference between compliance and health status.

I am using SNMP and WMI for discovery.  Should I use one or the other and not both?

Thanks!

KBeau

It is good to use one protocol over other but that will not cause any problem for you. So, just for my understanding how did you make sure that the devices need a firmware/driver update? 

Also, make sure that your proxy settings are proper and try to download the latest catalog from FTP and see if that makes a difference in the system update compliance. 

Let us know how it goes

Again, I'm sorry, I do not use WMI and SNMP, I use WS-MAN and SNMP.

I do not have any proxy settings in place.  I don't think I ever have before either.  Having said that, I tried using a domain admin account but was not successful.  I used the management server as the proxy server, is that correct?

I found that they needed updates by launching the OMSA application from my Manage/Devices page.

Regards,

KBeau

Morning,

You say "yellow triangle next to their name which indicates to me that they are behind on various updates."

Do you mean on Health Status ? As Manage, Devices should all be Green in Health Status.

System Update, Non-Compliant Systems is different indicating updates from your Catalog need applying..

Proxy server is needed to connect to the internet. It is not your management server IP. If you don't have a proxy configuration, then you should be able to reach internet from the OME server to get the latest catalog downloaded. Are you able to import the latest FTP catalog in OME?

I can download the latest catalog from my management server using OME.

I see the difference you are implying with the yellow triangle and I may have used incorrect wording, but all of the servers that have the yellow triangle are behind on updates but still not showing up in the area where I would do a remote update to them. 

So, non-compliance on one tab is defined differently from the Health status on another tab.  I get that, but what I don't understand is why I can no longer do remote updates like I used to.  In the past (before I updated to most recent version of OME), all servers that needed updates showed up under the non-compliant tab.  There are only two servers listed there, both of which are virtual but none of my physical Dell servers that currently need updates are showing up there.  These two virtual servers are also the only two that show up under the Issues and Resolutions tab.

Looks like my discovery/inventory/status scheduled runs are pulling everything in, but having to go to each server individually to download and install firmware updates is a bit of a pain.

Again, I'm sure I have a setting that is incorrect somewhere, I just don't know where.  I have been using OME for quite a while but still, what am I missing here?

Regards,

KBeau

Okay, so lets try root causing with first things first.

• Can you pull out one server from your list which you know that needs update and let us know the firmware versions of a few components?
• Can you also let us know the catalog version which is present in OME?It will show that information under system update tab.
• Previously, have you been using FTP method or you have a local repository of update packages?
• Are your servers discovered using SNMP+OMSA or you have iDRACs discovered using WSMAN or is it a combination of both?

• PERC H710 Mini, F/W 21.2.0-0007, F/W available for update, 21.3.1-0001, Driver 5.02.121.64, Storport driver, 6.2.9200.16813.
• Active Catalog (FTP) Realease ID RTWNT, Release Date, 4/9/2015
• FTP only but then I also browsed to the local repository .cab file and imported it.
• I use both SNMP+OMSA and WS-MAN

So during the process of getting these answers for you the problem was solved!  Once I imported a catalog.cab file to the management server, my Non-Compliant Systems list grew and I found that now I could update them.

To sum it all up, once I pointed to a local repository (versus the Dell FTP Catalog), OME finally gave me what I needed.  I guess I assumed that pointing to the FTP source would do that to but in my case it didn't.

I am very grateful for your assistance!

KBeau