Users Guide

NOTE: VMware ESXi operating system does not prompt for confirmation before resetting the
iDRAC.
NOTE: Due to limitations on the VMware ESXi operating system, iDRAC connectivity is not
restored completely after the reset. Ensure that you manually reset iDRAC. For more
information, see the “Remote iDRAC Hard Reset” in this document.
Error Handling
Table 33. Error Handling
Result Description
0 Success
1 Unsupported BIOS version for iDRAC reset
2 Unsupported platform
3 Access denied
4 iDRAC reset failed
In-band Support for iDRAC SNMP Alerts
By using iDRAC Service Module v2.3, you can receive SNMP alerts from the host operating system, which
is similar to the alerts that are generated by iDRAC.
You can also monitor the iDRAC SNMP alerts without configuring the iDRAC and manage the server
remotely by configuring the SNMP traps and destination on the host OS. In iDRAC Service Module v2.3 or
later, this feature converts all the Lifecycle logs replicated in the OS logs into SNMP traps.
NOTE: This feature is active only if the Lifecycle Logs replication feature is enabled.
NOTE: On Linux operating systems, this feature requires a master or OS SNMP enabled with SNMP
multiplexing (SMUX) protocol.
By default, this feature is disabled. Though the In-band SNMP alerting mechanism can coexist along with
iDRAC SNMP alerting mechanism, the recorded logs may have redundant SNMP alerts from both the
sources. It is recommended to either use the in-band or out-of-band option, instead of using both.
Command usage
This section provides the command usages for Windows, Linux, and ESXi operating systems.
• Windows operating system
– Using the local Windows Management Instrumentation (WMI):
winrm i EnableInBandSNMPTraps
wmi/root/cimv2/dcim/DCIM_iSMService?InstanceID="iSMExportedFunctions"
@{state="[0/1]"}
– Using the remote WMI interface:
winrm i EnableInBandSNMPTraps wmi/root/cimv2/dcim/DCIM_iSMService?
InstanceID="iSMExportedFunctions" @{state="[0/1]"}
314