Setup Guide
Table Of Contents
- 1 Getting Started
- 2 Template
- 3 SCP Export
- 4 SCP Import
- 5 SCP Import Preview
- 6 iDRAC Configuration
- 7 LifecycleController
- 8 EventFilters
- 9 RAID / Storage Configuration and Operations
- 10 BIOS Configuration
- 11 NIC / FiberChannel / InfiniBand Configuration
- 12 SupportAssist Operations
- 13 RepositoryUpdates
- 14 iDRAC Direct (SCP via USB)
- 15 OS Deployment
- 16 Telemetry Operations
- 17 Secure Enterprise Key Management Operations
- 18 Auto Config – DHCP Provisioning
- 19 Troubleshooting
- 20 Additional Resources
Server Configuration Profiles: User’s Guide
9 Server Configuration Profiles: Reference Guide | 456
1.5 SCP Import
SCP Import is the process in which the XML or JSON template is applied to the server. Any configuration
settings available in the template will be applied. Any workflows (OSD and firmware update) triggered by the
template will also be performed during this operation. SCP Import may restart the host system multiple times
to apply all requests but will only restart the host if required. Results and any potential errors can be found in
either exporting the Lifecycle Controller Log (LCL) or configuration results for the SCP import job ID using CLI
interface.
More information about configuration results can be found in SCP Import / Preview Configuration Results
.
More information on SCP Import workflows and all available options can be found in SCP Import.
1.6 SCP Import Preview
SCP Import Preview allows validation of the XML or JSON template against the host server without applying
settings, firmware, or other workflows. Any errors detected during this operation will be logged to the LCL.
SCP Import Preview is useful for identifying issues with a template without needing to run a full SCP Import
operation or shutting down the host.
More information on SCP Import Preview can be found in SCP Import Preview
.
1.7 Jobs
SCP operations create a ‘Job’ for tracking purpose that will contain useful information about the current status
of the operation. The job is identified by a JID (Job Identifier) that will be returned when the SCP operation is
created.
All iDRAC jobs can be found in the iDRAC GUI under Maintenance > Job Queue or through any iDRAC
interface. See the racadm example below.
racadm jobqueue view -i JID_952589510966
---------------------------- JOB -------------------------
[Job ID=JID_952589510966]
Job Name=Configure: Import Server Configuration Profile
Status=Completed
Scheduled Start Time=[Not Applicable]
Expiration Time=[Not Applicable]
Actual Start Time=[Mon, 20 Jul 2020 10:29:11]
Actual Completion Time=[Mon, 20 Jul 2020 10:29:13]
Message=[SYS053: Successfully imported and applied Server Configuration Profile.]
Percent Complete=[100]
----------------------------------------------------------
Note: Only one SCP operation can be run at a time.
1.8 iDRAC Lifecycle Logs
The Lifecycle Logs contain a sequence of XML events posted by various iDRAC and host operations. SCP
operations will log all critical information to the LCL. SCP job start, progress, and completion states can be
reviewed in the LCL.