The integrated Remote Access Controller (iDRAC) with Lifecycle Controller is responsible for system profile settings and out-of-band management. If issues occur regarding these topics, one of the first troubleshooting steps is to reset the IDRAC module. This procedure also works if the iDRAC's password is lost, it will restore default credentials.
Figure 1: I-button on PowerEdge R640 server
Figure 2: I-button on PowerEdge T620 server
For detailed information about the tool and its usage, please check the RACADM Command Line Interface Reference Guide (version 126.96.36.199. or later, only in English)
The command for resetting the iDRAC is
racadm racresetfor a soft reset (no saved settings will be changed) or
racadm racresetcfgfor a hard reset (IP/Account settings will be set back to factory default)
The Graphical User Interface (GUI) of the iDRAC provides an option to perform a soft reset:
The iDRAC Service Module (iSM) is a lightweight software application that can be installed on PowerEdge servers (12g and newer). iSM 2.3 (and newer) allows the administrator to hard reset the iDRAC remotely when iDRAC is unresponsive. Symptoms of a frozen iDRAC:
iDRAC Service Module provides the following interfaces through which iDRAC can be reset:
winrm i iDRACHardReset wmi/root/cimv2/dcim/DCIM_iSMService?InstanceID="iSMExportedFunctions"
winrm i iDRACHardReset wmi/root/cimv2/dcim/dcim_ismservice -u:"admin-username" -p:"password" -r:http://"remote-hostname or IP"/wsman -a:Basic -encoding:utf-8 -skipCACheck -skipCNCheck
iDRAC Service Module provides a PowerShell cmdlet to locally reset the iDRAC. To use PowerShell for resetting iDRAC:
Using Invoke-iDRACHardReset command from a remote PowerShell session.
On all iSM supported Linux OS-es; iSM provides a command which can be executed by logging into the OS using SSH or equivalent:
$ /opt/dell/srvadmin/iSM/bin/Invoke-iDRACHardReset -f
You have an option to specify the force (-f) option along with the command which does not wait for user confirmation and proceeds with the iDRAC reset action.
On RHEL-7 and SLES-11 SP2 versions; the IPMI driver may become unresponsive after the iDRAC reset. Administrators have to unload and reload the IPMI driver module. However, on RHEL-7.1 and higher versions; this IPMI issue has been addressed and a patch can be downloaded for the same from the RedHat site. The issue is observed on Linux kernel version prior to 3.15.
Steps to reload the IPMI driver in case kernel version is less than 3.15:
modprobe -r ipmi_si
On all iDRAC Service Module supported ESXi OS-es; iSM 2.3 and newer supports a CMPI method provider which shall enable customers to perform the iDRAC reset remotely using WinRM remote commands. Unlike Windows (except WMI) and Linux OS-es; ESXi does not prompt the user for a confirmation before resetting the iDRAC.
winrm i iDRACHardReset http://schemas.dell.com/wbem/wscim/1/cimschema/2/root/cimv2/dcim/DCIM_iSMService?__cimnamespace=root/cimv2/dcim+InstanceID=iSMEx portedFunctions -u:"root-username" -p:"password" -r:https://"Host-IP":443/wsman -a:basic -encoding:utf-8 -skipCNCheck -skipCACheck -skipRevocationcheck
The result of the operation is displayed as an integer value which indicates success or failure of the operation.
On ESXi 6.0 U1 and ESXi 6.0 U2 versions of ESXi; the IPMI driver may become unresponsive after the iDRAC reset. Users Hard Reset operation on certain VMware ESXi operating systems, the IPMI driver (ipmi_si_drv) may become unresponsive because of an existing issue in the IPMI driver. If the IPMI driver becomes unresponsive, reload the IPMI driver (ipmi_si_drv).
Steps to reload the ipmi_si_drv.
esxcfg-module -u ipmi_si_drv => unload ipmi_si_drv
esxcfg-module ipmi_si_drv => load ipmi_si_drv
|Need more help?|
|Find additional PowerEdge and PowerVault articles
Watch Part Replacement Videos for Enterprise products
Visit and ask for support in our Communities
Create an online support Request
Article ID: SLN305793
Last Date Modified: 12/02/2019 01:38 PM
Thank you for your feedback.