iDRAC9 Version 6.00.30.25 Release Notes

Product Description and Release Summary

The Integrated Dell Remote Access Controller (iDRAC) is designed to make server administrators more productive and improve the overall availability of Dell servers. iDRAC alerts administrators to server issues, helps them perform remote server management, and reduces the need for physical access to the server. Additionally, iDRAC enables administrators to deploy, monitor, manage, configure, update, and troubleshoot Dell servers from any location without using any agents. It accomplishes this regardless of the operating system or hypervisor presence or state.

iDRAC also provides an out-of-band mechanism for configuring the platform, applying firmware updates, saving or restoring a system backup, or deploying an operating system, either by using a GUI or a remote scripting language, such as Redfish or RACADM.

This release includes support for HBA355 OS quick boot support and fixes like liquid leakage reporting on systems with direct liquid cooling.

Topics:

• Revision History
• New features
• Deprecated features
• Resolved Issues
• Known issues -- To be fixed in future releases
• Important notes
• Limitations
• Environment and System Requirements
• Installation and upgrade considerations
• Resources and support
• Where to Get Help

Release date

December 2022

Priority and recommendations

Recommended: Dell Technologies recommends applying this update during your next scheduled update cycle. The update contains feature enhancements or changes that will help keep your system software current and compatible with other system modules (firmware, BIOS, drivers, and software).

Minimum version

Updating iDRAC firmware from a previous version, such as 3.2x, 3.1x, 3.0x to this version is not supported. Update the firmware to version 3.30.30.30 first, and then update to this version.

NOTE: For details about the previous releases, if applicable, or to determine the most recent release for your platform, and for latest documentation version, see KB article SLN308699 available at https://www.dell.com/support/article/sln308699.

Revision History

• 5.00.00.00
• 5.00.10.20
• 5.00.20.00
• 5.10.00.00
• 5.00.20.10
• 5.10.10.00
• 5.10.30.00
• 6.00.02.00

New features

Hardware

• Support for Titanium PSUs.
• Support for 4 GB SDRAM DDR4.
• Support for firmware upgrade of TPM 2.0 and TPM 1.2.

Storage and storage controllers

• Support for HBA355 ESXi OS quick boot.
• Support for adding HBA350i Mini Monolithic (MM) and HBA350i Mini Monolithic Low Profile (MM LP) controllers.

Automation -- API and CLI

• Added Chassis Manager firmware version to "racadm getsysinfo" command.

Deprecated features

The following table displays the features that are listed as deprecated*, Removed**, and To be Removed***:

Resolved Issues

BIOS and UEFI

• 229217/225671: BIOS update job progress remains at 10%.

iDRAC firmware

• 229351: CPLD update through Custom Catalog fails.

Monitoring and alerting

• 247095: System event logs failing to report liquid leakage in systems with liquid cooling.
• 240678: System event log SEL1514: Inlet temperature sensor data is not responding or not working.

Networking and IO

• 211380: FC Link status displayed as unavailable in iDRAC after a server reboot.
• 230642: Incorrect link speed displayed for iDRAC dedicated port.
• 218223: Shared NIC OCP link connection failure after AC power cycle.

Automation -- API and CLI

• 237176: RACADM exits with error invalid RC 17 for iDRAC.Security.
• 223742: Unable to discard pending jobs during an iDRAC firmware rollback or update.

Known issues -- To be fixed in future releases

Hardware

iDRAC firmware

Monitoring and alerting

Networking and IO

OS deployment

Automation -- API and CLI

Storage and storage controllers

Miscellaneous

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.
3. This note is applicable only to PowerEdge R540. While updating the BIOS firmware through local RACADM with local share, you may get an error "ERROR: RAC989: Unable to apply the BIOS_3P4XY_WN64_1.6.11.EXE firmware update." Use the direct DUP installation or installation through CIFS/NFS share to update the BIOS firmware.

iDRAC firmware

1. 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.
2. 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.
3. 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.
4. 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.
5. If Lifecycle controller logs display RED057 message during a component update, then run the command systemerase lcdata through RACADM interface and then retry the operation.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. After updating the iDRAC license to Data Center license, ensure that you reboot the iDRAC for Idle server detection feature related attributes to function.
14. Updating iDRAC firmware from version 3.3x to 4.xx or later using http/https/ftp share may fail if you use the default file name. Ensure to rename the file name before you proceed with the firmware update.
15. In LifeCycle Controller GUI, use the mouse to browse files or folders. Browsing files using keyboard is not supported.
16. 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.
17. 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.
18. When node initiated discovery or Group Manager is enabled, iDRAC uses mDNS to communicate through port 5353. Turn off the Group Manager and node initiated discovery to disable mDNS.
19. After iDRAC is upgraded to version 4.xx or later, you may stop receiving encrypted email alerts from iDRAC, if the external email server does not support encryption. iDRAC firmware version 4.xx or later includes a user-selectable encryption option and the default protocol is StartTLS. To start receiving email messages again, disable the email encryption by using the following RACADM command: racadm set idrac.RemoteHosts.ConnectionEncryption None
20. Windows Server 2012, Windows Server 2008 R2, and Windows 7 do not support TLS 1.2 and TLS 1.1. Install the following update to enable TLS 1.2 and TLS 1.1 as a default secure protocols in WinHTTP in Windows: http://support.microsoft.com/kb/3140245/EN-US
21. The drivers that LC exposes are present in a read-only drive that is labeled OEMDRV and the drive is active for 18 hours. During this period:
    a. You cannot update any DUP.
    b. LC cannot involve CSIOR.
    However, if a server AC power cycle or iDRAC reboot is performed, the OEMDRV drive is automatically detached.
22. When you reset or update the iDRAC, you must reboot LC if it is launched already. If you do not reboot, LC may show unexpected behavior.
23. Firmware rollback is not supported for CPLD, NVDIMM, SAS/SATA drives, and PSU (on modular systems).
24. When CMCs are daisy chained, only the first CMC (CMC which is connected to Top of Rack switch) receives LLDP packets. Other CMCs do not receive LLDP packets. So, the iDRAC network port (dedicated mode) LLDP information is not available in the blades whose corresponding CMC is not the first CMC in the daisy chain. The LLDP information is also not available for every CMC in the daisy chain that is not connected to TOR switch directly.

Limitations

Authentication

1. LC supports the following characters for username and password:
   
   • Alphabets (a-z, A-Z)
   • Numbers (0-9)
   • Special characters (-, _, .)
2. If there are no slots available to add a new user in iDRAC, the Group Manager Job for Add New User shows a failure with error GMGR0047. Use the web interface (iDRAC Settings > Users) to verify the number of iDRAC local users.
3. If the user does not exist on a specific iDRAC, Group Manager Jobs for Change User Password and Delete User show a failure with error GMGR0047. Use the web interface (iDRAC Settings > Users) to verify that the user exists.

Automation -- API and CLI

1. Sometimes, when using WSMan, an Internal SSL Error is reported and the WSMan command fails. If this issue occurs, retry the command.
2. Using WSMan, the attribute LCD.ChassisIdentifyDuration cannot be set to -1 (indefinite blink). To make the LED blink indefinitely, use the IdentifyChassis command with IdentifyState=1.
3. RACADM supports the underscore character (_) for iDRAC.SerialRedirection.QuitKey along with the existing symbols shown in the integrated help.
4. If iDRAC is in lockdown mode and you run the command 'racadm rollback', followed by the command 'racadm resetcfg', an incorrect message is displayed: ERROR: A firmware update is currently in progress. Unable to reset the RAC at this time. Reboot iDRAC to display the correct error message.
5. While using a Top or Skip command, if you enter a value greater than the unsigned long type (4,294,967,295), you may get an incorrect error message.

BIOS and UEFI

1. 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.

Hardware

1. In LC, not all the vendor FC cards are supported for VLAN configuration.
2. If an H730P adapter is installed in slot 9 (internal PERC slot) of PowerEdge T640, iDRAC displays it as H730P Integrated RAID Controller (Embedded).

iDRAC firmware

1. PowerEdge servers that shipped with iDRAC9 4.40.40.00 or later versions require stepped downgrades before rolling back to version 4.40.00.00 or older firmware. The iDRAC9 must be downgraded to 4.40.10.00 and then to the older firmware.
2. In Firmware Rollback page, the component names may vary in iDRAC GUI and Lifecycle Controller(LC) GUI.
3. Due to known limitations in OpenSource (SFCB), query filtering with long integers and lengthy strings may not work as expected.
4. LC can import and view an iDRAC license but cannot export or delete the iDRAC license. The iDRAC license can be deleted from iDRAC web interface.
5. The iSCSI offload attribute can be enabled only on two of the four available ports. If a card, which has this attribute that is enabled on two of its ports, is replaced with another card that has the attribute that is enabled on the other two ports, an error occurs. The firmware does not allow the attribute to be set because it is already set on the other two ports.
6. The "Discovered Servers" view of Group Manager may not show available iDRACs as available to onboard. Verify that the iDRACs are on the same link local network and not separated by a router. If they are still not visible, reset the Group Manager's controlling iDRAC.
   a. Open Group Manager on one of the member iDRACs.
   b. In the search box, type the controlling system's Service Tag.
   c. Double-click the iDRAC that matches the search results and go to iDRAC Settings -> Diagnostics.
   d. Select Reset iDRAC.
   When iDRAC fully restarts, Group Manager should see the new iDRAC.
7. If Emulex LightPulse LPe31002-M6-D and Emulex LightPulse LPe35002-M2 FC adapters are configured to boot from FC storage arrays using VAM method in iDRAC, then a maximum of two boot target arrays can be configured instead of eight.
8. During import server profile operation, if the image filename is "Backup.img", operation may fail. To avoid this failure, change the filename.

Monitoring and alerting

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. iDRAC supports iSM version 3.4.1 and above.
10. 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. 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.

Environment 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

• PowerEdge C6520
• PowerEdge C6525

Supported managed server operating systems and hypervisors

• Microsoft Windows
  • Server 2022 Essentials
  • Server 2022 Standard
  • Server 2022 Datacenter
  • Server 2019 Essentials
  • Server 2019 Standard
  • Server 2019 Datacenter
  • Server 2016 Essentials
  • Server 2016 Datacenter
  • Server 2016 Standard
  • WinPE 5.0 64-bit
  • WinPE 10
• Microsoft Azure Stack HCI
• Linux
  • RHEL 9.0
  • RHEL 8.5
  • SLES
  • SLES 15 SP3
  • Ubuntu
  • Ubuntu 22.04
  • Ubuntu 20.04.4
• VMware
  • ESXi 7.0 U3
  • ESXi 6.7 U3

Supported web browsers

• Microsoft Internet Explorer 11
• 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.

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 6.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.
5. NOTE: For some products, you may need to navigate through the subcategories.
6. Click DOCUMENTATION.
7. Click MANUALS AND DOCUMENTS.

Where to Get Help

Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues, see https://www.dell.com/contactdell.

If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or the product catalog.

Lifecycle Controller (LC) Remote Services -- client tools

Redfish API

For information about Redfish, see the DMTF website https://www.dmtf.org/standards/redfish. This website provides access to schema files, white papers, technical notes, and so on.

For iDRAC Redfish API guide, go to https://developer.dell.com.

Copyright

© 2022 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.