Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

145353

February 15th, 2016 13:00

Need help with using an xml file for system profile changes

I am looking to speed up deployment of newly racked servers by updating their server profile info via xml import and I am getting stuck.

I am able to successfully export the profile as an xml file to NFS.

I am not having luck modifying data on import.

My first super basic attempt is just changing the drac name.

Here is the contents of the xml file I am trying to import:

");">
labs-001-dev-a01-dc1.example.net
The job fails.

Any ideas on what I am doing wrong?

615 Posts

February 24th, 2016 16:00

Hi Martin,

I found my issue.

In the gui you can enter a FQDN like something.example.com in the DNS Rac Name field.

That will fail via a racadm import as apparently a . is not allowed when updating the "NIC.1#DNSRacName" attribute.

Is this a DRAC bug?

615 Posts

February 15th, 2016 14:00

So upon further exploration I was able to see that I am not able to update any data that is in comments in the original export.

I was successfully able to update a non commented attribute.

Soooo many of the items I need to configure are listed in comments, specifically RAID elements and Users.2#Password. Is there a flag I need to use to allow me to edit those attributes?

February 16th, 2016 00:00

Hi,

You should be able to import those values by uncommenting them, see the following Whitepapers (the first one has examples for creating RAID sets and virtual disks):

615 Posts

February 16th, 2016 11:00

Thanks Martin.

I am already using those for reference but thank you for the links!

I am still experiencing failure for updating attributes that were commented on export.

Here you can see a content comparison for successful vs failed.

---- Successful----

ADMIN NOTE: Service tag removed per privacy policy> TimeStamp="Mon Feb 15 12:50:44 2016">

 

    something

 

The previous xml contents provide a successful import and that is a non commented attribute:

[Job ID=JID_556205893224]

Job Name=Configure: Import system configuration XML file

Status=Completed

Start Time=[Not Applicable]

Expiration Time=[Not Applicable]

Message=[SYS053: Successfully imported and applied system configuration XML file.]

Percent Complete=[100]

---- UnSuccessful----

ADMIN NOTE: Service tag removed per privacy policy>" TimeStamp="Mon Feb 15 12:50:44 2016">

 

    something.example.net

    something.example.net

 

The previous xml contents provide an unsuccessful import and those are commented attributes:

[Job ID=JID_556208904510]

Job Name=Configure: Import system configuration XML file

Status=Completed with Errors

Start Time=[Not Applicable]

Expiration Time=[Not Applicable]

Message=[SYS055: Import of system configuration XML file operation completed with errors.]

Percent Complete=[100]

----------------------

Is there a way to get more verbose error output?

Looking at my failed xml do you see anything wrong with syntax?

February 17th, 2016 03:00

I don't see any issues, what is the iDRAC firmware you are running on R730 where you are trying to do this?

I might have some time later this week to try this in my test environment, will let you know.

615 Posts

February 17th, 2016 08:00

Thanks Martin!

iDRAC/LC 2.21.21.21

February 22nd, 2016 08:00

I did some simple testing on my test environment to change the iDRAC hostname.

Created an export of the current config with:

C:\Temp>racadm -r 192.168.2.202 -u root -p calvin -i get -f c:\temp\idrac-r630.xml -t xml

After that I edited the XML file to only contain the following:



HYPERV-idrac





That config I pushed back with RACADM into the iDRAC and that changed the hostname.

C:\Temp>racadm -r 192.168.2.202 -u root -p calvin set -f "C:\Temp\idrac-r630.xml" -t xml

Attached the xml file for you to test.

1 Attachment

February 25th, 2016 08:00

That is not a bug, you should not place the FQDN in the hostname field.

Place the hostname in the hostname filed and the domain in the actual domain.

The XML values for those are:

DOMAIN.LAN
Enabled

615 Posts

February 25th, 2016 08:00

Martin as a user I would disagree that this is best since the DNS DRAC Name field is what is presented in the following places to the user.

DRAC Login page

DRAC GUI Browser tab

Virtual Console window label

OME Device Name (used by all group associations in OME)

Since that field is presented in so many places it is the data that users rely on to ensure they are working on the correct system. Being able to have that match the OS Hostname of the system in large deployments is VERY HELPFUL.

I would like to make a feature request that a FQDN be allowable in that location.

60 Posts

November 23rd, 2018 03:00

Hi, I have the same issue, where you able to get around this in the end? - thanks

8 Posts

April 6th, 2021 07:00

I was facing a lot of problem with a xml editor then i came across an article fretic which has a lot of alternatives and solutions to xml problems 

Moderator

 • 

3.4K Posts

April 6th, 2021 08:00

Hell,

thanks for this article!
Marco

No Events found!

Top