I'm having an issue with OME 1.2.1 and a couple select updates. The main culprit is a NIC update for the Broadcom NetXtreme Gigabit Ethernet #2 and Broadcom NetXtreme I and NetXtreme II Driver Family (CYKKJ) . My systems show non-compliant, yet I have tried every which way to determine compliance via OME and manually on each system. These servers are 64bit (Windows 2008 R2) and note has been taken that 64bit DUPs are not supported. I'm also having issues with a PowerEdge 2800 and the Intel(R) Pro/1000 MT Network Connection Driver -- I have 22.214.171.124 installed and 126.96.36.199 (NIC_DRVR_WIN_R120343.EXE) shows as available but does not change compliance.
I am curious what I am missing to show these hosts as compliant or to resolve compliance manually -- any ideas? Hopefully my picture is legible after posting.
Solved! Go to Solution.
I have been working very closely with Dell for months on v1.2, we were told that this would be addressed in a catalog update in mid December.
Hopefully the catalog updates will help.
I also have a R720 that is not showing all of the updates that the server requires. It only shows BIOS and NIC firmware, yet I know it has a few other firmware updates that are needed as well. This R720 is running RHEL6 with OMSA and inventory collector running.
A different R720 server that runs ESXi 5.5 and OMSA 188.8.131.52 was tested through OpenManage Integration 2.0 and all available (and accurate) updates were listed for that server. Both products (OME and OpenManage Integration) should be using the same catalog information, correct? So my assumption was that OME is lacking more than just catalog functionality. Or am I way off base? OpenManage Integration so far has been pretty neat for my virtualization servers.
I'm just a bit puzzled on the OME solution as I have tried it several times in the past years to no avail -- I'm not convinced it has progressed far enough to be a real server update compliance system? On the plus side, it does give a great view of server information in one location.
I guess my question is: does anyone that actively uses OME use it exclusively (with accurate results) to monitor their server hardware update compliance? Do you still need to manually manage the servers outside of OME? I'm having to use idrac updating more often than I thought I would when I rolled OME out.
OME isn't perfect, it does have it's "issues" and quirks but the support on it is relatively good and they will figure out the issues even if it takes a few calls. I don't often have to update my ESXi boxes outside of OME, but when I do I just build a linux ISO disc using repository manager and remotely boot from that ISO and let it do it's thing.