Users Guide

Interface or Protocol Description
RACADM Use this command-line utility to perform iDRAC and server management. You can use RACADM locally and
remotely.
Local RACADM command-line interface runs on the managed systems that have Server Administrator
installed. Local RACADM communicates with iDRAC through its in-band IPMI host interface. Since it is
installed on the local managed system, users are required to log in to the operating system to run this
utility. A user must have a full administrator privilege or be a root user to use this utility.
Remote RACADM is a client utility that runs on a management station. It uses the out-of-band network
interface to run RACADM commands on the managed system and uses the HTTPs channel. The –r
option runs the RACADM command over a network.
Firmware RACADM is accessible by logging in to iDRAC using SSH or telnet. You can run the firmware
RACADM commands without specifying the iDRAC IP, user name, or password.
You do not have to specify the iDRAC IP, user name, or password to run the firmware RACADM
commands. After you enter the RACADM prompt, you can directly run the commands without the
racadm prefix.
iDRAC RESTful API and
Redfish
The Redfish Scalable Platforms Management API is a standard defined by the Distributed Management Task
Force (DMTF). Redfish is a next-generation systems management interface standard, which enables
scalable, secure, and open server management. It is a new interface that uses RESTful interface semantics
to access data that is defined in model format to perform out-of-band systems management. It is suitable for
a wide range of servers ranging from stand-alone servers to rack mount and bladed environments and for
large scale cloud environments.
Redfish provides the following benefits over existing server management methods:
Increased simplicity and usability
High data security
Programmable interface that can be easily scripted
Follows widely-used standards
For more information, see the iDRAC Redfish API Guide available at www.dell.com/idracmanuals.
WSMan
The LC-Remote Service is based on the WSMan protocol to do one-to-many systems management tasks.
You must use WSMan client such as WinRM client (Windows) or the OpenWSMan client (Linux) to use the
LC-Remote Services functionality. You can also use Power Shell and Python to script to the WSMan
interface.
Web Services for Management (WSMan) are a Simple Object Access Protocol (SOAP)–based protocol used
for systems management. iDRAC uses WSMan to convey Distributed Management Task Force (DMTF)
Common Information Model (CIM)–based management information. The CIM information defines the
semantics and information types that can be modified in a managed system. The data available through
WSMan is provided by iDRAC instrumentation interface mapped to the DMTF profiles and extension profiles.
For more information, see the following:
Lifecycle Controller Remote Services Quick Start Guide available at www.dell.com/idracmanuals .
Lifecycle Controller page on Dell EMC knowledge base site — www.dell.com/support/article/sln311809/
MOFs and Profiles — www.dell.com/support/article/sln311039/
DTMF website — dmtf.org/standards/profiles/
SSH Use SSH to run RACADM and SMCLP commands. It provides the same capabilities as the Telnet console
using an encrypted transport layer for higher security. The SSH service is enabled by default on iDRAC. The
SSH service can be disabled in iDRAC. iDRAC only supports SSH version 2 with the RSA host key algorithm.
A unique 1024-bit RSA host key is generated when you power-up iDRAC for the first time.
Telnet Use Telnet to access iDRAC where you can run RACADM and SMCLP commands. For details about
RACADM, see iDRAC RACADM CLI Guide available at www.dell.com/idracmanuals. For details about
SMCLP, see Using SMCLP.
NOTE: Telnet is not a secure protocol and is disabled by default. Telnet transmits all data,
including passwords in plain text. When transmitting sensitive information, use the SSH
interface.
VMCLI Use the Virtual Media Command Line Interface (VMCLI) to access a remote media through the management
station and deploy operating systems on multiple managed systems.
Overview 27