Reference Guide

41 RESTful Server Configuration with iDRAC RESTful API

2.13

2.14

Using partial SCP imports

Backing up, restoring and cloning entire server configurations is useful but in some cases only small changes

are required. For example, you might need to clone only a few BIOS settings. In such cases, XML imports are

useful because it is possible to modify multiple settings in one go. This is in contrast to using RACADM single

object set commands where each setting must be modified individually.

It can be valuable to have a set of preconfigured XML snippets containing settings for just a subset of a

server’s configuration available when needed. Like a source clone image, they are known to be good and

can be imported without having to modify more settings than required.

Creating SCP files for partial imports

Exported server settings within an SCP are saved in XML format that can be easily edited with a text editor.

XML uses open and closing tags and hierarchy to group content.

In the following example the VNC server settings have been singled out. In this example, the start and end

tags for SystemConfiguration and Component are retained while all other information is removed. The

same applies to the Attributes for the VNC server. When exported, the iDRAC.Embedded.1 component

section contains many more attributes, but for this example only the VNC settings have been kept.

<SystemConfiguration Model="PowerEdge FC630" ServiceTag="000000" TimeStamp="Mon

Sep 26 18:57:00 2016">

<Attribute Name="VNCServer.1#Enable">Enabled</Attribute>

<Attribute Name="VNCServer.1#Password">password</Attribute>

<Attribute Name="VNCServer.1#LowerEncryptionBitLength">Disabled</Attribute>

<Attribute Name="VNCServer.1#SSLEncryptionBitLength">Disabled</Attribute>

</Component>

</SystemConfiguration>

This SCP can be saved as a known-good configuration file for enabling VNC. The import process is the same

as shown in previous scripts throughout the document. Generally, the settings are not unique to their server

types. The PowerEdge FC630 tag at the start can be ignored and the XML can be used for any server with

VNC capabilities and of similar iDRAC with Lifecycle Controller firmware version.

2.15 Keeping order among server configuration files

Using SCP files to manage a fleet of servers can save time and effort but the number and variation of different

configuration files can multiply. One way to keep SCP files separate and in order is to use a versioning

system, such as Github or Subversion. Detailing the use of such tools is out of scope for this white paper but

a recommended best practice.