Users Guide
Table Of Contents
- Dell EMC iDRAC Service Module 4.0.1 User’s Guide
- Contents
- 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 the iDRAC Service Module on VMware ESXi
- Installing iDRAC Service Module on supported Linux operating systems
- Installing iDRAC Service Module when System Configuration Lock Down Mode is enabled in iDRAC
- Configuring iDRAC Servcie Module
- Security configurations and compatibility
- iSM monitoring 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
- 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-BMC Passthru
- Frequently asked questions
- Linux and Ubuntu installer packages
- Resources and support
- Contacting Dell EMC
Table 15. Windows Event Message mapped under LC logs monitored under S2D event correlation
Windows event source—SourceID Windows event message Mapped on iDRAC LC log
the most recent copy of configuration.
Return code: %3
StorageSpaces—drivers—102 Most of the physical drives of storage
pool %1 failed a configuration update,
which caused the pool to go into a failed
state. Return code: %2
MessageID : SDS0002
StorageSpaces—drivers—103 The capacity consumption of the storage
pool %1 has exceeded the threshold limit
set on the pool. Return code: %2
MessageID : SDS0003
StorageSpaces—drivers—200 Windows was unable to read the drive
header for physical drive %1. If you
know that the drive is still usable,
then resetting the drive health by using
command line or UI may clear this failure
condition and enable you to reassign the
drive to its storage pool. Return code:
%2
MessageID : SDS0004
StorageSpaces—drivers—203 An I/O failure has occurred on physical
drive %1. Return code: %2
MessageID : SDS0005
StorageSpaces—drivers—300 Physical drive %1 failed to read the
configuration or returned corrupt data
for storage space %2. As a result the
in-memory configuration may not be
the most recent copy of configuration.
Return code: %3
MessageID : SDS0006
StorageSpaces—drivers—301 All pool drives failed to read the
configuration or returned corrupt data
for storage space %1. As a result the
storage space will not attach. Return
code: %2
MessageID : SDS0007
StorageSpaces—drivers—302 Most of the pool drives hosting space
metadata for storage space %1 failed a
space metadata update, which caused
the storage pool to go to failed state.
Return code: %2
MessageID : SDS0008
StorageSpaces—drivers—303 Drives hosting data for storage space
have failed or are missing. As a result,
no copy of data is available. Return code:
%2
MessageID : SDS0009
StorageSpaces—drivers—304 One or more drives hosting data for
storage space %1 have failed or are
missing. As a result, at least one copy of
data is not available. However, at least
one copy of data is still available. Return
code: %2
MessageID : SDS0010
StorageSpaces—drivers—306 The attempt to map, or to allocate
more storage for, the storage space %1
has failed. This is because there was
a write failure that is involved in the
updating the storage space metadata.
Return code: %2
MessageID : SDS0011
34 iSM monitoring features