Users Guide

NOTE: The OS and Application Data collection on ESXi is supported only by yx4x and later servers.
Anonymous Collection of Report
Starting from iDRAC Service Module version 3.1, you can perform SupportAssist Collection/Upload without completing the registration
process. Until iSM 3.0.2, the registration was a prerequisite to perform SupportAssist Collection.
The supported iDRAC firmware for the anonymous collection is iDRAC 3.15.15.15 in the yx4x and yx5x servers and 2.60.60.60 in the yx3x
servers.
NOTE: You can perform Anonymous SupportAssist Collection upload using blank username or password in proxy
environment on the yx3x servers.
Correlation of software events to hardware failures for Microsoft SDS
Starting iSM 3.5, the event logs for hardware storage pool alerts or events will be monitored by iSM with Server Storage correlation
feature. Currently the server storage subsystem is monitored when Dell EMC storage controllers are used in RAID mode. But in Storage
Spaces(SS) or Storage Space Direct(S2D), the server storage subsystem is monitored in a pass-thru mode or the SATA chipset is used to
create the storage pool. With this feature, the hardware defined alerts covered by Lifecycle log and software defined alerts covered by OS
logs are merged and the alerts are registered in the iDRAC Lifecycle logs.
This feature is installed with the iDRAC Service Module package and will be enabled by default. User can change the preferences in the
iDRAC settings. As part of the monitoring, iSM will audit the logs for potential failures and warnings. iSM will embed the SS correlation
events on the Host to an equivalent LC event. The SSLCMAP should only reach the Lifecycle logs and SupportAssist alert. User cannot
configure the SSLCMAP to any other alert destination in iDRAC .
The following are the pre-requisites for S2D log collection:
• SS event correlation feature needs to be enabled in the service module page in iDRAC UI.
• PII filter needs to be disabled in the service module page in iDRAC UI
The following table describes the Windows Event Message mapped under LC logs monitored under S2D event correlation:
Windows Event Source - SourceID
Windows Event Message Mapped on iDRAC LC Log
StorageSpaces - Drivers - 100 Physical drive %1 failed to read the
configuration or returned corrupt data for
storage pool %2. As a result the in-memory
configuration might not be the most recent
copy of configuration. Return Code: %3
MessageID : SDS0001
StorageSpaces - Drivers - 102 Majority 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
the drive is still usable, then resetting the
drive health by using command line or GUI
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 IO 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
iDRAC Service Module monitoring features 33