• Integrate with SupportAssist Collection. This is applicable only if iDRAC Service Module version 2.0 or later is installed. For moreinformation, see Generating SupportAssist Collection.• Prepare to Remove NVMe PCIe SSD. For more information, see Idracug_preparing to remove nvme pcie ssd.NOTE: The features such as Windows Management Instrumentation Providers, Prepare to Remove NVMe PCIe SDDthrough iDRAC, Automating SupportAssist Collection OS collection are supported only on Dell PowerEdge servers withminimum firmware version 2.00.00.00 or later.Redfish profile support for network attributesiDRAC Service Module v2.3 or later provides additional network attributes to iDRAC, which can be obtained through the RESTclients from iDRAC. For more details, see iDRAC Redfish profile support.Operating system informationThe OpenManage Server Administrator currently shares operating system information and host name with iDRAC. The iDRACService Module provides similar information such as OS name, OS version, and Fully Qualified Domain Name (FQDN) with iDRAC.By default, this monitoring feature is enabled. It is not disabled if OpenManage Server Administrator is installed on the host OS.iDRAC Service Module version 2.0 or later has amended the operating system information feature with the OS network interfaceMonitoring. When iDRAC Service Module version 2.0 or later is used with iDRAC 2.00.00.00, it starts monitoring the operatingsystem network interfaces. You can view this information using iDRAC web interface, RACADM, or WSMAN. For more information,see Viewing network interfaces available on host os.When iDRAC Service Module version 2.0 or later is used with iDRAC version lower than 2.00.00.00, the OS information featuredoes not provide OS network interface monitoring.Replicate Lifecycle logs to OS logYou can replicate the Lifecycle Controller Logs to the OS logs from the time when the feature is enabled in iDRAC. This is similar tothe System Event Log (SEL) replication performed by OpenManage Server Administrator. All events that have the OS Log optionselected as the target (in the Alerts page, or in the equivalent RACADM or WSMAN interfaces) are replicated in the OS log usingthe iDRAC Service Module. The default set of logs to be included in the OS logs is the same as configured for SNMP alerts or traps.iDRAC Service Module also logs the events that have occurred when the operating system is not functioning. The OS loggingperformed by iDRAC Service Module follows the IETF syslog standards for Linux-based operating systems.NOTE: Starting iDRAC Service Module version 2.1, the Lifecycle Controller Logs replication location in the Windows OSlogs can be configured using the iDRAC Service Module installer. You can configure the location while installing iDRACService Module or modifying the iDRAC Service Module installer.If OpenManage Server Administrator is installed, this monitoring feature is disabled to avoid duplicate SEL entries in the OS log.NOTE: On Microsoft Windows, if iSM events get logged under System logs instead of Application logs, restart theWindows Event Log service or restart the host OS.Automatic system recovery optionsThe Automatic system recovery feature is a hardware-based timer. If a hardware failure occurs, the Health Monitor may not becalled, but the server is reset as if the power switch was activated. ASR is implemented using a "heartbeat" timer that continuouslycounts down. The Health Monitor frequently reloads the counter to prevent it from counting down to zero. If the ASR counts downto zero, it is assumed that the operating system has locked up and the system automatically attempts to reboot.You can perform automatic system recovery operations such as reboot, power cycle, or power off the server after a specified timeinterval. This feature is enabled only if the operating system watchdog timer is disabled. If OpenManage Server Administrator isinstalled, this monitoring feature is disabled to avoid duplicate watchdog timers.261
