Unsolved
7 Posts
0
891
December 15th, 2022 07:00
OME configuration compliance doesn't work
Hi,
I have issues with configuration compliance and sending updates to the hosts.
when I create a template with server configuration it shows me an error
when I try to send FW update to one of the hosts that can't be completed.
any hint on what I can do, btw the OME it's 3.8.2 version
No Events found!



DELL-Young E
Moderator
•
5.3K Posts
0
December 15th, 2022 18:00
Hello, in order to troubleshoot it would be great to know how you did what you did step by step. Is there a screenshot where you see the error or so?
randy7997
7 Posts
0
December 16th, 2022 08:00
Hi Young,
i started creating a template, the ones that finished completed were imported from file the other were imported from a reference server and didn't work
then creating a baseline compliance incomplete
DELL-Young E
Moderator
•
5.3K Posts
0
December 18th, 2022 16:00
Hello as far as I know this would only be activated for those who have purchased the OME enterprise license.
Managing the device configuration compliance
By selecting OpenManage Enterprise > Configuration > Configuration Compliance, you can create configuration baselines by using the built-in or user-created compliance templates. You can create a configuration compliance template from an existing deploy template, reference device, or by importing from a file. To use this feature, you must have the Enterprise level license of OpenManage Enterprise and iDRAC for servers
https://dell.to/3Yzdyov
randy7997
7 Posts
0
December 19th, 2022 12:00
Hi,
as I know we have an OME enterprise license. and the error is different because I can create the template, but when I try to create the baseline shows incomplete.
DELL-Young E
Moderator
•
5.3K Posts
0
December 19th, 2022 21:00
Hi since you have purchased license at this point I would suggest you kindly open a ticket with tech support by phone or email. https://dell.to/3HLSIwf
Silver-mox
1 Rookie
•
60 Posts
0
January 5th, 2023 08:00
Unsure if this helps, I had a client with similar issues. We had to ensure the following was in place.
1. The idracs had the correct licences (Enterprise - as advised above)
2. NTP & SNMP were correctly set and NTP was set on the OME appliance
3. The firmware versions on the source and target servers were the same (very important as options change with firmware releases.)
4. Model to model templates (BIOS settings AMD to AMD, Intel to Intel)
5. In 4 years of development, I've never been able to deploy local idrac user accounts with compliance templates, for some odd reason it creates the accounts however with blank passwords. use RACADM instead.
We use RACADM to commission our servers and tend to use the templates to confirm compliance rather than do the commissioning of that makes sense.
HTH
Mox
randy7997
7 Posts
0
January 11th, 2023 13:00
Hi,
The problem was solved by making a rule on the firewall that permits traffic from iDrac to the OME, but now I have a doubt does the configuration compliance work in the 11th and 12th servers?