The integrated Dell 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 restores default credentials.
For PowerEdge servers using iDRAC7 and upwards, a small button that is marked "i" (Figures 1 & 2) is on the front panel of many tower and rack systems. In order to reboot the iDRAC, press the button for at least 30 seconds. Stop pressing the button when the cooling fans start spinning at full speed and the front LCD (if given) is turning off. Now the iDRAC restarts without changing any saved settings. It takes a few minutes until the remote controller works as before, but the system keeps working during the whole process.
Figure 1: I-button on PowerEdge R640 server
Figure 2: I-button on PowerEdge T620 server
The Dell RACADM (Remote Access Controller Admin) utility is a command-line tool that allows for remote or local management of Dell Servers using the iDRAC. RACADM commands can be run remotely from a management station or locally on the managed system.
For detailed information about the tool and its usage, check the RACADM Command Line Interface Reference Guide (version 184.108.40.206. or later, only in English)
The command for resetting the iDRAC is:
racadm racresetfor a soft reset (no saved settings are changed) or
racadm racresetcfgfor a hard reset (IP and Account settings are reset back to factory default).
The Graphical User Interface (GUI) of the iDRAC provides an option to perform a soft reset:
1. Click the Maintenance tab.
2. Select Diagnostics.
3. Click Reset iDRAC.
Figure 3: Reset iDRAC option in iDRAC9
It is also possible to input iDRAC command lines directly from this screen.
iDRAC8 and previous
Figure 4: Reset iDRAC option
The iDRAC Service Module (iSM) is a lightweight software application that can be installed on PowerEdge servers running iDRAC7 and above. iSM 2.3 (and newer) allows the administrator to hard reset the iDRAC remotely when iDRAC is unresponsive. Symptoms of an iDRAC which has stopped responding:
iDRAC Service Module provides the following interfaces through which iDRAC can be reset from within a Windows Operating System:
WMI Method - This can be invoked either locally or remotely using Windows Management Instrumentation (WMI) commands
To reset the iDRAC using WMI commands, the procedure is as follows:
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
PowerShell Method - This can be invoked either locally or remotely using PowerShell commands
To reset the iDRAC using local PowerShell commands, the procedure is as follows:
iDRAC Service Module also provides a PowerShell cmdlet to locally reset the iDRAC. To use PowerShell for resetting iDRAC:
Using Invoke-iDRACHardReset command from a remote PowerShell session.
Program menu shortcut Method - This can be run by logging into the operating system using remote desktop session and selecting the iDRAC reset option from the program menu
iDRAC Service Module also provides a shortcut in the program menu of the Windows operating system. Select this option to reset iDRAC.
On all iSM supported Linux OS-es; iSM provides a command which can be run by logging into the operating system using SSH or equivalent:
$ /opt/dell/srvadmin/iSM/bin/Invoke-iDRACHardReset -f
There is an option to specify the force (-f) option along with the command. This 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 versions before 3.15.
Steps to reload the IPMI driver in case kernel version is less than 3.15:
modprobe -r ipmi_siIf the removal fails, then all applications (such as iDRAC Service Module and OpenManage Server Administrator) using the ipmi_si must be stopped. Then the operation should be retried.
On all iDRAC Service Module supported ESXi OS-es; iSM 2.3 and newer supports a CMPI method provider. This enables 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: SLN305793Last Date Modified: 07/24/2020 11:42 AM