Reference Guide
Table Of Contents
- Dell Lifecycle Controller Remote Services v2.40.40.40 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 are Redfish and the Web Service APIs?
- 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 support content from the Dell EMC support site
- Contacting Dell
- Remote Services Features
- Deployment and configuration
- Monitor
- Maintain
- Job management
- Getting started with API collateral and links
- Integrating the Lifecycle Controller API
- Social media reference
- Terms and definitions
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 local file or a network share. The Import operation imports the file from a local file or a network share, and
applies the previously saved or updated configurations contained in the file to a system.
Import and export can be performed using the WS-MAN or Redfish interfaces.
For more information, see Server Cloning with Server Configuration Profiles and Creating and Managing Server Configuration
Profiles documents available at www.delltechcenter.com/systemsmanagement.
Exceptions while importing server profile
On certain Dell devices, successful application of a server configuration profile requires two imports. The first import of the
profile enables hidden devices that are then configured with a second import.
Two imports are required while performing following actions:
● 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>
The second server import is to apply the configuration on the PERC controller:
<Component FQDD="RAID.Embedded.1-1">
<Attribute Name="RAIDresetConfig">False</Attribute>
<Attribute Name="RAIDforeignConfig">Ignore</Attribute>
<Component FQDD="Disk.Virtual.262145:RAID.Embedded.1-1">
<Attribute Name="RAIDaction">Create</Attribute>
<Attribute Name="Name">Virtual Disk 1</Attribute>
<Attribute Name="Size">0</Attribute>
<Attribute Name="StripeSize">128</Attribute>
<Attribute Name="SpanDepth">1</Attribute>
<Attribute Name="SpanLength">2</Attribute>
<Attribute Name="RAIDTypes">RAID 0</Attribute>
<Attribute Name="IncludedPhysicalDiskID">Disk.Direct.0-0:RAID.Embedded.1-1</
Attribute>
<Attribute Name="IncludedPhysicalDiskID">Disk.Direct.1-1:RAID.Embedded.1-1</
Attribute>
</Component>
<Component FQDD="Disk.Direct.0-0:RAID.Embedded.1-1">
<Attribute Name="RAIDPDState">Ready</Attribute>
</Component>
<Component FQDD="Disk.Direct.1-1:RAID.Embedded.1-1">
<Component FQDD="Disk.Direct.1-1:RAID.Embedded.1-1">
<Attribute Name="RAIDPDState">Ready</Attribute>
</Component>
</Component>
● Enabling PCI slots — PCI slots in the system that are disabled in the BIOS require two imports – one to enable the slot and
another to configure the card in the slot.
Remote Services Features
17