- Notes, cautions, and warnings
- Introduction
- Preinstallation setup
- Installing iDRAC Service Module
- Initial installation of iDRAC Service Module through iDRAC Enterprise or Datacenter or iDRAC Express on Microsoft Windows and Linux
- Installing iDRAC Service Module on Microsoft Windows operating systems
- Silent installation of iDRAC Service Module on Microsoft Windows
- Modifying iDRAC Service Module components on Microsoft Windows operating systems
- Repairing iDRAC Service Module running on Microsoft Windows operating systems
- Uninstalling iDRAC Service Module running on Microsoft Windows operating systems
- Installing iDRAC Service Module on VMware ESXi
- Preinstallation requirements for VMware ESXi
- Installing iDRAC Service Module on VMware ESXi using CLI
- Installing iDRAC Service Module using the vSphere CLI
- Installing iDRAC Service Module using VMware Update Manager
- Upgrading iDRAC Service Module on VMware ESXi
- Installing iDRAC Service Module using vSphere Lifecycle Manager in vSphere Client
- Using the Power CLI
- Uninstalling iDRAC Service Module on VMware ESXi
- Installing iDRAC Service Module on supported Linux operating systems
- Installing iDRAC Service Module when System Configuration Lockdown mode is enabled in iDRAC
- Configuring iDRAC Service Module
- Security configurations and compatibility
- Features
- S.M.A.R.T monitoring
- Operating system information
- Lifecycle Controller log replication into operating system
- Automatic system recovery
- Windows Management Instrumentation Providers
- Prepare to remove a NVMe PCIe SSD device
- Remote iDRAC hard reset
- iDRAC access via Host OS
- Accessing iDRAC via GUI, WS-Man, Redfish, and Remote RACADM
- In-Band support for iDRAC SNMP alerts
- Mapping iDRAC Lifecycle Logs to OMSA and OMSS SNMP alerts
- Enable WS-Man remotely
- Autoupdating iSM
- FullPowerCycle
- SupportAssist on the box
- Configuring the In-Band SNMP Get feature—Linux
- Configuring the In-Band SNMP Get feature—Windows
- iDRAC GUI Launcher
- Single sign-on to iDRAC UI from host operating system administrators desktop
- IPv6 communication between iSM and iDRAC over OS to iDRAC Pass-through
- Isolation of OS to iDRAC Pass-through Independent feature
- Software RAID
- Frequently asked questions
- Linux and Ubuntu installer packages
- Resources and support
- Contacting Dell EMC
Dell EMC iDRAC Service Module 4.2.0.0 User’s Guide
Remote iDRAC hard reset
iDRAC may become unresponsive for various reasons. iSM can fully reset an unresponsive iDRAC8 or iDRAC9 controller by temporarily removing power to the iDRAC controller without affecting operating system production. This feature can only be disabled from the iSM page in iDRAC using the iDRAC interfaces.
To reset iDRAC, use the following Windows PowerShell or Linux shell command:
./Invoke-iDRACHardReset
NOTE The shell command is supported only on VMware ESXi 7.x.
In all ESXi operating systems, you can perform the iDRAC reset remotely using the following WinRM remote command:
winrm i iDRACHardReset http://schemas.dell.com/wbem/wscim/1/cimschema/2/root/cimv2/dcim/DCIM_iSMService?__cimnamespace=root/cimv2/dcim+InstanceID=iSMExportedFunctions -u:"root-username" -p:"password" -r:https://"Host-IP":443/wsman -a:basic -encoding:utf-8 -skipCNCheck -skipCACheck -skipRevocationcheck
NOTE The remote iDRAC hard reset feature only works with iDRAC8 on the PowerEdge yx3x or later servers and if logged into the operating system as an administrator.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\