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.
Yes, the NICs seem to be appearing in the hardware inventories of the servers affected. I haven't checked all 30+ servers that I manage through OME, just the ones that I know have had NIC FW appear on the baselines in the past (and haven't been rebooted to install them yet) but aren't displaying those updates now.
There are several server models affected: R420, R430, R330, R520, R530
iDRAC versions are: 7 Express/2.63.60.62 and 8 Enterprise/2.63.60.61
I hope that suffices as the "Software Identity" information.
OMEnterprise 3.2 has a bug w.r.t reporting NIC / PERC / HBA components correctly in the FW compliance report. We have root caused the issue and are working a fix which will be made available shortly (as a minor upgrade to those on 3.2).
Neither Dell representative has appeared to be active since their last post promising an update 'shortly.' As I don't know what else may be being misrepresented, I can't fully trust my compliance reports. When will the update in question be available? Would I have to do anything special to get it other than check the console for new versions?
Mracekvb23
6 Posts
0
June 28th, 2019 11:00
whobutdrew
1 Rookie
•
11 Posts
0
June 28th, 2019 16:00
I have just noticed this as well. Have you heard/found anything?
Mracekvb23
6 Posts
0
July 1st, 2019 06:00
whobutdrew
1 Rookie
•
11 Posts
0
July 1st, 2019 11:00
LMK if you find/learn anything, please.
You never know what you have until its gone, I suppose...
Mracekvb23
6 Posts
0
July 1st, 2019 11:00
AT_Virtustream
6 Posts
0
July 2nd, 2019 17:00
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
anilkumarvkr
1 Rookie
•
52 Posts
0
July 2nd, 2019 21:00
@whobutdrew
Sorry to hear that you are no longer able to find the HBA and NIC Cards displayed under compliance report in the 3.2 OMEnterprise.
Please do follow the below steps to resolve this issue:
Update the catalog from Catalog Management (Check for Updates) wait for the catalog to get updated
Once Catalog gets updated please wait until the baseline gets updated and a new compliance report gets generated.
Please update iDRAC Firmware on servers where you are not able to find the HBA and Network Cards
once Firmware Update on the target machine gets complete, Please go ahead and refresh the inventory on all devices
Wait for the Compliance Report to get generated once again and you should be able to find your cards getting displayed.
Thanks,
Anil Kumar V K R
Dell EMC
#iworkforDell
anilkumarvkr
1 Rookie
•
52 Posts
0
July 2nd, 2019 21:00
@Mracekvb23
Sorry to hear that you are no longer able to find the HBA and Network Cards in the 3.2 OMEnterprise.
Please do follow the below steps to resolve this issue:
Update the catalog from Catalog Management (Check for Updates) wait for the catalog to get updated
Once Catalog gets updated please wait until the baseline gets updated and a new compliance report gets generated.
Please update iDRAC Firmware on servers where you are not able to find the HBA and Network Cards
once Firmware Update on the target machine gets complete, Please go ahead and refresh the inventory on all devices
Wait for the Compliance Report to get generated once again and you should be able to find your cards getting displayed.
Thanks,
Anil Kumar V K R
Dell EMC
#iworkforDell
whobutdrew
1 Rookie
•
11 Posts
0
July 3rd, 2019 08:00
@anilkumarvkr
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).
What did I miss?
anilkumarvkr
1 Rookie
•
52 Posts
0
July 3rd, 2019 19:00
@whobutdrew
Thanks for the information provided
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.
Thanks,
Anil Kumar V K R
Dell EMC
#iworkforDell
whobutdrew
1 Rookie
•
11 Posts
0
July 5th, 2019 08:00
@anilkumarvkr
Yes, the NICs seem to be appearing in the hardware inventories of the servers affected. I haven't checked all 30+ servers that I manage through OME, just the ones that I know have had NIC FW appear on the baselines in the past (and haven't been rebooted to install them yet) but aren't displaying those updates now.
There are several server models affected: R420, R430, R330, R520, R530
iDRAC versions are: 7 Express/2.63.60.62 and 8 Enterprise/2.63.60.61
I hope that suffices as the "Software Identity" information.
piyer
5 Posts
0
July 5th, 2019 16:00
@whobutdrew and all,
OMEnterprise 3.2 has a bug w.r.t reporting NIC / PERC / HBA components correctly in the FW compliance report. We have root caused the issue and are working a fix which will be made available shortly (as a minor upgrade to those on 3.2).
#iwork4dell
whobutdrew
1 Rookie
•
11 Posts
0
July 9th, 2019 16:00
@PI_001 Would we have to do anything special to receive this update, or just let the console inform us that an update is available?
whobutdrew
1 Rookie
•
11 Posts
0
July 15th, 2019 09:00
@PI_001 @anilkumarvkr
Is there a timetable yet for the update to be released?
whobutdrew
1 Rookie
•
11 Posts
0
July 31st, 2019 11:00
Previously, another poster and I were in communication with Dell employees about NICs not reporting in to OME. See here: https://www.dell.com/community/Dell-OpenManage-Enterprise/Firmware-Compliance-Question/td-p/7324044
Neither Dell representative has appeared to be active since their last post promising an update 'shortly.' As I don't know what else may be being misrepresented, I can't fully trust my compliance reports. When will the update in question be available? Would I have to do anything special to get it other than check the console for new versions?