iDRAC9 Version 6.00.02.00 Release Notes

Release Summary

PDF

Storage and storage controllers

Table 1. Updated HBA controller version missing After an HBA controller firmware is updated through OS, iDRAC does not display the updated controller firmware version.
Description	HBA controller firmware version that was updated through OS is not displayed in iDRAC.
Workaround	Perform an iDRAC reset or cold boot the system.
Systems Affected	All systems supported by this release with HBA 330 or HBA 355 controller.
Tracking number	236357

Table 2. Storage inventory missing or Raidpop memory leakContinuous cold boot and warm boot of the host server may increase raidpop memory consumption and may lead to storage inventory loss for some time.
Description	Continuous cold boot and warm boot of the host server may increase raidpop memory consumption and may lead to storage inventory loss for some time.
Workaround	Perform an iDRAC reset.
Systems Affected	All systems supported by this release.
Tracking number	239078

Table 3. Information Not Available for Device Protocol Device protocol value may be displayed as "Information Not Available" in all iDRAC interfaces after NVMe drive that uses the NVMe 1.2 or below protocol versions is hot plugged.
Description	Device protocol value may be displayed as "Information Not Available" in all iDRAC interfaces after NVMe drive that uses the NVMe 1.2 or below protocol versions is hot plugged.
Workaround	AC power cycle the server or cold reboot the host and then perform an iDRAC reset.
Systems Affected	All systems supported by this release.
Tracking number	238868

Table 4. PERC Rekey failingIf iDRAC and PERC have the same Key Ids then PERC Rekey command fails.
Description	If iDRAC and PERC have the same Key Ids then PERC Rekey command fails.
Workaround	Use the iDRAC Rekey command instead of PERC Rekey.
Systems Affected	All systems supported by this release.
Tracking number	230629/189445

Table 5. Max Capable Speed reported as Unknown Maximum capable speed for SAS4 drives that are configured with PERC9, PERC10, or PERC 11 is reported as Unknown in iDRAC.
Description	Maximum capable speed for SAS4 drives that are configured with PERC9, PERC10, or PERC 11 is reported as Unknown in iDRAC.
Workaround	N/A
Systems Affected	All systems supported by this release.
Tracking number	230290

Table 6. LC logs display incorrect version change for disks After a disk firmware upgrade, LC logs may report it as a firmware downgrade with PR36 message.
Description	After a disk firmware upgrade, LC logs may report it as a firmware downgrade with PR36 message.
Workaround	Restart the host system.
Systems Affected	All systems supported by this release.
Tracking number	197049

Table 7. Deleting VD creates pending operation with empty data When existing VD is deleted from iDRAC GUI using delete VD operation from the Virtual disk option and then added to pending operation, the pending operation displays no information. However, the delete VD pending operation is created successfully.
Description	When existing VD is deleted from iDRAC GUI using delete VD operation from the Virtual disk option and then added to pending operation, the pending operation displays no information. However, the delete VD pending operation is created successfully.
Workaround	To successfully delete the VD and add to pending operations, perform the following steps: Select the Configuration option in iDRAC GUI Select Storage Configuration, then select the Controller and click Apply now.
Systems Affected	All systems supported by this release.
Tracking number	184393