Concept Guide
Table Of Contents
- Dell Lifecycle Controller Remote Services v2.20.20.20 Quick Start Guide
- Introduction
- Why use Lifecycle Controller?
- Benefits of using iDRAC with Lifecycle Controller
- Key features
- What’s new in this release?
- Why use Lifecycle Controller Remote Services?
- Licensable features in Lifecycle Controller
- What is the Web Service API?
- Where can the Lifecycle Controller API be used from?
- Who can use the API?
- How is one-to-many management achieved?
- Other information that you may need
- Accessing documents from Dell support site
- Contacting Dell
- Remote Services Features
- Getting started with API collateral and links
- Integrating the Lifecycle Controller API
- Social media reference
- Terms and definitions

Out-of-band server performance monitoring
Using this feature, you can monitor the performance index of CPU, memory, and I/O. Intel ME supports
Compute Usage Per Second (CUPS) functionality for monitoring the performance. The monitoring is
independent of the OS and does not use CPU resources. The Intel ME displays a platform CUPS sensor
that provides the Computation, Memory and I/O resource utilization value in the form of a platform
“CUPS Index”. iDRAC monitors this CUPS index for overall system utilization and also the instant value of
CPU, Memory, and I/O utilization index.
NOTE: To use this feature, iDRAC enterprise license is required.
For more information about monitoring the out-of-band performance, see the Base Metrics and Sensors
profile document available at en.community.dell.com/techcenter/systems-management/w/wiki/
1906.dcim-library-profile.aspx.
Maintain
Using various Lifecycle Controller-Remote Services capabilities, you can maintain the health of a system
throughout its lifecycle. You can use features such as remote firmware management, part replacement,
server profile import or export, and provisioning server to maintain a system using Lifecycle Controller-
Remote Services.
Server configuration profiles — export or import
Lifecycle Controller-Remote Services can export or import a Server Configuration Profiles file. The export
operation collects the configuration information for BIOS, iDRAC, RAID, NIC, FC-HBA, System, and
Lifecycle Controller and stores it in a single file that is copied to a network share. The Import operation
imports the file from a network share, and applies the previously saved or updated configurations
contained in the file to a system. For more information, see Server Cloning with Server Configuration
Profiles and Creating and Managing Server Configuration Profiles documents available at
en.community.dell.com/techcenter/systems-management/w/wiki/1906.aspx.
Exceptions while importing server profile
On certain Dell devices, successful application of a server configuration profile is possible only after two
imports. The first import of the profile enables hidden devices which are then configured with a second
import.
The devices that require two imports are:
• Enabling RAID mode on storage controllers — PERC S110 and PERC S130 require two imports — one
to set the embedded SATA controller to RAID mode and the second to configure the RAID controller
for operations such as creating a virtual disk.
Example:
If the EmbSata BIOS attribute on the import system is not set to RAIDMode, then the first import must
contain the following:
<Component FQDD="BIOS.Setup.1-1">
<Attribute Name="EmbSata">RaidMode</Attribute>
</Component>
19