Reference Guide

39 RESTful Server Configuration with iDRAC RESTful API
2.12 Applying a source configuration image to a target server
The configuration files resulting from exporting settings using the Clone options can be imported just as easily
and in the same fashion as any other configuration file using the import scripts previously shown.
Utilizing the script which was modified to include the ExportUse option the source image configuration is first
exported.
$ python ./redfish_SCP_export_clone.py 192.168.0.120 root calvin
jwr_rf_clone.xml
- JID_968276760233 successfully created for ExportSystemConfiguration method
- Query job ID command passed
- Job not marked completed, current status is: Running
- Message: Exporting Server Configuration Profile.
- Query job ID command passed
- Job not marked completed, current status is: Running
- Message: Exporting Server Configuration Profile.
- Query job ID command passed
Job ID = JID_968276760233
Name = Export: Server Configuration Profile
Message = Successfully exported Server Configuration Profile
JobStatus = Completed
JID_968276760233 completed in: 0:00:24
$
2.12.1 Modifying the iDRAC IP address to match the clone target
Since a full clone is desired, all settings are kept as-is in the export file with the exception of the iDRAC
address. Unless the iDRAC IP address is updated, the target iDRAC IP address will become identical to the
source and will not function on the network. We will now modify the iDRAC IP address from 192.168.0.120 to
192.168.0.121 to avoid this address conflict:
<Attribute Name=”NICStatic.1#DNSDomaininFromDHCP”>Disabled</Attribute>
<Attribute Name=”IPv4Static.1#Address”>192.168.0.121</Attribute>
<Attribute Name=”IPv4Static.1#Netmask”>255.255.255.0</Attribute>
<Attribute Name=”IPv4Static.1#Gateway”>192.168.0.1</Attribute>
<Attribute Name=”IPv4Static.1#DNS1”>8.8.8.8</Attribute>