iDRAC9 Version 7.00.39.00 Release Notes

Important notes

Authentication

1. Ensure that you use digest authentication for HTTP/HTTPs share for all iDRAC and LC features, basic authentication is no longer supported and is blocked by iDRAC due to security risks.
2. If an Active Directory user is configured for SSO with RSA token authentication, then the RSA token is bypassed and user can log in directly. This is because RSA is not applicable for AD-SSO, Active Directory smart card, and local user smart card logins.

BIOS and UEFI

1. While performing BIOS Recovery operation all iDRAC resets are blocked and if a iDRAC reset to default operation is performed, it causes iDRAC to be set to factory defaults and iDRAC will not reset. The condition is expected and a manual iDRAC reset is recommended.
2. If the BIOS date and time are set incorrectly while resetting iDRAC to default settings, the iDRAC's IP address may be lost. Reset iDRAC or AC power cycling the server to recover iDRAC IP.

iDRAC firmware

1. In iDRAC, attaching a folder that is in an NFS share hosted by a Linux-based operating system is not supported.
2. In Lifecycle (LC) interface, It is recommended to avoid performing any operations on media that is mounted as RFS through ¡DRAC GUI/RACADM/Redfish.
3. Updating iDRAC firmware to version 6.xx or later changes the static IPv4 or IPv6 DNS settings. Ensure that you reconfigure the network settings after the upgrade is complete.
4. Firmware update using an FTP fails if the HTTP proxy is used without any authentication. Ensure that you change the proxy configuration to allow the CONNECT method to use non-SSL ports. For example, while using a squid proxy, remove the line "http_access deny CONNECT !SSL_ports" that restricts from using the CONNECT method on non-SSL ports.
5. To apply a firmware update that is scheduled and awaiting a host reboot, ensure that you perform a cold reboot instead of a warm reboot.
6. For catalog updates through downloads.dell.com, adding catalog location or name is not required. Adding downloads.dell.com as HTTPS Address enables iDRAC to find the appropriate catalog file.
7. If Lifecycle controller logs display RED057 message during a component update, then run the command systemerase Icdata through RACADM interface and then retry the operation.
8. While performing a PSU firmware update through the host OS in the 15 th or later Generations of PowerEdge servers, ensure that you perform a cold reboot to apply the update.
9. During OS deployment through SCP, if the SCP configuration file includes the attribute "OSD.1#AnswerFileName" then a virtual USB device OEMDRV is attached to the server that contains the file with responses for an unattended OS installation. This device will be available for the duration as specified in the optional attribute "OSD.1#ExposeDuration" in the template and if the attribute is not specified, it remains attached for about 18 hours. After the OS installation is complete, detaching the ISO and the driver pack also unmounts the OEMDRV device.
10. Before updating PSU firmware on PowerEdge C series systems, ensure that all the blades are powered off in the chassis first. If any of the blades are powered on, the PSU firmware update process may fail, and Lifecycle Controller (LC) logs report the failure.
11. Adding an iDRAC system with firmware version 4.4x or later to a group manager of systems with iDRAC versions earlier than 3.xx, 4.0x, 4.1x, 4.2x, or 4.3x is not supported. Ensure that all the systems have the latest iDRAC firmware version 4.4x or any later versions.
12. While performing a firmware update or rollback through LifeCycle controller(LC) GUI, the component information displayed in the table listing the available updates may be truncated if it exceeds the table column or row width.
13. After an iDRAC reboot, the iDRAC GUI may take some time to initialize causing some information to be unavailable or some options to be disabled.
14. While generating Server Configuration Profile templates using the Clone or Replace option, ensure that the template is updated using a password that complies with the restrictions set on the target iDRAC, or use the 'Include Password Hash' option.
15. After updating the iDRAC license to Data Center license, ensure that you reboot the iDRAC for Idle server detection feature related attributes to function.
16. In LifeCycle Controller GUI, use the mouse to browse files or folders. Browsing files using keyboard is not supported.
17. iDRAC GUI search output points to a GUI page where the search keywords are missing within the page. These are typical false positives like any other search engine that may be ignored.
18. If a single DUP is used to update firmware for multiple devices, and if any update fails then the firmware for the subsequent cards may display an incorrect version. Update the firmware for all the failed devices again.
19. If you get an error while performing SupportAssist collection through RACADM using HTTPS share, use the following commands to perform the collection:
    a. Racadm SupportAssist collect.
    racadm supportassist collect -t Sysinfo
    b. Racadm SupportAssist exportlastcollection
    racadm supportassist exportlastcollection -1 <https> -u <username> -p <password>

Monitoring and alerting

1. After a system cold reboot, the corresponding Unlock event for Boss Drives getting unlocked are not generated in iDRAC Lifecycle (LC) Logs. To verify if the BOSS drives are successfully unlocked and secured, see the BOSS Drive Secure State in the iDRAC GUI or run the RACADM command racadm storage get pdisks -0.
2. Operating system crash capture and last crash screen are not supported for all Linux based operating systems such as RHEL, SLES, Ubuntu, ESXI, and Cent operating systems.
3. In certain cases, Group Manager Jobs view may not show a detailed error message for a member iDRAC job. For more information about the failure, review the job execution details in the Lifecycle Logs of the member iDRAC by using the web interface (Maintenance > Lifecycle Log) or by using the RACADM command racadm lclog view.
4. PCIe SSDs in NVMe RAID mode may not display the updated state due to predicted failure. To update RAID-related information, ensure that a CSIOR is performed.
5. If the LCD display is blank, press any one of the three LCD buttons to turn on the LCD before inserting a USB storage device.
6. If Flex Address is enabled on Chassis Management Controllers (CMC), iDRAC and LC do not display the same MAC addresses. To view the chassis-assigned MAC address, use the iDRAC web interface or the CMC web interface.
7. The inventory displayed in LC UI may not be the same as that of any iDRAC interfaces. To get the updated inventory, run the CSIOR, wait for 2 minutes, reboot the host, and then check the inventory in LC UI.
8. In certain cases, in Group Manager Jobs view, the completion percentage for a job may be displayed incorrectly (>100%) for a job in progress. This is a temporary condition and does not affect how Group Manager jobs are performed. When the job is completed, Group Manager Jobs view displays Completed successfully or Completed with errors.
9. While running host stress test, if the system ID/Health LED turns off from blue, then press the ID button for a second and press it again to turn on the LED.
10. When setting the iDRAC Service Module (iSM) monitoring attributes from the web interface, if the BIOS watchdog timer is enabled, an error may be displayed but the attributes are set. To avoid the error, disable the BIOS watchdog timer or disable the iSM Auto System Recovery and then apply the attributes.
11. iDRAC supports iSM version 3.4.1 and above.
12. Redfish or other iDRAC interfaces only display the FQDD of a faulty part, use the LCLogs for detailed information.

Networking and IO

1. While performing any network operation, LC may go into an infinite loop if there are network glitches, leaks, or packet loss. Restart LC and retry the operation with the correct NFS share name details.
2. When multiple NICs are configured for the first time, and the first configured NIC port stops responding or shuts down, then any operation over network from Lifecycle Controller GUI using FQDN may fail from all configured NICs. Before trying any operation over network in LC GUI, ensure that you reboot the host when the first configured NIC goes down.
3. If NPAR is enabled, LC might show unexpected behavior when configuring network settings. Disable NPAR and execute the network setting configurations. To disable the NPAR option, go to System Setup > Device Setting.
4. When NPAR is enabled, the port numbers displayed on the LC Network Settings page (Settings > Network Settings) do not match the port numbers displayed on the Device Settings page (System Setup > Advanced Hardware Configuration > Device Settings).
5. When Virtualization Mode is set to NPAR for network adapters that support the partitioning feature, PartitionState attribute can only be used for checking the state of partitions created for base partition in WSMan enumeration. You can see the states of all the partitions by pressing F2 during POST and going to Device Setting.
6. The process of retrieving IPv6 address from the DHCP server with VLAN connection takes a few minutes. Wait for a few minutes and check the Network Settings page to view the assigned IPv6 address.
7. Network operations such as Update, Export, or Import may take more time than expected. The delay may occur because the source or destination share is not reachable or does not exist, or due to other network issues.
8. LC does not support SOCK4 proxy with credentials.
9. LC UI supports share names and file paths that are up to 256 characters long. However, the protocol you use may only allow shorter values for these fields.
10. Because of internal UEFI network stack protocol implementation, there may be a delay while opening the LC UI Network Settings page or while applying the network setting.
11. Before performing any network operations, verify that the network is configured with the network cable connected. In some scenarios, a warning message may not be displayed but the operation may fail. Following are some examples that may lead to failure:
    • Static IP is configured without the network cable being connected.
    • Network cable is disconnected.
    • After a Repurpose and Retire operation is performed.
    • Network is configured with the network cable connected but the network card is replaced later.
12. Any changes to the network settings in iDRAC take effect after 30 seconds. Any automation or user verification needs to wait for 30 seconds before verifying the new settings. iDRAC returns the old active value until the new values take effect. Any DHCP settings may take more time (>30 seconds) depending on the network environment.
13. When trying to save network details using the Network Configuration page of LC UI, the following error message may be displayed: Unable to save the IPvX network settings, where x is the version of IP (IPv4 or IPv6). The following could be one reason for this error:
    On the Network Settings page of Lifecycle Controller GUI, the IP Address Source for both IPv4 and IPv6 is either DHCP or Static and DHCP is selected by default. So, even if you want to use only one version of IP address, LC tries to validate both versions, and displays an error if the network details for the unintended version cannot be validated.
    If the error does not apply to the IP version you are using, click OK to close the error message. All the other settings that you configured are saved. You can either click Cancel or Back to navigate away from the Network Settings page.
14. If the Gateway IP is not configured in a network, the network settings and operations in LC UI may show some unexpected behavior.

OS deployment

1. Operating system installation fails when the OS media volume name (label) is blank. Recommendation is to add a valid volume name for OS media (USB drive, DVD, and so on) before starting the OS installation.
2. While installing an operating system, a media verification warning message may be displayed. This has no impact on the installation, to proceed, click Yes.
3. Windows operating system deployment may intermittently fail with the following error message:
   A required CD/DVD drive device driver is missing. If you have a driver floppy disk, CD, DVD, or USB drive, please insert it now.
   Reboot to LC and retry until the operating system is successfully deployed.
4. Deployment of Windows Server operating systems (OS) using LC may fail with one of the following messages:
   • Windows installation cannot continue because a required driver could not be installed
   • Product key required
   • Windows cannot find the software license terms
   This issue occurs when the Windows setup copies the driver to the scratch space (X: drive) and the scratch space becomes full. To resolve this issue, do any of the following:
   • Remove all the installed add-on devices before starting the OS installation. After the OS installation is complete, connect the add-on devices, and manually install the remaining drivers using Dell Update Packages (DUPs).
   • To avoid physically removing the hardware, disable the PCIe slots in the BIOS.
   • Increase scratch space size beyond 32 MB using DISM set-scratchspace command when creating customized deployment. For more details, see Microsoft's documentation.
5. LC may display multiple drive names for some CDs or DVDs, such as the ones containing operating systems.
6. If the operating system (OS) selected for installation and the OS on the media used are different, LC displays a warning message. However, while installing Windows OS, the warning message is displayed only when the bit count (x86 or x64) of the OS does not match. For example, if Windows Server 2008 x64 is selected for installation and Windows Server 2008 x86 media is used, the warning is displayed.

Security

1. Cryptographic Erase operation is not supported for hot-plugged NVMe disks. Cold reboot (power cycle) the server before starting the operation. If the operation continues to fail, ensure that CSIOR is enabled and that the NVMe disk is qualified by Dell.

Storage

1. iDRAC interfaces do not support slicing RAID volumes through software RAID controllers. To configure sliced RAID volumes, use F2 Device settings.
2. Part number for Predictive failure message "PDR16" for NVMe drive may appear as "Not Available" immediately after the cold reboot. Allow some time after the cold reboot for iDRAC to initialize the inventory.
3. While renaming a virtual disk (VD), using a . (period) is not allowed in the VD name.
4. If your system has a PERC card configured in Enhanced HBA mode and you downgrade iDRAC to an older version, the SET commands for storage configuration may fail. To resolve the issue, ensure that a Collect System Inventory On Reboot (CSIOR) is performed after the downgrade. To perform a CSIOR, use the following methods:
   a. Completely turn off the system and then turn it on again.
   b. Ensure that CSIOR is enabled before turning off the system.
   c. Use the following RACADM command: racadm serveraction powercycle
5. Few legacy drives do not support the SMART ID #245 "Remaining Rated Write Endurance". In such cases, iDRAC interfaces may display the "Remaining Rated Write Endurance" attribute as unavailable.
6. If a M.2 SATA drive attached to BOSS-S2 controller is removed, performing a blink operation may not fail for the removed drive.

SupportAssist and parts replacement

1. Part-replacement of BOSS-S1 controller is not detected by Lifecycle Controller. After replacing the controller, follow the instructions in the controller's documentation.

Firmware and driver update

1. In PowerEdge systems with AMD configuration, if a PSU firmware update is initiated from LCUI, host goes into powered-off state and Job is Completed with status 0%. Ensure that you power on the system using any iDRAC interface to start the PSU firmware update.
2. CMC server component update does not support the iDRAC9 firmware packages. Use iDRAC GUI, RACADM interface, or OpenManage Enterprise Modular to perform any out-of-band updates of iDRAC9 firmware.
3. After an iDRAC reset or firmware update operation, the ServerPoweredOnTime—a property in RACADM and WSMan—may not be populated until the host server is restarted.
4. Some of the supported components may not be displayed on the Firmware Update > View Current Versions page. To update this list, restart the system.
5. If the iDRAC firmware update is interrupted, you may have to wait up to 30 minutes before attempting another firmware update.
6. Firmware update is supported only for LAN on Motherboards (LoM), Network Daughter Cards (NDC), and network adapters from Broadcom, QLogic, and Intel, and some of the QLogic and Emulex fiber channel cards. For the list of supported fiber channel cards, see the Lifecycle Controller User's Guide available at https://www.dell.com/idracmanuals..
7. After the CPLD firmware is updated on modular systems, the firmware update date is displayed as 2000-01-01 on the View Current Versions page. The update date and time is displayed according to the time zone configured on the server.
8. On some modular systems, after a firmware update, the Lifecycle Log displays the timestamp as 1999-12-31 instead of the date on which the firmware update was performed.
9. It is not recommended to perform CPLD update along with other updates. If a CPLD update is uploaded and updated along with other updates using iDRAC web interface, CPLD update completes successfully but the other updates do not take effect. To complete the iDRAC updates, reinitiate the updates.

Miscellaneous

1. You may be unable to scroll using the keyboard. Use the mouse to scroll.
2. Due to a limitation of Google Chrome browser, HTML5 virtual console intermittently displays the following error message: Chrome ran out of memory while trying to display the webpage.
3. When accessing the iDRAC web interface for the first time using Google Chrome version 59.0, the mouse pointer may not be visible. To display the mouse pointer, refresh the page or use Google Chrome version 61.0 or later.
4. If you use the HTML5 plug-in on Chrome version 61.0 to access Virtual Console, you cannot connect to Virtual Media. To connect to Virtual Media using the HTML5 plug-in, use Chrome version 63 or later.
5. Launching Virtual Console with Java plug-in fails after the iDRAC firmware is updated. Delete the Java cache and then launch the virtual console.
6. A Serial-On-Lan (SOL) session that has been active for more than five days or multiple reboots may get terminated automatically. If the session terminates, you must reinitiate the session.
7. Due to an issue with Safari, if an ipv6 literal address is used to log into the Web GUI, Safari is not able to launch the HTML5 based vConsole. Alternative options are to use Java based vConsole, or HTML5 vConsole by using the corresponding DNS name or by using an alternate browser in Mac OS.
8. iDRAC login page does not allow password entry using Firefox browser in Ubuntu management OS.
9. iDRAC and LC features cannot access CIFS or Samba shares when only SMBv1 protocol is enabled. All iDRAC features work with SMBv2 protocol. For information on enabling SMBv2 protocol, see the documentation for your operating system.
10. In Lifecycle Controller GUI, using keyboard to browse folders and files is not supported. Use the mouse to navigate through files and folders.
11. When accessing iDRAC through a Safari web browser version 14.0.3 and later versions, if a page refresh is attempted using the browser refresh option, then the iDRAC session may get cleared and you may get redirected to the iDRAC dashboard page. To refresh the page, use the Refresh option available on the iDRAC console.

Environmental and system requirements

License Requirements

iDRAC features are available based on the purchased license.

• iDRAC Express—Available by default on all blade servers, and rack or tower servers of 600 or higher series
• iDRAC Enterprise—Available on all servers as an upgrade
• iDRAC Datacenter—Available on all servers as an upgrade.
• iDRAC Secure Enterprise Key Manager(SEKM)—Available on all servers as an upgrade.
  NOTE: IDRAC Secure Enterprise Key Manager(SEKM) with PERC is not supported on MX series blade servers.
• BMC - Available only on Dell PowerEdge C series servers.

For more information about the features available for a license, see the iDRAC licenses section in the iDRAC User's Guide available at dell.com/idracmanuals.

NOTE: To manage new and existing licenses, go to the Dell Digital Locker.

Supported systems

16th Generation of PowerEdge Servers

PowerEdge XE9640

Supported managed server operating systems and hypervisors

• Microsoft Windows
  • Server 2022 Standard
  • Server 2022 Datacenter
  • Server 2019 Standard (Downgrade only)
  • Server 2019 Datacenter (Downgrade only)
  • WinPE 5.0 64-bit
  • WinPE 10
• Microsoft Azure Stack HCI v2 and v3
• Linux
  • RHEL 9.1
  • RHEL 8.7
• SLES
  • SLES 15 SP4
• Ubuntu
  • Ubuntu 22.04.1
• VMware
  • ESXi 8.0
  • ESXi 7.0 U3

Supported web browsers

• Microsoft EDGE
• Safari 15
• Mozilla Firefox 100
• Mozilla Firefox 99
• Google Chrome 102
• Google Chrome 101

Supported software

Java

• Java - Oracle version

OpenSource tools

• OpenJDK 8u202
• Adopt Open JDK
• You may utilize an open source version of AdoptOpenJDK or OpenJDK (“Adopt Open JDK”) subject to the terms and conditions of the Adopt Open JDK community at the link below.
  • You use Adopt Open JDK at your own risk. Adopt Open JDK may not meet your requirements or expectations. It could include quality, technical or other mistakes, inaccuracies or typographical errors.
  • Dell does not provide support or maintenance for Adopt Open JDK.
  • Dell makes no express warranties, and disclaims all implied warranties, including merchantability, fitness for a particular purpose, title, and non-infringement as well as any warranty arising by statute, operation of law, course of dealing or performance or usage of trade regarding Adopt Open JDK.
  • Dell has no liability to you for any damage that arise out of or relate to your use of Adopt Open JDK.

iDRAC Service Module (iSM)

iSM version 5.1.0.0 or later

iDRAC tools

This version of iDRAC requires the following tools based on the operating system:

• Dell iDRAC Tools for Microsoft Windows Server(R), v11.0.0.0
• Dell IDRAC Tools for Linux, v11.0.0.0
• Dell iDRAC Tools for VMware ESXi (R), v11.0.0.0
• This version contains:
  • Remote/Local RACADM on Windows or Linux or ESXi
  • IPMI Tool on Windows or Linux
  • Secured Component Verification (SCV)

Download the DRAC tools from the Drivers & downloads page for your system at https://www.dell.com/support.

Before installing iDRAC tools from OM 9.5.0, you must uninstall any older versions of DRAC tools. For more information about uninstalling applications, see the documentation for your operating system.

Supported Key Management Server (KMS) for Secured Enterprise Key Manager (SEKM)

• Cipher Trust Manager version 2.10.2
• IBM Security Guardium Key Lifecycle Manager version 4.1.1.0
• Utimaco Enterprise Secure Key Manager version 8.4.0
• KeySecure Classic version 8.12.5
• Thales Data Security Maanager (DSM) version 6.4.8

Installation and upgrade considerations

Downloading iDRAC firmware installation file

NOTE: For information about updating iDRAC firmware using various interfaces, see the iDRAC User's Guide available at https://www.dell.com/idracmanuals..

1. Go to https://www.dell.com/support.
2. In the Enter a Service Tag, Serial Number... field, type the Service Tag or the model number of your server, and press Enter or click the search icon.
3. On the product support page, click Drivers & downloads.
4. Select the appropriate operating system.
5. From the list, locate the iDRAC entry and click the download icon.

Updating iDRAC firmware from host OS

From the host operating system, execute the installation package that you downloaded and follow the instructions of the update wizard.

For more information about opening executable files on your system, see the operating system's documentation.

Updating iDRAC remotely using iDRAC web interface

You can remotely update the firmware from the management stations using the iDRAC web interface.

1. Extract the self-extracting installation package to the management station.
2. Access the iDRAC web interface using a supported web browser.
3. Log in as an administrator.
4. Click Maintenance > System Update.
   The Manual Update page is displayed.
5. Select Local to upload the firmware image from the local system.
6. Click Browse, select the .d9 file that you extracted or the Dell Update Package for Windows, and click Upload.
7. Wait for the upload to complete. After the upload is complete, the Update Details section displays the uploaded file and the status.
8. Select the firmware file and click Install.
   The message RAC0603: Updating Job Queue is displayed.
9. To view the status of the firmware update, click Job Queue.
   After the update is complete, iDRAC restarts automatically.

Resources and support

For more information about the features of this release, see the documentation for iDRAC 7.xx.

Latest Release Notes

To access the latest Release Notes for this version of iDRAC:

1. Go to www.dell.com/idracmanuals.
2. Click the link for the generation and then click the firmware series of iDRAC.
3. Click DOCUMENTATION.
4. Click MANUALS AND DOCUMENTS.

Accessing documents using direct links

You can directly access the documents using the following links:

Accessing documents using the product search

1. Go to https://www.dell.com/support.
2. In the Enter a Service Tag, Serial Number... search box, type the product name. For example, PowerEdge or iDRAC.
   A list of matching products is displayed.
3. Select your product and click the search icon or press enter.
4. Click DOCUMENTATION.
5. Click MANUALS AND DOCUMENTS.

Accessing documents using product selector

You can also access documents by selecting your product.

1. Go to https://www.dell.com/support.
2. Click Browse all products.
3. Click the desired product category, such as Servers, Software, Storage, and so on.
4. Click the desired product and then click the desired version if applicable.
   NOTE: For some products, you may need to navigate through the subcategories.
5. Click DOCUMENTATION.
6. Click MANUALS AND DOCUMENTS.