Unsolved
This post is more than 5 years old
2 Intern
•
33 Posts
0
1936
September 4th, 2019 07:00
Deploy Template Issues in 3.2.1
So prior to the upgrade I created a template from a reference device r740XD2 and deployed it using Configuration Compliance with no issues. It was a very handy little tool!
That being said, I tried this again for a new batch of machines after the update and it seems like there are many elements that can't be applied for some reason or another - more than the error message leads on. Does anyone know what's going on here?
I have tried the previous template I used, tried recreating the template, exporting the template directly from iDRAC and using it as the compliance baseline - still no luck.
No Events found!
Daniel My
12 Elder
•
6.2K Posts
0
September 4th, 2019 11:00
Hello
You would need to go through each failing attribute and track the reason. The AC power recovery delay says it cannot modify a read only attribute. The setting will be read only if AC power recovery is disabled. It may be an issue of the device used to profile having the option set at some point and then recovery being disabled.
You should also check firmware version. All hardware should be at the same firmware revision before configuration settings are applied because configuration options may change with firmware updates. For adddcsetting enabled, I'm not seeing that exact syntax in the latest CLI guide. The command attribute may have changed with firmware updates.
I doubt each of the failed attribute changes have the same resolution.
Thanks
Daniel My
12 Elder
•
6.2K Posts
0
September 4th, 2019 12:00
Anything that is enabled in the compliance template will need to match. If it doesn't match then it will be non-compliant. If you are going to have custom fields for values that may differ on each system then you may need to deselect those fields in the template.
qdellforum
2 Intern
•
33 Posts
0
September 4th, 2019 12:00
Thanks Daniel. I can confirm all firmware was updated - as I used OME to check compliance. As far as tracking why each failed attribute has failed, how I would be able to do that for such attributes that are blank and showing up an out of compliance? Check this screen out: Blank values are out of compliance for being...blank?
qdellforum
2 Intern
•
33 Posts
0
September 4th, 2019 13:00
That doesn't make sense Daniel, some of those fields aren't "enabled" or "disabled" (Custom Asset Tags, for example, don't have any "expected value" yet it's not compliant?).
The only way I can narrow down is by ALL/iDRAC/BIOS/NIC/RAID, I'm not able to select the individual components here.
Can you do me a favor and confirm the ability to create a config profile from a reference device and the ability to apply it to the same model of server? This is not working for any type of server I try to clone and deploy, I have tried R740XD2 and R640's today. I was able to deploy these profiles without issue on the last version of OMEnt.
Daniel My
12 Elder
•
6.2K Posts
0
September 4th, 2019 13:00
I don't have the environment set up to test deployment. I've been planning to get something set up, but I haven't gotten around to it. Maybe someone in the community can chime in on whether or not they are experiencing issues with 3.2.1. I have not heard of any known issues.