White Papers

Dell™ Lifecycle Controller 2 Web Services Interface Guide for Linux Version: 2.1.0
12
3 Overview
The remote interface guidelines provided in this document are illustrated by command line examples
of the WS-MAN protocol Web services APIs that expose the remote management capabilities of the Dell
Lifecycle Controller. The command line examples are from the Microsoft® Windows® and Linux
environments using WinRM
4
and WSMANCLI
5
respectively. The Lifecycle Controller remote management
capabilities are organized by management domain and documented in Dell CIM Profile specifications
2
.
The remote enablement feature for Lifecycle Controller 2.0 provides the following capabilities:
 Remotely get inventory of the BIOS, component firmware, and embedded software including
version information of both the installed as well as available cached versions
 Remote update of BIOS, component firmware, Diagnostic content, DRAC content, driver pack,
power supplies from remotely located Dell Update Packages or cached images located in the
Lifecycle Controller
 Remotely schedule and track the status of update tasks (jobs)
 Remotely manage the Part Replacement feature by allowing retrieving and setting auto update
and auto system inventory sync
 Enable re-initiation of Lifecycle Controller Auto-Discovery feature
 Enhancement of Operation System Deployment capabilities by supporting the downloading of
an ISO image to a Dell VFlash SD Card and booting to the ISO image on the VFlash SD Card
 NIC configuration enables the ability to get and set NIC attributes that are configurable using
NIC Option ROM or NIC UEFI HII.
 Remote RAID configuration allows users to remotely query and configure the Hardware Raid of
the system
 Multiple HW Inventory views allows users to remote query the inventory of Hardware
3.1 Format for WSMAN CLI Examples in Document
The examples of WinRM and WSMANCLI command line invocations in this document are formatted for
readability and often span multiple lines in the document. In actual use, scripted or hand-typed
invocations are contained on one line. The examples also use substitute values for the target iDRAC IP
address, username (with ExecuteServerCommand privilege), password and other site specific
information. Actual use of these examples would require using values for IP Address, username and
password, etc. that are valid. These values are represented in the examples as follows:
Target iDRAC IP address = $IPADDRESS
iDRAC Username = $USERNAME
iDRAC Password = $PASSWORD
Additional substitute values are used in some of the examples and are described in the specific
example.
The following example is typical of the formatting used in this document: