Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • 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 Premier Sign In Partner Program Sign In
Contact Us

iDRAC9 Version 5.10.30.00 Release Notes

PDF

Monitoring and alerting

  1. OS collector application is now bundled with iDRAC Service Module version 4.0.1 and later versions. After iDRAC firmware is upgraded to version 4.40.40.00 or later versions, iDRAC inventory will no longer display OS Collector application separately in the firmware inventory page.
  2. Redfish Life Cycle Events (RLCE) do not support event generation for collection resources.
  3. For staged operations that require system reboot, after the system reboot is complete RLCE events for the operation may take up to 20 s depending on the system configuration.
  4. A Redfish request to update or post with JSON format payload supports only the first valid JSON in the request. If additional text is passed in the payload, the text gets discarded.
  5. While PERC inventory is in progress, Lifecycle controller logging may fail after a warm reboot by RTCEM for HBA, BOSS, or NVME drives.
  6. 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.
  7. 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 either a failed state or job that is stuck in running. It is also recommended that after you use "JID_CLEARALL_FORCE", an iDRAC reset is needed to ensure iDRAC is back in a good working state. Ensure that all the services are in ready state before performing iDRAC reset. To check the status of the services, run the command getremoteservicesstatus.
  8. 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.
  9. 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.
  10. 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>
  11. 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: <>()\