Unsolved
70 Posts
0
1433
June 22nd, 2021 01:00
Firmware Compliancy
Hi,
I am running OME version 3.6.0 (Build 41) appliance and repository manager 3.3.1.694 on a windows VM.
When i run the Compliance check it will show a lot of Firmware compliant but also a lot with the status unknown. it states in the colon "Update file not in catalog: Check dell.com/support" ?
This is strange because the Firmware is in the Repository available so it should say "OK" with the current correct version for the baseline.
What is causing this?
screenshot of OME:
Screenshot of my repo:
No Events found!
DELL-Charles R
Moderator
•
4.7K Posts
0
June 22nd, 2021 07:00
Hello TechnicalEngineeringKLM,
Does the Jobs log give you any more details about what went on with the job?
Try reboot the appliance, and the host if you can, retry and check results.
Is this happening to more than one host?
I'll run this by one of our Systems Management engineer along with your feedback and update you with their recommendation.
justin gray
2 Intern
•
143 Posts
0
June 22nd, 2021 08:00
What model server(s) and what version of iDRAC are you seeing this on?
Do they fall into the support matrix for v3.6?
TechnicalEngineeringKLM
70 Posts
0
June 22nd, 2021 23:00
Hi,
yes this problem is seen on a lot of servers, the appliance is already rebooted more then once. it is strange because we also run the Plugin "Update manager" and that gives different firmware replies and also when i connect the default DELL-ESXi-Default_catalog it will give again different output.
what is should expect is, see the Current baseline versions and the current versions on the server no matter which repo i use. that is how it should work in my opinion.
TechnicalEngineeringKLM
70 Posts
0
June 22nd, 2021 23:00
i first saw this issue on the PowerEdge R740xd with the latest iDRAC release on it at this time 4.40.00.00, but it shows alos on the PowerEdge R730xd with iDRAC version 2.75.100.75.
styrange thing is, i see this problem only in a baseline for nodes used in a vSAN cluster with a carefully created vSAN repo at it.
DELL-Erman O
Moderator
•
2.9K Posts
0
June 23rd, 2021 00:00
Hello, I just looked at the thread, it's a bit confusing. Thanks for the model and other info. I will be sharing this information with my colleague.
DELL-Erman O
Moderator
•
2.9K Posts
0
June 23rd, 2021 01:00
Thanks for your feedback, It will be useful to those in the community. Have a good one!
TechnicalEngineeringKLM
70 Posts
0
June 23rd, 2021 01:00
i think i solved the issue already,
i thought the repo was created by the repository itself but it seems to be created by hand and so there was a lot of firmware indeed missing from in the repository.
i will create the repo my self and then check the compliance agian and see what the results will be.
After creating it by again it looks that the problem is solved.
so Thx for taking the time to respond.
Greetz peter
TechnicalEngineeringKLM
70 Posts
0
June 23rd, 2021 01:00
Thx for responding but i solved the problem, it was a human error in this case. lots of firmware was missing from the repo.
it is somewhat confusing when you see a release number in the repository like 16.17.01.00 for the HBA adapter and it is actually the HBA 330 Mini, its the same firmware version and in the description it is also almost the sam. so this kind of mistakes will easily be made i guess.
Greetz Peter