Users Guide

Table Of Contents
SSD Wear Threshold
iDRAC provides you the ability to configure thresholds of Remaining Rated Write Endurance for all SSD's and Available Spare of
NVMe PCIe SSDs.
When SSD Remaining Rated Write Endurance and NVMe PCIe SSD Available Spare values are less than the threshold, then
iDRAC logs this event in the LC log and depending on the alert type selection, iDRAC also performs Email alert, SNMP Trap,
IPMI Alert, Logging in Remote Syslog, WS Eventing and OS log.
iDRAC alerts the user when the SSD Remaining Rated Write Endurance goes below the set threshold, so that the system admin
can take a backup of SSD or replace it.
For only NVMe PCIe SSDs, iDRAC displays Available Spare and provide a threshold to warn. The Available Spare is not
available for SSDs which are connected behind PERC and HBA.
Configuring SSD Wear Threshold alert features using web interface
To configure Remaining Rated Write Endurance and Available Spare Alert Threshold using web interface:
1. In the iDRAC Web interface, go to Configuration > System Settings > Hardware Settings > SSD Wear Thresholds.
The SSD Wear Thresholds page is displayed.
2. Remaining Rated Write Endurance You can set the value between 1-99%. The default value is 10%.
Alert type for this feature is SSD Wear Write Endurance and security alert is Warning as a result of threshold event..
3. Available Spare Alert Threshold You can set the value between 1-99%. The default value is 10%.
Alert type for this feature is SSD Wear Available Spare and security alert is Warning as a result of threshold event.
Configuring SSD Wear Threshold alert features using RACADM
To configure Remaining Rated Write Endurance, use the command:
racadm set System.Storage.RemainingRatedWriteEnduranceAlertThreshold n
, where n= 1 to 99%.
To configure Available Spare Alert Threshold, use the command:
racadm System.Storage.AvailableSpareAlertThreshold n
, where n= 1 to 99%.
Configuring persistence policy settings
Using IO identity, you can configure policies specifying the system reset and power cycle behaviors that determine the
persistence or clearance of the virtual address, initiator, and storage target settings. Each individual persistence policy attribute
applies to all ports and partitions of all applicable devices in the system. The device behavior changes between auxiliary powered
devices and non-auxiliary powered devices.
NOTE:
The Persistence Policy feature may not work when set to default, if the VirtualAddressManagement attribute
is set to FlexAddress (not for MX platforms) or RemoteAssignedAddress (for MX platforms) mode on iDRAC and if
the FlexAddress or Remote-Assigned Address feature is disabled in CMC (not for MX platforms) or OME Modular (for
MX platforms), ensure that you set the VirtualAddressManagement attribute to Console mode in iDRAC or enable the
FlexAddress or Remote-Assigned Address feature in CMC or OME Modular.
You can configure the following persistence policies:
Virtual Address: Auxiliary powered devices
Virtual Address: Non-Auxiliary powered devices
Initiator
Storage target
Before applying the persistence policy, make sure to:
Inventory the network hardware at least once, that is, enabled Collect System Inventory On Restart.
Enable I/O Identity Optimization.
Inventorying, monitoring, and configuring network devices
215