Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

iDRAC9 Version 4.30.30.30 Release Notes

PDF

Important notes

  1. While performing a firmware update or rollback through LifeCycle controller GUI, the component information displayed in the table listing the available updates may be truncated if it exceeds the table column or row width.
  2. If SOL session is active for a long duration or if the system is rebooted multiple times, the SOL session gets terminated automatically.
  3. Critical event PDR1016 will not be generated when M.2 drives from the BOSS-S2 controller are removed since M.2 drives are directly attached to BOSS controller and not connected to the backplane.
  4. While performing BIOS Recovery operation all iDRAC resets are blocked and if a iDRAC reset to default operation is performed, it will cause iDRAC to be set to factory defaults and iDRAC will not reset. The condition is expected and a manual iDRAC reset is recommended.
  5. 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.
  6. Unlike RAID 10 configured via iDRAC, OMSA or PERCCLI with all disks on a single span, a RAID 10 VD created in the Lifecycle Controller only supports two disks per span. Therefore, expansion of RAID 10 VD created in the LC is not permissible.
  7. AD/LDAP diagnostic results will display Not Run or Not Applicable for Ping Directory Server Tests. ICMP ping tests are no longer performed while running AD/LDAP diagnostics.
  8. 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.
  9. While clearing the Job queue using RACADM, WSMAN, or Redfish interface, it is recommended to use JID_CLEARALL instead of JID_CLEARALL_FORCE . Use JID_CLEARALL_FORCE only to recover iDRAC Lifecycle controller from a failed state to avoid an iDRAC restart.
  10. For Dell online catalog update, downloads.dell.com only supports https protocol.
  11. After updating the iDRAC license to Data Center license, ensure that you reboot the iDRAC for Idle server detection feature related attributes to function.
  12. Updating firmware from version 3.30.30.30/3.34.34.34/3.36.36.36 to 4.00.00.00 or later using http/https/ftp share may fail if you use default file name. Ensure to rename the file name before you proceed with the firmware update.
  13. In LifeCycle Controller GUI, use mouse to browse files or folders. Keyboard navigation does not work while browsing files.
  14. 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.
  15. 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.
  16. While performing any method (GET/POST and so on) on an incorrect Dell-specific URI, a proper extended error message specifying that “Resource URI is incorrect” is not provided in the response body.
  17. PSU Part Replacement Firmware Update will not initiate if the secondary string of the new firmware is the same as the secondary string of replaced PSU’s existing firmware. Firmware version string format is denoted as xx.yy.zz, where zz is the secondary string.
  18. You may get an irrelevant response message while performing operating system method to Insert media with incorrect media for firmware upgradation or OS deployment.
  19. While streaming telemetry reports for an older version of Rsyslog servers, the system may intermittently miss a few reported data. Upgrade the Rsyslog server to the latest version.
  20. 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.
  21. iDRAC RESTful API with Redfish displays an error stating unacceptable header specified in request for commands that are run on PowerShell. You need to explicitly include a header while using Powershell for any type of Redfish request.
  22. When node initiated discovery or Group Manager is enabled, iDRAC uses mDNS to communicate through port 5353. Turn off Group Manager and node initiated discovery to disable mDNS.
  23. SMART monitoring is disabled for a hard drive while it is set to Non-Raid mode.
  24. In systems with network adapters without internal temperature sensors, for some adapters the NIC temperature sensors metric value is reported as 0.
  25. After any iDRAC reset event, including the iDRAC firmware update, the LC Log event time is incorrectly reported for few events. This condition is momentary, and iDRAC time catches up to correct time.
  26. Performing GET method on Steps only shows the next scheduled jobs and not the completed jobs.
  27. If you install OMSA while iSM is already installed and connected, iSM may restart after the OMSA installation is complete.
  28. After iDRAC is upgraded to version 4.00.00.00 or later for the first time, there may be a change in network settings option including IPv4 and IPv6. Reconfigure the network settings to resolve this.
  29. After iDRAC is upgraded to version 4.00.00.00 or later, you may stop receiving encrypted email alerts from iDRAC, if the external email server does not support encryption. iDRAC firmware version 4.00.00.00 or later introduces 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
  30. 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
  31. 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:
    1. You cannot update any DUP.
    2. LC cannot involve CSIOR.

    However, if a server AC power cycle or iDRAC reboot is performed, the OEMDRV drive is automatically detached.

  32. CPLD firmware update has no impact on Trusted Platform Module enablement.
  33. Depending on the virtual storage device attached through iDRAC, that is, USB drive or CD/DVD .ISO file, LC displays Virtual Floppy or Virtual CD respectively.
  34. If the network is not configured and you try to perform a network operation in LC, a warning message is displayed. When you go to the network settings page from this message, the left navigation panel on network settings page may not be displayed.
  35. If a network operation fails for a valid address, try configuring the network settings again. If the issue persists, restart the system and retry the operation.
  36. 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.
  37. Fibre-channel NIC cards with dual or four ports are displayed as a single port card in LC. However, all ports are updated when a firmware update is performed.
  38. The option to enable or disable the disk cache policy for SWRAID controllers are supported only on SWRAID controller driver version 4.1.0-0025 or later.
  39. Rollback is not supported for CPLD and HBA controllers.
  40. 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.
  41. If any of the NVMe drives report a 'Failed' status (Red LED) due to any of NVMe controller SMART errors (critical warning bits set), it should be treated as a predictive failure (Blinking amber LED). These errors include SMART errors such as:
    1. Available spare threshold
    2. Reliability degraded
    3. Read-only mode
    4. Virtual memory backup failed, and so on.
  42. This note is applicable only to PowerEdge C6420, DCS9650, DCS9670, and DCS9690 systems. If you update iDRAC to this version from version 3.02.x.x or earlier, you must perform a power cycle of the system before performing any power-related operations. The power cycle is required to tune the memory parameters without affecting the host. iDRAC tunes the memory parameters at the first power cycle after a firmware update. To allow the memory tuning to be completed:
    1. Update to this version of iDRAC.
    2. At the next possible maintenance cycle, or before any power operations are performed, power off the host.
    3. Wait for 2 minutes to allow iDRAC to reset and tune the memory parameters.
    4. Power on the host.
  43. This note is applicable only to PowerEdge M640 and FC640. If you update iDRAC to this version, you must perform a virtual reseat of the system from CMC. Reseat is required to tune the memory parameters and to resolve issues that may lead to the watchdog timer causing iDRAC to be reset. To allow the memory tuning to be completed:
    1. Update to this version of iDRAC.
    2. At the next possible maintenance cycle, perform a virtual reseat.
  44. After updating iDRAC Firmware to 3.30.30.30 from a previous version, the first inventory collection after system reboot may display both PR7 (New Device Detected) and PR8 (Device not detected) messages. This is an expected behavior that is caused by a change in the slot number display format.
  45. Ensure that the SSH client is updated to the latest version. Following SSH configurations are no longer available on iDRAC:
    KEX algorithms:
    1. diffie-hellman-group14-sha1
    MAC:
    1. umac-64
    2. umac-64-etm@openssh.com
  46. This note is applicable only to PowerEdge M640 and FC640. When performing BIOS Recovery operation, host may not turn on. To recover from this condition, do a virtual/physical reseat operation of the blade server.
  47. After updating the iDRAC firmware, LC logs may display Message ID PR36 that "Version change detected for PCIe SSD firmware. Previous version:X.X.X, Current version:X.X.X." This is due to a change in the naming convention. Ignore the log entry.
  48. After downgrading the iDRAC firmware to any previous versions, storage page and drives may display warnings. To resolve the issue, reset iDRAC using the 'racreset' command.
  49. 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.
  50. If you get an error while performing SupportAssist collection through RACADM using HTTPS share, use the following commands to perform the collection:
    1. Racadm SupportAssist collect. 
      racadm supportassist collect -t Sysinfo
    2. Racadm SupportAssist exportlastcollection 
      racadm supportassist exportlastcollection -l <https> -u <username> -p <password>
  51. The Lifecycle Controller GUI features available on your system depends on the iDRAC license installed. The GUI help pages may display information about features that are not available with the license installed. For licensed feature list, see the Licensed Feature section in iDRAC User's guide available at Dell.com/iDRACmanuals.
  52. For improved support on drives and operating system deployment, it is recommended to use the UEFI BIOS boot mode.
  53. To create a virtual disk or deploy an operating system, ensure that you use the Dell supported SATA, SAS, or NVMe drives. For more information, see the documentation for BIOS, controller, and drive.
  54. In the software inventory, the hash value for iDRAC firmware is displayed as NA instead of hash.
  55. If SMBv2 share fails in Lifecycle GUI, ensure that:
    • The Digitally sign communications option is disabled.
    • Permissions to access the folder or file is granted.
    • folder/file name does not have a space.
    • Share contains fewer files and folders.
  56. While iDRAC is initializing, all communications with iDRAC may fail. For any service requests, wait until the initialization process is complete.
  57. Performing Redfish Patch method on Read-Only property for PowerControl resource returns a status code 200.
  58. In iDRAC, if there is no link that is detected in the selected iDRAC port then the iDRAC IP is displayed as 0.0.0.0.
  59. While performing a firmware update on a system where the operating system is installed with GNOME GUI enabled, system may get into Suspend mode. To avoid the system from going into suspend mode, ensure that you change the power settings in the operating system. To change the power settings:
    1. Go to Settings, and select Power.
    2. For the option, “When the Power Button is pressed” select Power Off.
  60. Firmware update on drives and backplanes through Windows DUP will reflect in iDRAC after a cold boot. In Lifecycle logs, version change may be displayed repeatedly if cold reboot is not done.
  61. FRU objects or properties for Network adapters that are embedded on the motherboard are not available through any of the iDRAC interfaces.
  62. Lifecycle Controller supports ISO images with ISO-9660 format only. Other formats including combination with ISO-9660 are not recommended.
  63. UserDefined delay AC Recovery Power Delay is slow with lower limit of 60, but some conditions might cause BMC ready to be later than this and hence may not work. So, it is advised that the UserDefined delay be set to 80 s or higher. Any values less than this may cause the operation to fail.
  64. The iDRAC feature “Topology LLDP” is not supported on 1 GbE controllers and on selected 10 GbE controllers (Intel X520, QLogic 578xx).
  65. Mellanox network adapters that are used in PowerEdge MX740c and MX840c servers must be updated to version 14.23.10.20 or later, before updating the iDRAC firmware to version 4.00.00.00 or later.
  66. Install SEKM license before you update the iDRAC to SEKM supported version 4.00.00.00 or later. If you install the SEKM license after updating the iDRAC to SEKM supported version, you have to reapply SEKM supported iDRAC firmware.
  67. If you are configuring a Gemalto based KeySecure SEKM Server with iDRAC, and to get the redundancy feature functional, copy the certificates manually from primary Gemalto KeySecure cluster to secondary Gemalto SEKM KeySecure cluster. The redundance feature works after the iDRAC is set up for SSL certificate-based authentication.
  68. Key sharing between multiple iDRACs is supported and can be configured on the SEKM server. Key sharing can be done if all the iDRACs are part of the same SEKM group and all keys are assigned to the same group with the right permissions.
  69. When FCP is enabled, 'Default Password Warning' setting is disabled after the default user password is changed.
  70. Firmware update from iDRAC versions earlier than version 3.30.30.30 is not supported (For example, updating iDRAC firmware from version 3.21.21.21 to version 4.00.00.00 or later is not supported). First update to version 3.30.30.30 or higher, and then initiate update to 4.00.00.00 or later.
  71. If system lockdown mode is enabled while a user is logged into LifeCycle Controller GUI, then lockdown mode will not be applicable on LifeCycle Controller.
  72. Due to a DMTF tool limitation, the URIs for some OEM actions that are extensions to the DMTF schemas may not appear in the OpenAPI.YAML file.
  73. The iDRAC Virtual Keyboard labeling is changed to upper case to align it with the physical keyboard layout.
  74. Keyboard interactive authentication has been enabled on the iDRAC SSH Server to provide enhanced security. SSH clients now require both password authentication and keyboard interactive authentication to before logging in a user in to iDRAC.
  75. If you see iSM0050 event in LC log, then ensure that you update the iDRAC Service Module (iSM) to version 3.4 or to a TLS-capable iSM. iSM without TLS capability is not supported on iDRAC firmware version 3.30.30.30 or later.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\