My Microsoft CA script has stopped working with newer idrac versions, and I'm wondering if it's an issue with our FQDNs - throwing it out to anyone who might have ideas.
I'm getting this:
Configuring: [iDRAC.Security]ERROR: RAC917 : The syntax of the specified command is not correct. See the command help text. To see the help text, run "racadm help ".
I think the main issue is that the cfg file looks like this: [iDRAC.Security] CsrCommonName=idrac-hostname.contoso.local
And that it doesn't like either the hyphen in the fqdn, or else the cfg has changed in a newer version. Oddly, i also can't set this manually which boggles my mind: racadm.exe -r $FQDN -u $idracuser -p $idracpass set iDRAC.Security.CsrCommonName $hostname.$domName
So... What changed?
Edit: I'm also running - before this section - this:
Digging in more, I think the issue is that previous versions you could import a .cfg file of the config data you wanted.. Now however that doesn't seem to work, it only allows -f to be done with a -t of xml or json.
Though that doesn't explain why I also can't update it manually, but I'd rather use a dynamically created cfg file vs a bunch of commands anyways.
Are you trying with commonname or "CsrCommonName". Actual command is
racadm set iDRAC.Security.CsrCommonName MyCompany
Can you also try with xml/json format and see whether it works? If it is not working with these can you share the server model and iDRAC FW version you have on the server
you can run below command to get xml file with current iDRAC configuration.
racadm -r "ip" -u root -p "pwd" get -t xml -c iDRAC.Embedded.1 -f idrac.xml
You can make necessary change on the config file by editing the file. Once you done with the changes you can save the file and run below command to upload the configuration to iDRAC
racadm -r "ip" -u root -p "pwd" set -t xml -c iDRAC.Embedded.1 -f idrac.xml
JRRW
1 Rookie
•
3 Posts
932
0
Posted March 24th, 2021 10:00
Even in their newest racadm they don't do a good job on clarifying things - i.e. they say to run
racadm set iDRAC.security.commonname MyCompany
Yet that command doesn't actually work in that syntax.
Really frustrating to not have better or more accurate guides.