White Papers

Introduction to server configuration in OpenManage Enterprise 3.0
6 Advanced Server Configuration in Dell EMC OpenManage Enterprise 3.0
1 Introduction to server configuration in OpenManage
Enterprise 3.0
The current configuration of a server is represented as several individual elements—called configuration
attributes. For a typical server, there are several hundred such attributes, and it can be quite overwhelming to
tune all different aspects. OpenManage Enterprise 3.0 has features that make it easy for a user to capture
configuration from a “reference” server (that is, server for which all aspects have been correctly set up and
fine-tuned) and replicate that configuration to one or more target servers. Some of the configuration element
values need to be different on the different targets. OpenManage Enterprise 3.0 has features that ensure the
configuration captured from a source server is correctly replicated to a target, while ensuring that the
configuration elements that need disparate values are populated correctly.
1.1 Configuration Elements
1.1.1 Templates in OpenManage Enterprise
The configuration management and compliance operations provided in OpenManage Enterprise 3.0 provide
the capability to manage and control the configuration of the devices in a network. A template is a set of
system configuration settings referred to as attributes. A template may contain a small set of attributes for a
specific purpose, or all the attributes for a full system configuration. OpenManage Enterprise provides several
options for creating templates:
 Some pre-canned templates for specific purposes.
 A template can be created by importing a Server Configuration Profile (SCP) file into the OpenManage
Enterprise appliance. The SCP file can be captured from a server by using the 1x1 iDRAC GUI (Graphical
User Interface), or exported by OpenManage Essentials (OME), or OpenManage Enterprise.
 Most frequently, templates are created by getting the current system configuration from a server on the
network (referred to in OpenManage Enterprise as a “Reference Server”).
 Templates may also be cloned (copied) and edited. This applies to all templates, whether built-in,
imported, or created from a reference device.
1.1.2 Identities in OpenManage Enterprise
Some of the attributes which are typically included in a template are referred to as Identity attributes. Identity
attributes identify a device and distinguish it from all other devices on the network. Because identity attributes
must uniquely identify a device, it is imperative that each device has a unique network identity. Otherwise,
inter-device network communications cannot function properly.
Devices come with unique manufacturer-assigned Identity values pre-installed (such as a factory-assigned
MAC address). Those identities are fixed and never change. However, devices can assume a set of alternate
identity values, called a “virtual identity”, and function on the network by using that identity, as if the virtual
identity were its factory-installed identity. The use of virtual identity is the basis for Stateless operations.
OpenManage Enterprise provides management support for “virtual identities”. Just like factory-installed
identities, virtual identities must also be unique on the network. Using virtual identities enables OpenManage
Enterprise to support operations such as shifting (migrating) a full device configuration—including its virtual
identity—from one server to another. In other words, a virtual identity can be removed from one device and
assigned to a different device (for example, in case the original device stops working or requires
maintenance).