Home > Servers > Systems Management > White Papers > Server Configuration Profiles: Reference Guide > Structure
At a high level, both formats follow a similar structure:
SystemConfiguration
‐ Components
‐ ‐ Attributes
SystemConfiguration is the root node in both formats. It contains properties such as Model, ServiceTag, and Timestamp, which are populated based on the system information where the template was generated.
The template can also be generated with informational comment data that provides more details about how the template was generated.
Components are children of SystemConfiguration and are uniquely identified by a Fully Qualified Device Descriptor (FQDD). The FQDD format is iDRAC.Embedded.1, BIOS.Setup.1-1, and so on. There can be numerous components per template, but each component is unique.
Example: <Component FQDD="NIC.Slot.4‐1‐1">
The FQDD helps describe the device and, in some cases, the physical location of the device in the target server. When a template is applied to many servers, the slot devices must be in the same slot position in the target server. For example, if the template’s FQDD points to slot 3 but the target device is in slot 4, the configuration will not be applied. For more recommendations, see Golden template (one to many).
Note: In the case of storage devices, components can also be nested within components.
Attributes are children of Components and are name-value pairs used to identify and set specific component configuration settings.
Example: <Attribute Name="BlnkLeds">0</Attribute>
The Attribute Registry drives the behavior of all attributes. This registry contains attribute information such as description, possible values, read-only status, dependency data, and much more.
The latest version of the Attribute Registry is available at www.dell.com/idracmanuals.
If issues are encountered with a specific attribute, the Integrated Dell Remote Access Controller 9 Attribute Registry is the best place to start.