In 3.1, Compliance compared current and baseline versions of FC HBA firmware version and NIC firmware versions, but I no longer see those comparisons and can't upgrade either of them? Is this by design? Can I no longer upgrade them from the console?
I opened a ticket with Dell this morning and they developer said it would likely be a couple weeks, but maybe sooner. They told me to revert back to my snapshot taking me back to 3.1 in the mean time, so that's what I did.
We hit this today using self-generated Dell Repository Manager baselines (after spending nearly 10 hour total attempting to finally upgrade to 3.2). After a lot of trial and error with a CIFS location, it appears there is a new bug that if more than 1 period exists in the catalog path, it cannot connect.
It's pretty sad especially given that each new iteration of a baseline through DRM increments the "version" by one in the format . .xml.
I manually renamed the catalog file to catalog.xml and was able to "edit"/re-confirm our existing catalog in OME. Only at that point did all of the other card components show up in the compliance list
Hopefully this helps some other poor soul who managed to upgrade to 3.2
I updated the catalog, let it finish, re-ran a full inventory of all of my devices, let that finish, and then checked a device which previously had a NIC FW update listed. It still does not appear in the list. Its version of iDRAC is up to date, according to the catalog (v2.63.60.62 on a PowerEdge R420).
Could you please let us know if that NIC Card is being displayed in the OpenManage Enterprise under Hardware > NIC Information details
Could you please provide us the Software Identity information of that iDRAC so that we can isolate the issue why NIC is not getting displayed under the compliance report on OpenManage Enterprise.
Mracekvb23
6 Posts
2931
0
Posted June 28th, 2019 11:00