Release Notes

system reboots after you click OK. However, on next boot to LC UI, the boot mode is changed to BIOS and the
boot device selected during OS deployment is discarded.
Workaround Before deploying OS using LC UI, change the boot mode to BIOS from BIOS setup (F2 at POST).
Systems affected All systems supported by this release.
Tracking number 98665
Header error while using Powershell for Redfish
requests
Description iDRAC RESTful API with Redfish displays an error stating unacceptable header specified in request for commands
run on PowerShell. Unlike other REST API tools such as Python, CURL and Postman, the PowerShell Invoke-
WebRequest command does NOT automatically add a header to REST requests; the header must be explicitly
included by the programmer.
Workaround You need to explicitly include a header while using Powershell for any type of Redfish request.
Systems affected All systems supported by this release.
Tracking number N/A
Port 5353 blocked by iDRAC internal firewall and
appears as Open|Filtered
Description
When node initiated discovery or Group Manager is enabled, iDRAC uses mDNS to communicate through port
5353. However, when both are disabled, port 5353 is blocked by iDRAC's internal firewall and appears as Open|
Filtered port in the port scans.
Workaround Group Manager and node initiated discovery need to be turned off in order to disable mDNS.
Systems affected All systems supported by this release.
Tracking number N/A
Repetitive PR7 messages related to PSU in LC logs
after a system erase operation
Description
When the system is powered on manually after performing a system erase on LC data, several messages are
displayed in LC logs for PSU stating “PR7 New device detected: POWER SUPPLY (PSU.Slot.X)”.
Workaround N/A
Systems affected All systems supported by this release.
Tracking number 129440
Qlogic Fiber channel device Link Status displayed
as Unknown or Unavailable
Description
iDRAC may report Network or Fiber channel device(s) Link Status as Unknown or Unavailable even though the
link status is operational.
Workaround Reset the iDRAC or power cycle the system.
Systems affected All systems supported by this release.
Known issues — To be fixed in future releases 17