Unsolved
This post is more than 5 years old
4 Posts
0
1541
September 2nd, 2016 11:00
Essentials showing system compliant (incorrectly) after OMSA upgrade
I currently have OMSA 8.1 x64 deployed throughout my environment. I have a number of servers that show as non-compliant in Essentials. Some need a few updates, some newly built servers need many updates.
I uninstall OMSA 8.1 and install OMSA 8.3, and the same server now shows as Compliant, and not needing updates.
Our current build image has OMSA 8.1 installed already, so I tried uninstalling 8.1 and installing 8.3 before I even added a new server to the Essentials console. It still shows as compliant, even though this new server needs quite a few updates to firmware and drivers.
I am using the latest Dell online catalog for Essentials, and created a SUU from the same online catalog to compare.
- The SUU shows firmware updates are needed.
- OMSA shows warnings that firmware updates are needed.
- Essentials shows the system needs no updates after moving to OMSA 8.3
Is there a step I'm missing in this process? I've tried removing the device from Essentials after the upgrade, and re-adding it, but it still shows as Compliant.
I recently switched Essentials advanced settings to enable downgrades, based off of a recommendation. The thought was, this would force Essentials to re-evaluate and might pick things up correctly. This actually moved the server back over to the Non-Compliant tab, but when I select the server, it shows no updates to apply.
Has anyone run into this and found a fix? Or any thoughts on new things I can try?
DELL-Arun Mo
116 Posts
0
September 6th, 2016 02:00
Hi,
Thanks for the post. You are not missing any step. Something is not correct.
Few questions:
1. What is the version of OME you are using?
2. What is the target OS you are trying to update?
3. Did you discover the target with both in-band(using OMSA) & out-of-band (using iDRAC) ?
4. What is the protocol used to discover OMSA ? (SNMP or WMI?)
5. What is the model of the target server ?
It is very difficult to pin point what is going wrong.
We have to take step by step approach.
1. In non-compliant tab, click on "Refresh" button. (This will force OME to recompute the updates).
If you still see the issue, then the data what OME has currently is not correct.
2. Open the device details tab in OME & under the software inventory table check what are the firmwares/drivers are getting listed. This is to ensure OMSA is returning correct value to OME.
Based on above, we will analyse the issue further and suggest possible actions.
DBKillian
4 Posts
0
September 6th, 2016 09:00
1) I'm using OME version 2.1.0.2635
2) Target OS is Server 2012 R2
3) I perform discovery in-band with OMSA only.
4) I use SNMP to discover all servers
5) I have more PowerEdge R720's, but a few R730xd's as well.
I've tried refreshing the non-compliant tab with no change in results.
Viewing the software details reported by OMSA, for instance...
IDRAC firmware shows as 2.21.21.21, and the current catalog used by OME has 2.32.31.30
BIOS version is 2.5.2, and the current catalog used by OME has 2.5.4
...among other items.
Additional points:
After enabling downgrades and disabling them again within OME, all of the servers that have been upgraded to OMSA 8.3 now show in Non-Compliant again, but show no updates to apply.
These same symptoms happened for servers I upgraded to OMSA 8.2 as well.
When installing the new version of OMSA, I choose custom installation and select the Enhanced Message Format, but I don't really see how that would have any impact on what I'm seeing.
DBKillian
4 Posts
0
September 15th, 2016 11:00
Any thoughts on what I could try next?