DELL iDRAC9 Remote Access Controller User Guide

DELL iDRAC9 Remote Access Controller

Specifications

• Product: iDRAC9 Version 7.10.50.05
• Release Date: June 2024
• Supports: AMD Mi300x GPU, Dell CX-7 network adapter, NVIDIA G6X10 FC card
• Release Type: Major (MA)

iDRAC9 Version 7.10.50.05 Release Notes
The Integrated Dell Remote Access Controller (iDRAC) is designed to make server administrators more productive and improve the overall availability of Dell servers. This release adds support for AMD Mi300x GPU and Dell CX-7 network adapter on PowerEdge XE9680.

• Current Release Version: 7.10.50.05
• Release Type: Major (MA)

Topics:

• Revision History
• Product Description
• New and enhanced features
• Fixes
• Known issues
• Limitations
• Environmental and system requirements
• Installation and upgrade considerations
• Where to get help

Revision History

● N/A

NOTE : The list of previous iDRAC versions that are supported may vary depending on the server model. To see the supported previous versions for a specific server:

1. Go to the Dell Support page.
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. From the list, locate and expand the iDRAC entry and click Older versions.
   A list of all previous versions supported is displayed along with the download link and the release date.

Product Description

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.

Release date
June 2024

Priority and recommendations
Recommended: Dell 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
N/A

NOTE : For details about the previous releases, if applicable, or to determine the most recent release for your platform, and for the latest documentation version, see Integrated Dell Remote Access Controller 9 Versions and Release Notes.

New and enhanced features

Hardware

• iDRAC9 support for AMD Mi300x GPU on PowerEdge XE9680 server.
• Support for Dell CX-7 network adapter.
• Support for NVIDIA G6X10 FC card.

NOTE : Sideband support on the NVIDIA G6X10 FC card is not available with the current iDRAC firmware version.

Monitoring and alerting
Support to export GPU logs through Technical Support Report (TSR logs).

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

Table 1. Deprecated Features

Features| iDRAC9 for 14th- Generation PowerEdge Rx4xx/ Cx4xx| iDRAC9 for 15th- Generation PowerEdge Rx5xx/ Cx5xx| iDRAC9 for 16th-Generation PowerEdge Rx6xx/ Cx6xx
---|---|---|---
SM-CLP| Removed| Removed| Removed
VM CLI| Removed| Removed| Removed
vFlash| Deprecated| Removed| Removed
Backup and Restore| Removed| Removed| Removed
 NOTE: Alternatively, use the Server Configuration Profiles (SCP) feature to import or export server configuration settings and firmware updates.
RBAP and Simple Identity profiles| Removed| Removed| Removed
WSMan| Deprecated| Deprecated| Deprecated
DCIM_account profile| Removed| Removed| Removed
Telnet and TLS 1.0| Removed| Removed| Removed
SHA1| Removed| Removed| Removed
Features| iDRAC9 for 14th- Generation PowerEdge Rx4xx/ Cx4xx| iDRAC9 for 15th- Generation PowerEdge Rx5xx/ Cx5xx| iDRAC9 for 16th-Generation PowerEdge Rx6xx/ Cx6xx
---|---|---|---
Java, ActiveX, and HTML5 plugins for console, media, and RFS access| Removed| Removed| Removed
NOTE: Attaching a virtual external device using a Java client is supported.
SupportAssist direct upload, scheduling, and register| Removed| Removed| Removed
 NOTE: Alternatively, use Secure Connect Gateway or OpenManage Enterprise Services plug-in for automatic case creation.

NOTE: In iDRAC release version 7.00.00.00 and later versions, Dell Tech Support no longer accepts automatic uploads of SupportAssist Collections.

• Deprecated*- No longer being updated or new features added.
• Removed**- Code has been removed, this feature is no longer functional.
• To be Removed***- Expected to be removed from iDRAC code in an upcoming release.

Fixes

N/A

Known issues

iDRAC firmware
Table 2. Firmware update failure

Details:

Description| Firmware update fails when the “Apply downgrade versions” option is selected.
Workaround| Retry the update using individual N-1 version DUPs.
Systems Affected| All systems are supported by this release.
Tracking number| 295292

Monitoring and alerting

Table 3. Erroneous TotalPSUHeatDissipation Metrics

Details:

Description| Intermittently, TotalPSUHeatDissipation telemetry metrics may display inaccurate negative values when GPU workloads are performed.
Workaround| Disregard the erroneous negative values.
Systems Affected| PowerEdge XE9680 with AMD MI300X GPUs.
Details:

Tracking number| 287175

Table 4. Overstated Power Consumption in TotalFPGAPower

Details:

Description| The TotalFPGAPower telemetry metric may indicate higher power consumption than the actual power consumed by the AMD MI300x FPGA card.
Workaround| See the Accelerator Power sensor values obtained through the ‘racadm get sensor info’ command for accurate measurement of power consumption by the FPGA card.
Systems Affected| PowerEdge XE9680 with AMD MI300X GPUs.
Tracking number| 286932

Table 5. Missing or duplicated sensor attributes

Details:

Description| Some attributes for sensors that are related to temperature or network are either absent or duplicated in the iDRAC GUI, under the System page.
Workaround| Resolve this issue by performing an iDRAC reboot.
Systems Affected| All systems are supported by this release.
Tracking number| 286491, 286425, 286266.

Table 6. DUP Update Failures

Details:

Description| Some attributes for sensors that are related to temperature or network are either absent or duplicated in the iDRAC GUI, under the System page.
Workaround| Resolve this issue by performing an iDRAC reboot.
Systems Affected| All systems are supported by this release.
Tracking number| 286491, 286425, 286266.

Table 7. Not ready status post cold boot

Details:

Description| After a cold boot, the RACADM command ‘getremoteservicesstatus’ indicates an overall status as Not Ready.
Workaround| Resolve this issue by performing an iDRAC reset.
Systems Affected| All systems supported by this release with SPDM SPDM-capable network controllers.
Tracking number| 285876

Table 8. Duplicate LC Log event issue after AMD MI300X firmware update

Details:

Description| Following the firmware update for AMD MI300X GPU using the “MI300X 8-GPU Baseboard Update Bundle” and subsequent power cycle, an LC Log event with Message ID JCP037 indicating the completion of the firmware update is recorded twice. The first instance occurs after the firmware update is finished, and the second occurs after the power cycle.
Details:

Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 285618

Table 9. SEKM043 Errors in Lifecycle Logs

Details:

Description| In instances of server stress, SEKM043 errors may be displayed in Lifecycle Logs, particularly when performing Disable or Enable actions on the drive.
Workaround| Initiate a cold boot or warm boot and then retry the operation.
Systems Affected| All systems are supported by this release.
Tracking number| 277050

Table 10. PDR8 and PDR5 disk removal and insertion logs during enclosure firmware updates

Details:

Description| During the firmware update process for enclosures like PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460, there are observations of PDR8 and PDR5 disk removal and insertion logs.
Workaround| N/A
Systems Affected| All systems supported by this release and connected to PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 enclosure through an HBA controller.
Tracking number| 275053

Table 11. Intermittent SWC9016 Error Triggering Front Panel Amber Light

Details:

Description| On occasional host cold boots, the Lifecycle(LC) Log and SEL log may display the message “SWC9016

– Unable to authenticate CPLD either because of unsuccessful cryptographic authentication or integrity issue.” This error results in the server front panel’s Amber light being activated and the health status changing to ‘critical.’

Workaround| This log error does not have a functional impact, and it can be cleared by performing an AC power cycle.
Systems Affected| All systems are supported by this release.
Tracking number| 276462

Table 12. PR1 & PR10 Lifecycle logs displayed during Retire and Repurpose operation 

Details:

Description| PR1 & PR10 logs are displayed in Lifecycle logs for PSUs when the Retire and Repurpose operation is executed. This doesn’t impact server functionality.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 186119

Table 13. After a warm reboot, LC logs display Disk Inserted

Details:

Description| Following a warm reboot of the server, iDRAC may report “Disk Inserted” in the LC logs for drives behind HBA or PERC12 controllers.
Workaround| Ignore the log entry.
Systems Affected| All systems are supported by this release.
Tracking number| 144819/141414/278145

Table 14. Repetitive PR7 messages related to PSU in LC logs after a system erase operation

Details:

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 are supported by this release.
Tracking number| 129440

Networking and IO

Table 15. Incorrect FCOE attributes reported

Details:

Description| The Fibre Channel over Ethernet (FCOE) attributes of the NIC reported by iDRAC are incorrect.
Workaround| While the reported attributes may be incorrect, they do not affect the functionality of the NIC or any associated operations. Systems Affected: All systems supported by this release.
Systems Affected| All systems are supported by this release.
Tracking number| 289309

Table 16. Failure in applying virtual MAC address configuration

Details:

Description| Virtual MAC address configuration may fail to be applied for some network adapters during an SCP configuration or host cold reboot.
Workaround| Enable the warm reboot persistence policy and perform a host warm reboot.
Systems Affected| PowerEdge XE9680
Tracking number| 292390

Table 17. NIC Mode switch issue

Details:

Description| When the NIC card is switched from Ethernet mode to InfiniBand mode or vice versa, both NIC and InfiniBand devices appear in iDRAC.
Workaround| Reboot the iDRAC.
Systems Affected| All 16G PowerEdge systems are supported by this release.
Tracking number| 295565

Table 18. The latest NIC firmware version not displaying in iDRAC

Details:

Description| When performing a real-time NIC firmware update without requiring a host reboot, if the update job is successful without requesting the host to reboot, the latest firmware version may not reflect in any of the iDRAC interfaces.
Workaround| Perform an iDRAC reset or reboot of the host system.
Systems Affected| All systems are supported by this release.
Tracking number| 277745

Table 19. HWC8010 error after installing a DPU card

Details:

Description| The server may report the error “HWC8010: Configuration error: Add-in card in slot x” after the server is restarted post a DPU card installation.
Workaround| Ensure that the DPU card is installed in the PCIe Slot 1 in PowerEdge R650 and Slot 2 in PowerEdge R750.
Systems Affected| PowerEdge R650 and PowerEdge R750
Tracking number| 232953

Table 20. Unable to add iDRAC Static IP

Details:

Description| After setting iDrac static IP using IPV4 group (IPv4.1.Address, IPv4.1.Gateway, IPv4.1.Netmask) using Redfish or RACADM interface, a new IP address may not apply and the system may become inaccessible.
Workaround| Use the IPV4Static group (IPv4Static.1.Address, IPv4Static.1.Gateway, IPv4Static.1.Netmask) to set the static IP address.
Systems Affected| All systems are supported by this release.
Tracking number| 185458

Table 21. Partial information displayed for Mellanox Cards

Details:

Description| iDRAC interfaces only display partial information for the Mellanox network cards, such as, in InfiniBand mode the card is displayed as a NIC device. Also, no board manufacturer and version are available.
Workaround| N/a
Systems Affected| All systems are supported by this release.
Tracking number| 179265

Table 22. NIC or FC device slot listed in hardware inventory even when disabled in BIOS

Details:

Description| For some NIC or FC cards, even if the device slot is disabled in BIOS, the slot may still get listed in the hardware inventory.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 104535

Automation — API and CLI

Table 23. Select query parameters issue

Details:

Description| The Select query parameter on the ComponentIntegrity URI fails for second-level attributes, and the ID attribute on DellAttribute URIs returns an incorrect value for the ID.
Workaround| N/A
Systems Affected| All systems supported by this release are configured with Emulex cards.
Tracking number| 283336

Table 24. Exporting ePSA Diagnostic Results Encounters Failure with SOCKS Proxy

Details:

Description| An issue has been identified wherein exporting ePSA Diagnostic Results using a SOCKS proxy through Redfish results in failure.
Workaround| Use the other iDRAC interfaces for exporting ePSA diagnostics.
Systems Affected| All systems are supported by this release.
Tracking number| 282869

Table 25. Drive property not displayed

Details:

Description| In Redfish API, the properties of some Samsung drives are displayed as unknown in the GET operation response.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 266130

Table 26. Expand query parameter issue

Details:

Description| Performing a GET method on the ComponentIntegrity instance with the Expand query parameter may fail to expand some of the properties or links.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 263837/272326

Table 27. GET method on Port collection returning incorrect information

Details:

Description| GET method on the Ports collection URI with a filter query parameter that includes the “ne” operator returns incorrect details.
Workaround| N/A
Systems Affected| All systems supported by this release
Tracking number| 261094

Table 28. Redfish Validator error

Details:

Description| Running a schema validator to check schema conformance may display an error about the NetworkAttributeRegistry instance that the JSON does not match the required URIs in Schema of AttributeRegistry.
Workaround| N/A
Systems Affected| All systems supported by this release
Tracking number| 268459

Table 29. RLCE reports an Incorrect value for the fan sensor

Details:

Description| Redfish Life Cycle Events may report incorrect data for fan sensor URI after a hot-pluggable fan is removed.
Workaround| Restart the host system.
Systems Affected| All systems are supported by this release.
Tracking number| 193777

Table 30. Service Validator reporting errors for Redfish API services

Details:

Description| To continue to support firmware backward compatibility, you may get errors for Redfish API services in the Service Validator. They do not have any functional impact on the system and may be ignored.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 183321

Table 31. Performing GET with the Top query parameter returns no error

Details:

Description| The top query on a Parity URI instance returns a complete response instead of an error code.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 175801

Table 32. Uploaded firmware link not available in SoftwareImages property

Details:

Description| While performing the GET method on BIOS or Manager Schema through Redfish, the SoftwareImages property may not display the uploaded firmware link.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 156737

Table 33. Attributes for CNA cards not displayed through Redfish or RACADM interface

Details:

Description| If the partitions are disabled on FCoE-capable CNA cards, a few HII attribute values for WWN, VirtWWN, WWPN, and VirtWWPN are displayed on the iDRAC GUI’s Network page. However, the same data is not displayed when Get commands are performed in Redfish and RACADM interfaces.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 151560

Table 34. Unable to create a recurring job after the same job was completed

Details:

Description| Creating a recurring job will fail if the same job was completed recently and its Task ID still exists.
Workaround| Wait for ten minutes for the Task ID to be deleted.
Systems Affected| All systems are supported by this release.
Tracking number| 147501

Table 35. Get operation not displaying model or serial number for PCIe devices

Details:

Description| If you perform a Get operation for a PCIe device using Redfish API, the response may not display the model and serial number of the device.
Workaround| N/A
Systems Affected| All systems are supported by this release.
Tracking number| 111564

Storage

Table 36. Failure in PSID Revert Job for Samsung SEDs

Details:

Description| When a Samsung Self-Encrypting Drive (SED) is removed from a system and then reinserted after two rekey operations have been performed on the same system, the PSID (Physical Security ID) revert job fails.
Workaround| Perform an iDRAC reboot.
Systems Affected| All systems are supported by this release.
Tracking number| 293183

Table 37. Incomplete LC Log entry for copy-back operations

Details:

Description| Incomplete Lifecycle (LC) log entries may occur during copy-back operations on the PERC12 controller.
Workaround| To check the details about the Copy Back destination drive, check the RAID controller logs (TTY log).
Systems Affected| All systems are supported by this release with PERC 12 Controllers.
Tracking number| 282136

Table 38. Enclosure Status reported incorrectly

Details:

Description| When the enclosure subcomponent Link Control Card (LCC) LCC-A or LCC-B is in a critical state, the overall enclosure status may still be reported as healthy.
Workaround| Perform an iDRAC reset to resolve the issue. Also, check the Lifecycle (LC) logs for any enclosure component failure messages.
Systems Affected| All systems supported by this release are configured with PowerVault MD 2412, PowerVault MD 2424, or PowerVault MD 2460 enclosures.
Tracking number| 292904

Table 39. Enclosure-Connector position mismatch

Details:

Description| An enclosure-connector position mismatch may occur when performing a cold or warm boot on a system experiencing an EMM failure.
Workaround| Perform an iDRAC reset.
Systems Affected| All systems are supported by this release.
Tracking number| 293863

Table 40. Connection Issue with Utimaco Key Management Server

Details:

Description| iDRAC encounters difficulty connecting to the Utimaco key management server version 8.50 when Client Certification Authentication is enabled in KMIP server authentication settings on KMS.
Workaround| Resolve the issue by disabling client certificate authentication.
Systems Affected| All systems supported by this release are configured with Utimaco key management server version 8.50.
Tracking number| 279795

Table 41. BOSS Security Configuration Job Failur e

Details:

Description| The BOSS security configuration job may encounter a failure when the system is under stress.
Workaround| Perform a cold reboot on the host.
Systems Affected| All systems are supported by this release.
Tracking number| 282234

Table 42. The drive part number is not displayed

Details:

Description| If a faulty drive is hot-inserted into the BOSS controller, the Part Number of the drive is not shown in the PDR3 Lifecycle logs.
Workaround| Go to the Storage Overview page to check the part number of the drive.
Systems Affected| All systems are supported by this release.
Tracking number| 270642

Table 43. LC logs display incorrect version changes for disks

Details:

Description| After a disk firmware upgrade, LC logs may report it as a firmware downgrade with a PR36 message.
Workaround| Restart the host system.
Systems Affected| All systems are supported by this release.
Tracking number| 197049

Miscellaneous

Table 44. The issue with the rollback of multiple BBU

Details:

Description| Performing multiple Battery Backup Units (BBU) firmware rollback, the rollback process is only applied to one BBU.
Workaround| Use the firmware update feature to update the BBU firmware.
Systems Affected| All systems supported by this release are configured with more than one BBU.
Tracking number| 292136

Table 45. The issue with SCP catalog import and staged jobs

Details:

Description| When combining staged and direct updates in the same SCP catalog import, the staged jobs are not updated.
Workaround| Update the iDRAC job separately instead of including it in the SCP catalog.
Systems Affected| All systems are supported by this release.
Tracking number| 288896

Table 46. Exporting GPU debug logs in TSR completes with errors

Details:

Description| The process of exporting GPU debug logs in the Technical Support Report (TSR) is encountering errors.
Workaround| This issue does not have any impact on the functionality as the current configuration does not support this option. Therefore, no workaround is required.
Systems Affected| PowerEdge XE9680 with NVIDIA HGX A100 8-GPU configuration.
Tracking number| 298771

Table 47. Numlock or Caps Lock key behavior issue in Virtual Console

Details:

Description| While accessing a server with ESXi OS through the iDRAC virtual console, if the Num Lock or Caps Lock is enabled before launching the virtual console, these keys may not function correctly.
Workaround| Perform any of the following:

●    Use the Shift key as a modifier for the alphabets and Number keys work as expected.

●    Disable and then re-enable Num Lock or Caps Lock for normal functionality.

Systems Affected| All systems are supported by this release.
Details:

Tracking number| 277106

Table 48. PSU Firmware Update Failure

Details:

Description| PSU firmware updates may fail when attempted repeatedly in short intervals.
Workaround| Reboot the iDRAC and then try updating the PSU firmware again.
Systems Affected| All systems are supported by this release.
Tracking number| 293225, 292902, 291999

Table 49. AMD GPU firmware update issue

Details:

Description| The AMD GPU firmware update fails, and the iDRAC shows firmware versions as 00.00.00.00 on the iDRAC firmware inventory page.
Workaround| Reboot the iDRAC or perform an AC cycle.
Systems Affected| PowerEdge XE9680
Tracking number| 286001

Table 50. Unable to upload iDRAC firmware using iDRAC GUI

Details:

Description| Problem encountered when attempting to upload iDRAC firmware through iDRAC GUI.
Workaround| Power off the system and attempt the IDRAC DUP upload.
Systems Affected| PowerEdge XE9680
Tracking number| 287729

Table 51. The server remains powered off after the CPLD firmware update

Details:

Description| Following a CPLD firmware update, the server persists in a power- off state.
Workaround| Run the RACADM command “job queue delete -i JID_CLEARALL_FORCE.”
Systems Affected| PowerEdge XE9680
Tracking number| 287537

Table 52. Missing GPU component entries in iDRAC Firmware Inventory

Details:

Description| Following an AC cycle, entries about NVIDIA H100 component versions are missing from the

iDRAC Firmware Inventory page. This prevents the accelerator firmware update from progressing, as H100 Baseboard Update Bundle registration is required.

Workaround| Resolve this issue by rebooting the iDRAC.
Systems Affected| PowerEdge XE9680
Tracking number| 285593

Table 53. Discrepancy in PSU Input Line Type

Details:

Description| The iDRAC GUI indicates “High Line” instead of “Extended High Line” for all PSUs, despite three being of the extended type and one of “High Line.”
Workaround| To ensure accurate configuration information, maintain consistency in the PSU types connected. If there are two different power supply types installed, remove the undesired PSU and perform an iDRAC reset.
Systems Affected| All systems are supported by this release.
Tracking number| 281269/282959

Table 54. PSU Type issue

Details:

Description| Servers equipped with 1400W power supply units (PSUs) of distinct hardware revisions, such as A01 and A02, exhibit a disparity in the iDRAC GUI. Specifically, the A02 PSU is presented as AC Type, while the A01 is indicated as DC Type.
Workaround| Use PSUs of the same A02 version.
Systems Affected| All systems are supported by this release.
Tracking number| 281279

Table 55. Failure in mapping images through RFS

Details:

Description| When using NFS/HTTP/HTTPS shares, the mapping of.IMG images through RF he in “Read-Write” maaree is encountering issues.
Workaround| Either use a CIFS share or opt for a lower version of NFS/HTTPS share to connect.IMG files using RFS in Read-Write mode. Note that, NFS version 4.1 and HTTPS with IIS version 10.0 for Windows are known to work for connecting.IMG files in Read-Write mode.
Systems Affected| All systems are supported by this release.
Tracking number| 277169

Table 56. VMAC reapplication issue after network card and BIOS updat es

Details:

Description| The VMAC fails to be reapplied following updates to the network card and BIOS.
Workaround| Perform the following:

For systems not in a failed state:

1.      Run the command racadm set iDRAC.PCIeVDM.Enable disabled.

2.      Perform a cold boot.

3.      Proceed with the required BIOS/NIC firmware upgrades.

For systems already in a failed state (i.e., without the PCIeVDM disabled- triggered firmware upgrade):

1.      Run the command racadm set iDRAC.PCIeVDM.Enable disabled.

2.      Perform a cold boot.

3.      Once again, perform a cold boot.

Systems Affected| All systems are supported by this release.
Tracking number| 278034

Table 57. Firmware update through iDRAC Group Manager failing

Details:

Description| iDRAC firmware update for Identity Module installed systems from iDRAC Group Manager fails with an error “Firmware is invalid for this platform”.
Workaround| Use other iDRAC interfaces to update the firmware.
Systems Affected| All systems are supported by this release.
Tracking number| 274746

Table 58. Few Virtual Keyboard keys work for other languages

Details:

Description| Some keys or key combinations may not provide the correct output for languages other than English.
Workaround| Use the physical keyboard or Windows On-Screen Keyboard.
Systems Affected| All systems are supported by this release.
Tracking number| 181505

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 the user can log in directly. This is because RSA is not applicable for AD-SSO, Active Directory smart cards, and local user smart card logins.

BIOS and UEFI

1. While performing BIOS Recovery operation all iDRAC resets are blocked and if an 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 the iDRAC IP.

iDRAC firmware

1. Modifying Power and Thermal Budget tables for the NVIDIA G6X10 FC card is only supported through IPMI commands. Therefore, after a system board replacement or if a System Erase operation is performed, the system fans may oscillate in an open loop.

2. The iDRAC GUI displays only one AMD Mi300x GPU instead of all eight on both the Accelerator and Cooling pages. The Getsensorinfo command in RACADM similarly results in displaying all the GPUs within a single slot. The number of GPUs detected can be viewed on the iDRAC GUI hardware inventory page, which retrieves data from the BIOS. Furthermore, the FRU-related information for the GPUs is not available in iDRAC; instead, it is displayed as “N/A.”

3. During a GPU firmware update, avoid any USB or USB-NIC operations (such as connecting to the USB management port, iDRAC quick sync operation, enabling or disabling USB-NIC port, or similar USB operations) in iDRAC, Any such operation during the firmware update can result in unpredictable behavior and may also result in a firmware update failure.

4. Avoid connecting to the USB port during iDRAC reboot or restart operations, as it may lead to unpredictable behavior.

5. In iDRAC, attaching a folder that is in an NFS share hosted by a Linux-based operating system is not supported. the

6. In Lthe lifecycle (LC) interface, It is recommended to avoid performing any operations on media that is mounted as RFS through iDRAC GUI/RACADM/Redfish.

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

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

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

10. For catalog updates through downloads.dell.com, adding catalog location or name is not required. Adding downloads.dell.com as an HTTPS Address enables iDRAC to find the appropriate catalog file.

11. If the Lifecycle controller logs display a RED057 message during a component update, then run the command system erase data through the RACADM interface and then retry the operation.

12. While performing a PSU firmware update through the host OS in the 15th or later Generations of PowerEdge servers, ensure that you perform a cold reboot to apply the update.

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

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

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

16. While performing a firmware update or rollback through the 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.

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

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

19. After updating the iDRAC license to the Data Center license, ensure that you reboot the iDRAC for the Idle server detection feature-related attributes to function.

20. In the LifeCycle Controller GUI, use the mouse to browse files or folders. Browsing files using the keyboard is not supported.

21. iDRAC GUI search output points to a GUI page where the search keywords are missing within the page. These are typically false positives like any other search engine that may be ignored.

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

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

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

25. 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 default secure protocols in WinHTTP in Windows:
    http://support.microsoft.com/kb/3140245/EN-US

26. 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:

27. a. You cannot update any DUP.

28. b. LC cannot involve CSIOR.
    However, if a server AC power cycle or iDRAC reboot is performed, the OEMDRV drive is automatically detached.

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

30. firmware rollback is not supported for CPLD, NVDIMM, SAS/SATA drives, and PSU (on modular systems).

31. When CMCs are daisy-chained, only the first CMC (CMC which is connected to the Top of the 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 the TOR switch directly.

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

33. After downgrading the iDRAC firmware to any previous versions, storage pages, and drives may display warnings. To resolve the issue, reset iDRAC using the ‘racreset’ command.

34. The Lifecycle Controller GUI features available on your system depend on the iDRAC license installed. The GUI help pages may display information about features that are not available with the license installed. For the licensed feature list, see the Licensed Feature section in the iDRAC User’s guide available at Dell.com/iDRACmanuals.

35. While performing a firmware update on a system where the operating system is installed with GNOME GUI enabled, the 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:

36. a. Go to Settings, and select Power.

37. b. For the option, “When the Power Button is pressed” select Power Off.

38. Lifecycle Controller supports ISO images with ISO-9660 format only. Other formats including combination with ISO-9660 are not recommended.

39. UserDefined delay AC Recovery Power Delay is slow with a 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 User-defined delay be set to 80 s or higher. Any values less than this may cause the operation to fail.

40. Install the 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 the SEKM-supported version, you have to reapply to SEKM-supported iDRAC firmware.

41. Key sharing between multiple iDRACs is supported and can be configured on the SEKM server. Key sharing can be done if all the ideas are part of the same SEKM group and all keys are assigned to the same group with the right permissions.

42. If system lockdown mode is enabled while a user is logged into LifeCycle Controller GUI, then lockdown mode will not apply to LifeCycle Controller.

43. Product Name for GPU may be displayed as Not Applicable if the product area data is not available on the GPU FRU chip.

Monitoring and alerting

1. The reporting format in SCV application version 1.92 has undergone a redesign. The iDRAC GUI reporting format is in alignment with SCV application version 1.91. Therefore, there may be variations in comparisons between SCV application reporting and iDRAC GUI.

2. When servers with SPDM-enabled components undergo an AC power cycle stress or a host reboot stress (cold or warm boot), the LC logs may show errors related to SPDM export issues. To address this, it is recommended to incorporate appropriate time intervals between consecutive power cycles. The time required for iDRAC readiness may differ based on the server configuration. The objective of these necessary time gaps is to ensure the full functionality of iDRAC and the completion of the Secured Component Verification (SCV) inventory before commencing the next stress cycle.

3. In iDRAC firmware version 6.00.30.00, Crash Video Capture is set to a disabled state by default. To enable it, perform the RACADM set command on the attribute

   • idrac.virtualconsole.CrashVideoCaptureEnable.

4. While updating a device firmware through the LC interface, Lifecycle logs may display RED032, RED096, and RED008 messages if the size of the image payload exceeds the available space in the firmware partition. To free up space in the partition, perform Systemerase by selecting the Lifecycle Controller data option in the System category and retry the update.

5. iDRAC displays an additional fan sensor for each installed dual-rotor fan. System fan slots that are blank or if a single rotor fan is removed from the system, iDRAC displays two sensors.

6. 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 the OS Collector application separately on the firmware inventory page.

7. Redfish Life Cycle Events (RLCE) do not support event generation for collection resources.

8. For staged operations that require a system reboot, after the system reboot is complete RLCE events for the operation may take up to 20 s depending on the system configuration.

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

10. While PERC inventory is in progress, Lifecycle controller logging may fail after a warm reboot by RTCEM for HBA, BOSS, or NVME drives.

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

12. 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 the iDRAC Lifecycle controller from either a failed state or a 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 a ready state before performing an iDRAC reset. To check the status of the services, run the command getremoteservicesstatus.

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

14. After any iDRAC reset event, including the iDRAC firmware update, the LC Log event time is incorrectly reported for a few events. This condition is momentary, and iDRAC time catches up to the correct time.

15. If you get an error while performing SupportAssist collection through RACADM using HTTPS share, use the following commands to perform the collection:

16. a. Racadm SupportAssist collect.
    racadm supportassist collect -t Sysinfo

17. b. Racadm SupportAssist exportlastcollection
    racadm support assist exportlastcollection -l -u -p

Networking and IO

1. During a DPU (Smart NIC) firmware update, the SUP0516 message about the firmware update is logged in Lifecycle (LC) Logs before the system restart log (SYS1000). The actual firmware update is applied at Post while the host system is powered on.
2. The firmware version for DPU cards on the iDRAC Overview page (Network Devices section) may vary from the version that is displayed on the Firmware Inventory page. Use the version that is displayed on the Firmware Inventory page.
3. iDRAC may display some unsupported attributes such as PCIeOfflineOnlineFQDDList, SerialNumber, PermanentMACAddress, CSP Mode, and DPUOSDeploymentTaskState for DPUs when GET is performed on the iDRAC attribute registry. These attributes are expected to be removed from the iDRAC code in an upcoming release.
4. iDRAC IPv6 auto-generated addresses change to stable-privacy assigned addressing when iDRAC is upgraded to firmware version 5.10.00.00 (or later) from any previous iDRAC versions.
5. In a SCP import job for enabling NPAR on a network port, if all partitions are not required then ensure that you apply the SCP import twice. Once to enable the NPAR on the port and the second time to disable the partitions that are not required.
6. For partition-enabled COMMs adapter, a PR6 Lifecycle Log message may be displayed as partition-1 even though the values are configured as other than the first partition.
7. When aauto-negotiationis disabled while iDRAC is in Shared LOM mode, the speed and duplex values shown in the GUI and RACADM output may not accurately show the actual speed and duplex on the link.
8. In systems with network adapters without internal temperature sensors, for some adapters t, the NIC temperature sensors metric value is reported as 0.
9. After iDRAC is upgraded to version 4. xx or later for the first time, there may be a change in network settings options including IPv4 and IPv6. Reconfigure the network settings to resolve this.
10. 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 the network settings page may not be displayed.
11. 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.
12. Fibre-channel NIC cards with dual or four ports are displayed as single-port port cards. However, all ports are updated when a firmware update is performed.
13. If SMBv2 share fails in Lifecycle GUI, ensure that:
14. The Digitally sign communications option is disabled.
15. Permission to access the folder or file is granted.
16. folder/file name does not have a space.
17. Share contains fewer files and folders.
18. While iDRAC is initializing, all communications with iDRAC may fail. For any service requests, wait until the initialization process is complete.
19. In iDRAC, if no link is detected in the selected iDRAC port then the iDRAC IP is displayed as 0.0.0.0.
20. FRU objects or properties for Network adapters that are embedded on the motherboard are not available through any of the iDRAC interfaces.
21. The iDRAC feature “Topology LLDP” is not supported on 1 GbE controller and on selected 10 GbE controllers (Intel X520, QLogic 578xx).

Automation — API and CLI

1. The display of the Intel IPU card’s PartNumber and SerialNumber in the PCIeDevice instance URI may vary with Redfish, as the Redfish interface does not support this card.

2. A compliance error in the Bios AttributeRegistry is flagged due to a deviation from the schema to accommodate Value Level dependencies of BIOS attributes in the implementation. This can be disregarded as there is no impact on functionality.

3. For Redfish OEM actions ExportLCLog and ExportHWInventory, the final job status message is not consistent across all supported network share protocols. When using NFS or CIFS share, the final job status message is “ was successful” and while using HTTP or HTTPS, the final job status message is “The command was successful”. To view what operation was performed, see the JobType property in the job ID JSON output results.

4. For Telemetry reports, if the RecurrenceInterval is set to a value lower than the metric SensingInterval a few extra reports may be generated when no data is available at the source. Ensure that RecurrenceInterval is greater than and a multiple of SensingInterval.

5. During an iDRAC stress test, if the number of user sessions exceeds eight, then iDRAC may display unexpected failures for Redfish operations.

6. Values for some properties may not reflect the same across different iDRAC interfaces, as there can be a delay in data refresh.

7. If you get a 400 status code while performing Redfish MultipartUpload for firmware updates, wait for five minutes and retry the operation again.

8. When streaming alerts using Remote Syslog or Redfish event listener, not every message ID/message gets streamed. To confirm which message ID/messages can be streamed, see the EEMI guide.

9. While accessing iDRAC GUI and Redfish through the same browser, if the web server times out, then RedfishService may prompt you to enter the login credentials to create a session. Select Cancel to clear the Redfish login prompt and proceed to the iDRAC login page.

10. For Telemetry reports through subscription, if there are more than two subscriptions, it is recommended to update the Metric Report Recurrence interval to above 60 seconds.

11. In Redfish API, all BIOS certificate-related operations are now supported using the new URI: /redfish/v1/Systems/
    {ComputerSystemId}/Boot/Certificates.

12. 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. The firmware version string format is denoted as xx.yy.zz, where zz is the secondary string.

13. You may get an irrelevant response message while performing the operating system method to Insert media with incorrect media for firmware upgradation or OS deployment.

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

15. iDRAC RESTful API with Redfish displays an error stating an unacceptable header specified in the request for commands that are run on PowerShell. Ensure that you include a header while using Powershell for any type of Redfish request.

16. Performing the GET method on steps only shows the next scheduled jobs and not the completed jobs.

17. Performing the Rethe fish Patch method on the Read-Only property for the PowerControl resource returns a 200 status code.

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

19. In RAthe CADM interface, using XML escape symbols such as < or > or & as AssetTag or as a substring in the AssetTag will be configured as regular characters that they represent.

Security

1. iDRAC v5.10.00.00 adds an enhanced security check for accessing iDRAC using a hostname. To access iDRAC using a hostname, ensure that you configure the hostname through the attribute idrac. webserver.ManualDNSEntry
   ( racadm set idrac.webserver.ManualDNSEntry kos2-204-i.datadomain.com).

2. Setting Custom Cypher String with TLS version 1.3 is not supported.

3. Accessing iDRAC through OpenManage Enterprise Modular SSO may fail if iDRAC is configured with a short FQDN. Ensure that you configure iDRAC with full FQDN that includes a Hostname with a Domain name.

4. 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:

5. a. You cannot update any DUP.

6. b. LC cannot involve CSIOR.
   However, if a server AC power cycle or iDRAC reboot is performed, the OEMDRV drive is automatically detached.

7. CPLD firmware update has no impact on Trusted Platform Module enablement.

8. Ensure that the SSH client is updated to the latest version. Following SSH configurations are no longer available on iDRAC: KEX algorithms:

   • a. diffie-hellman-group14-sha1
     MAC:

   • a. sumac-64

   • b. umac-64-etm@openssh.com

9. In the software inventory, the hash value for iDRAC firmware is displayed as NA instead of a hash.

10. Install the 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 the SEKM-supported version, you have to reapply the SEKM-supported iDRAC firmware.

11. If you are configuring a Gemalto-based KeySecure SEKM Server with iDRAC, and to get the redundancy feature functional, copy the certificates manually from the primary Gemalto KeySecure cluster to the secondary Gemalto SEKM KeySecure cluster. The redundancy feature works after the iDRAC is set up for SSL certificate-based authentication.

12. When FCP is enabled, the ‘Default Password Warning’ setting is disabled after the default user password is changed.

13. For enhanced security, keyboard-interactive authentication is enabled on the iDRAC SSH Server. SSH clients now require keyboard-interactive authentication before logging a user into iDRAC.

14. After upgrading or downgrading the iDRAC firmware, ensure that you review the version of the TLS protocol that is selected on the Web Server Settings page.

Storage

1. The standard erase process for non-instant Secure Erase (ISE) drives may require a significant amount of time. For larger drives, this process could potentially extend to hours or even days.
2. Servers with NVMe drives with different firmware versions and configured through a PERC may display PR36 messages in Lifecycle logs during the boot process.
3. Reports about the drives that are not certified by Dell may not be included in the Telemetry reports.
4. PatrolReadRate property is deprecated and not supported from iDRAC firmware version 5.10.25.00 and the later releases. Setting PatrolReadRate using SCP is not supported.
5. While encrypting VDs through the Lifecycle controller, ensure that the first VD in the list is selected. Selecting a VD that is already secured does not affect the existing encryption of the VD.
6. Before performing SecureErase on a vFlash, ensure that the partitions on the vFlash are detached.
7. Intel ColdStream NVMe devices do not support cryptographic erase. For more information, see Intel’s documentation for the specific device.
8. Creating a RAID using the selected controller is not supported through the Lifecycle Controller interface. Use iDRAC GUI to create the virtual disk, then relaunch the Lifecycle Controller and retry the deployment operation.
9. Before deleting a VD that hosts the OS, ensure that you uninstall iSM. If a VD is deleted without uninstalling iSM, the LC log may display the error: “ISM0007 The iDRAC Service Module Communication has ended with iDRAC”.
10. 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 the BOSS controller and not connected to the backplane.
11. SMART monitoring is disabled for a hard drive while it is set to Non-Raid mode.
12. 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.
13. The option to enable or disable the disk cache policy for SWRAID controllers is supported only on SWRAID controller driver version 4.1.0-0025 or later.
14. If any of the NVMe drives report a ‘Failed’ status (Red LED) due to any of the 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:
15. a. Available spare threshold
16. b. Reliability degraded
17. c. Read-only mode
18. d. Virtual memory backup failed, and so on.
19. For improved support on drives and operating system deployment, it is recommended to use the UEFI BIOS boot mode.
20. 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.
21. Firmware updates 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 a cold reboot is not done.
22. The iDRAC Virtual Keyboard labeling is changed to upper case to align it with the physical keyboard layout.

Miscellaneous

1. iDRAC may take about 15 to 20 minutes to display information about GPUs, network cards, DIMMs, or other components depending on the system configuration. It may display stale data for these components if a system reboot is performed multiple times in a span of 5 to 10 minutes. Perform an iDRAC reboot to clear out the stale data.
2. The host OS may display an incorrect folder size of the folder that is attached through remote file sharing.
3. Virtual Console and Virtual media may not function on Safari browser while iDRAC is set to use TLS version 1.3. Ensure that browser settings are updated to TLS 1.2 or below.
4. Configuring Power Factor Correction (PFC) for power supplies in all 15th generation of PowerEdge systems is not supported.
5. While BIOS is set to Boot mode, the boot capture video file size is limited to 2 MB. During the video capture, if the size of the video file exceeds the limit, then only partial operation is captured.
6. CPLD update may fail if the DUP method is used while the power cap policy is enabled.
7. Remote File Share (RFS) through HTTP is only supported without authentication.
8. If part replacement is performed on systems with two PSUs while the upgrade option is enabled, then the firmware update for both PSUs is repeated once.
9. Arrow keys on the virtual keyboard of the iDRAC Virtual Console with eHTML5 plug-in do not respond inside the BIOS boot manager after the system reboots. Close and reopen the eHTML5 Virtual console session.
10. If the SOL session is active for a long duration or if the system is rebooted multiple times, the SOL session gets terminated automatically.
11. For Dell’s online catalog update, downloads.dell.com only supports the https protocol.
12. If you install OMSA while iSM is already installed and connected, iSM may restart after the OMSA installation is complete.
13. In SLES and RHEL, the native video players do not support the MPEG-1 video formats. To play the captured videos, install an MPEG decoder or a video player that supports this format.
14. You may experience frame loss or drift in frame rate in the boot or crash capture videos due to iDRAC memory constraints.o

Limitations

Authentication

1. LC supports the following characters for username and password:
2. Alphabets (a-z, A-Z)
3. Numbers (0-9)
4. Special characters (-, _, .)
5. 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 the error GMGR0047. Use the web interface (iDRAC Settings > Users) to verify the number of iDRAC local users.
6. If the user does not exist on a specific iDRAC, Group Manager Jobs for Change User Password and Delete User show a failure with the error GMGR0047. Use the web interface (iDRAC Settings > Users) to verify that the user exists.
7. LDAP bind password does not accommodate password hashes; it solely supports clear text. Consequently, no password hash is supported for any SCP export. Additionally, there is no mechanism to retrieve the password in clear text through SCP, or any retrieval method through Redfish or RACADM. Users are responsible for managing their passwords.

Automation — API and CLI

1. The configuration result, such as the result for the SCP configuration operation, has a limit of 32 KB. If the result surpasses this limit, certain configuration details may not be visible in the output of the Configuration result.
2. Attempting to enable SEKM for PERC 12 through a staged configuration job using the Redfish interface results in failure. Try SEKM activation for PERC 12 through the Redfish interface by using a real-time configuration job.
3. For a newly created job, Redfish may display a 404 error if you perform a Get method to see the details for the job. Wait for about ten seconds and try performing the Get method again.
4. Sometimes, when using WSMan, an Internal SSL Error is reported and the WSMan command fails. If this issue occurs, retry the command.
5. 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.
6. RACADM supports the underscore character (_) for iDRAC.SerialRedirection.QuitKey along with the existing symbols shown in the integrated help.
7. 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.
8. 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. Following an AC cycle or iDRAC reboot, when the host is turned off, the “GPU Baseboard Update Bundle” component may not be listed on the Firmware Inventory page until the host is powered on.
2. In LC, not all the vendor FC cards are supported for VLAN configuration.

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 the 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 the iDRAC web interface.

5. The iSCSI offload attribute can be enabled only on two of the four available ports. If a card, that 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 the 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.

7. a. Open Group Manager on one of the member iDRACs.

8. b. In the search box, type the controlling system’s Service Tag.

9. c. Double-click the iDRAC that matches the search results and go to iDRAC Settings -> Diagnostics.

10. d. Select Reset iDRAC.
    When iDRAC fully restarts, Group Manager should see the new iDRAC.

11. If Emulex LightPulse LPe31002-M6-D and Emulex LightPulse LPe35002-M2 FC adapters are configured to boot from FC storage arrays using the VAM method in iDRAC, then a maximum of two boot target arrays can be configured instead of the eight.

12. During the import server profile operation, if the image filename is “Backup. img”, the operation may fail. To avoid this failure, change the filename.

Monitoring and alerting

1. After a system cold reboot, the corresponding Unlock event for Boss Drives getting unlocked is not generated in iDRAC Lifecycle (LC) Logs. To verify if the BOSS drives are successfully unlocked and secured, see the BOSS Drive Secure State in the iDRAC GUI or run the RACADM command racadm storage get disks -o.
2. Operating system crash capture and last crash screen are not supported for all Linux-based operating systems such as RHEL, SLES, Ubuntu, ESXI, and Cent operating systems.
3. In certain cases, the Group Manager Jobs view may not show a detailed error message for a member’s 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 clog view.
4. 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.
5. If the LCD is blank, press any one of the three LCD buttons to turn on the LCD before inserting a USB storage device.
6. 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.
7. The inventory displayed in LC UI may not be the same as that of any iDRAC interface. To get the updated inventory, run the CSIOR, wait for 2 minutes, reboot the host, and then check the inventory in LC UI.
8. In certain cases, in the 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.
9. While running the 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.
10. 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.
11. IDRAC supports iSM version 3.4.1 and above.
12. 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. When multiple NICs are configured for the first time, and the first configured NIC port stops responding or shuts down, then any operation over the network from Lifecycle Controller GUI using FQDN may fail from all configured NICs. Before trying any operation over the network in LC GUI, ensure that you reboot the host when the first configured NIC goes down.

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

4. When NPAR is enabled, the port numbers displayed on the LC Network Settings page (Settings > Network Settings) do not match the port numbers displayed on the Device Settings page (System Setup > Advanced Hardware Configuration > Device Settings).

5. When Virtualization Mode is set to NPAR for network adapters that support the partitioning feature, the PartitionState attribute can only be used for checking the state of partitions created for base partition in WSMan enumeration. You can see the states of all the partitions by pressing F2 during POST and going to Device Setting.

6. The process of retrieving the IPv6 address from the DHCP server with a VLAN connection takes a few minutes. Wait for a few minutes and check the Network Settings page to view the assigned IPv6 address.

7. Network operations such as Update, Export, or Import may take more time than expected. The delay may occur because the source or destination share is not reachable or does not exist, or due to other network issues.

8. LC does not support SOCK4 proxy with credentials.

9. LC UI supports shared names and file paths that are up to 256 characters long. However, the protocol you use may only allow shorter values for these fields.

10. Because of internal UEFI network stack protocol implementation, there may be a delay while opening the LC UI Network Settings page or while applying the network setting.

11. Before performing any network operations, verify that the network is configured with the network cable connected. In some scenarios, a warning message may not be displayed but the operation may fail. Following are some examples that may lead to failure:

12. Static IP is configured without the network cable being connected.

13. The network cable is disconnected.

14. After a Repurpose and Retire operation is performed.

15. The network is configured with the network cable connected but the network card is replaced later.

16.  Any changes to the network settings in iDRAC take effect after 30 seconds. Any automation or user verification needs to wait for 30 seconds before verifying the new settings. iDRAC returns the old active value until the new values take effect. Any DHCP settings may take more time (>30 seconds) depending on the network environment.

17. When trying to save network details using the Network Configuration page of LC UI, the following error message may be displayed: Unable to save the IPvX network settings, where X is the version of IP (IPv4 or IPv6). The following could be one reason for this error: On the Network Settings page of Lifecycle Controller GUI, the IP Address Source for both IPv4 and IPv6 is either DHCP or Static and DHCP is selected by default. So, even if you want to use only one version of
    IP address, LC tries to validate both versions and displays an error if the network details for the unintended version cannot be validated. If the error does not apply to the IP version you are using, click OK to close the error message. All the other settings that you configured are saved. You can either click Cancel or Back to navigate away from the Network Settings page.

18. If the Gateway IP is not configured in a network, the network settings and operations in LC UI may show some unexpected behavior.

OS deployment

1. Operating system installation fails when the OS media volume name (label) is blank. The recommendation is to add a valid volume name for OS media (USB drive, DVD, and so on) before starting the OS installation.

2. While installing an operating system, a media verification warning message may be displayed. This has no impact on the installation, to proceed, click Yes.

3. Windows operating system deployment may intermittently fail with the following error message:

   • A required CD/DVD drive device driver is missing. If you have a driver floppy disk, OS deployment CD, DVD, or USB drive, please insert it now.
     Reboot to LC and retry until the operating system is successfully deployed.

4. 4. Deployment of Windows Server operating systems (OS) using LC may fail with one of the following messages:

   • Windows installation cannot continue because a required driver could not be installed

   • Product key required

   • Windows cannot find the software license terms
     This issue occurs when the Windows setup copies the driver to the scratch space (X: drive) and the scratch space becomes full. To resolve this issue, do any of the following:

   • Remove all the installed add-on devices before starting the OS installation. After the OS installation is complete, connect the add-on devices, and manually install the remaining drivers using Dell Update Packages (DUPs).

   • To avoid physically removing the hardware, disable the PCle slots in the BIOS.

   • Increase scratch space size beyond 32 MB using the DISM set-scratch space command when creating a customized deployment. For more details, see Microsoft’s documentation.

5. LC may display multiple drive names for some CDs or DVDs, such as the ones containing operating systems.

6. If the operating system (OS) selected for installation and the OS on the media used are different, LC displays a warning message. However, while installing Windows OS, the warning message is displayed only when the bit count (x86 or x64) of the OS does not match. For example, if Windows Server 2008 x64 is selected for installation and Windows Server 2008 x86 media is used, the warning is displayed.

7. In Windows10, the HTML5 plug-in does not support Virtual media connection on the following versions of Edge browsers:

   • a. Microsoft Edge 44.17763.1.0
   • b. Microsoft EdgeHTML 18.17763

Security

1. Cryptographic Erase operation is not supported for hot-plugged NVMe disks. Cold reboot (power cycle) the server before starting the operation. If the operation continues to fail, ensure that CSIOR is enabled and that the NVMe disk is qualified by Dell.

Storage

1. iDRAC interfaces do not support slicing RAID volumes through software RAID controllers. To configure sliced RAID volumes, use F2 Device settings.
2. The part number for the Predictive failure message “For the NVMe drive may appear as “Not Available” immediately after the cold reboot. Allow sometime after the cold reboot for iDRAC to initialize the inventory.
3. While renaming a virtual disk (VD), using a . (period) is not allowed in the VD name.
4. If your system has a PERC card configured in Enhanced HBA mode and you downgrade iDRAC to an older version, the SET commands for storage configuration may fail. To resolve the issue, ensure that a Collect System Inventory On Reboot (CSIOR) is performed after the downgrade. To perform a CSIOR, use the following methods:
5. a. Completely turn off the system and then turn it on again.
6. b. Ensure that CSIOR is enabled before turning off the system.
7. c. Use the following RACADM command: racadm server action power cycle
8. Few legacy drives do not support the SMART ID #245 “Remaining Rated Write Endurance”. In such cases, iDRAC interfaces may display the “Remaining Rated Write Endurance” attribute as unavailable.
9. If an M.2 SATA drive attached to the BOSS-S2 controller is removed, performing a blink operation may not fail for the removed drive.
10. The standard erase procedure for non-ISE drives is notably time-consuming, particularly for larger drives, potentially spanning hours or days, with the added risk of job failure. A workaround is to conduct the erase on each disk individually while other drives are uninstalled.

SupportAssist and parts replacement

1. Part-replacement of the BOSS-S1 controller is not detected by the Lifecycle Controller. After replacing the controller, follow the instructions in the controller’s documentation.

Firmware and driver update

1. In PowerEdge systems with AMD configuration, if a PSU firmware update is initiated from LCUI, the host goes into a powered-off state, and the Job is Completed with a status of 0%. Ensure that you power the system using any iDRAC interface to start the PSU firmware update.
2. CMC server component update does not support the iDRAC9 firmware packages. Use iDRAC GUI, RACADM interface, or OpenManage Enterprise Modular to perform any out-of-band updates of iDRAC9 firmware.
3. After an iDRAC reset or firmware update operation, the ServerPoweredOnTime—a property in RACADM and WSMan—may not be populated until the host server is restarted.
4. Some of the supported components may not be displayed on the Firmware Update > View Current Versions page. To update this list, restart the system.
5. If the iDRAC firmware update is interrupted, you may have to wait up to 30 minutes before attempting another firmware update.
6. Firmware update is supported only for LAN on Motherboards (LoM), Network Daughter Cards (NDC), and network adapters from Broadcom, QLogic, and Intel, and some of the QLogic and Emulex fiber channel cards. For the list of supported fiber channel cards, see the Lifecycle Controller User’s Guide available at iDRAC Manuals.
7. After the CPLD firmware is updated on modular systems, the firmware update date is displayed as 2000-01-01 on the View Current Versions page. The update date and time are displayed according to the time zone configured on the server.
8. On some modular systems, after a firmware update, the Lifecycle Log displays the timestamp as 1999-12-31 instead of the date on which the firmware update was performed.
9. It is not recommended to perform CPLD updates along with other updates. If a CPLD update is uploaded and updated along with other updates using the iDRAC web interface, the CPLD update completes successfully but the other updates do not take effect. To complete the iDRAC updates, reinitiate the updates.

Miscellaneous

1. You may be unable to scroll using the keyboard. Use the mouse to scroll.
2. Due to a limitation of the Google Chrome browser, the HTML5 virtual console intermittently displays the following error message: Chrome ran out of memory while trying to display the webpage.
3. When accessing the iDRAC web interface for the first time using Google Chrome version 59.0, the mouse pointer may not be visible. To display the mouse pointer, refresh the page or use Google Chrome version 61.0 or later.
4. If you use the HTML5 plug-in on Chrome version 61.0 to access Virtual Console, you cannot connect to Virtual Media. To connect to Virtual Media using the HTML5 plug-in, use Chrome version 63 or later.
5. Launching Virtual Console with Java plug-in fails after the iDRAC firmware is updated. Delete the Java cache and then launch the virtual console.
6. A Serial-On-Lan (SOL) session that has been active for more than five days or multiple reboots may get terminated automatically. If the session terminates, you must reinitiate the session.
7. Due to an issue with Safari, if an ipv6 literal address is used to log into the Web GUI, Safari is not able to launch the HTML5-baconsolesole. Alternative options are to use Java-based vConsole, or HTML5 vConsole by using the corresponding DNS name or by using an alternate browser in Mac OS.
8. iDRAC login page does not allow password entry using the Firefox browser in Ubuntu management OS.
9. iDRAC and LC features cannot access CIFS or Samba shares when only the SMBv1 protocol is enabled. All iDRAC features work with SMBv2 protocol. For information on enabling SMBv2 protocol, see the documentation for your operating system.
10. In Lifecycle Controller GUI, using the keyboard to browse folders and files is not supported. Use the mouse to navigate through files and folders.
11. When accessing iDRAC through a Safari web browser version 14.0.3 and later versions, if a page refresh is attempted using the browser refresh option, then the iDRAC session may get cleared and you may get redirected to the iDRAC dashboard page. To refresh the page, use the Refresh option available on the iDRAC console.

Environmental 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 XE9680

Supported managed server operating systems and hypervisors

• SALES
  • SLES 15 SP4
• Ubuntu
  • Ubuntu 22.04

Supported web browsers

• Microsoft EDGE
• Safari 17
• Mozilla Firefox 122
• Mozilla Firefox 121
• Google Chrome 123
• Google Chrome 122IU

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.
• Dell makes no express warranties and disclaims all implied warranties, including merchantability, fitness for a particular purpose, title, and non-infringement as well as any warranty arising by statute, operation of law, course of dealing, or performance, or usage of trade regarding Adopt Open JDK.
• Dell has no liability to you for any damage that arises out of or relates to your use of Adopt Open JDK.

iDRAC Service Module (iSM)
iSM version 5.1.0.0 or later

iDRAC tools
This version of iDRAC requires the following tools based on the operating system:

• Dell iDRAC Tools for Microsoft Windows Server(R), v11.1.0.0
• Dell iDRAC Tools for Linux, v11.1.0.0
• Dell iDRAC Tools for VMware ESXi (R), v11.1.0.0

This version contains:

• Remote/Local RACADM on Windows or Linux or ESXi
• IPMI Tool on Windows or Linux
• Secured Component Verification (SCV)

Download the DRAC tools from the Drivers & downloads page for your system on the Dell Support page.
Before installing iDRAC tools from OM 9.5.0, you must uninstall any older versions of DRAC tools. For more information about uninstalling applications, see the documentation for your operating system.

Supported Key Management Server (KMS) for Secured Enterprise Key Manager (SEKM)

• CipherTrust Manager version 2.11.1
• IBM Security Guardium Key Lifecycle Manager version 4.1.1.0
• Utimaco Enterprise Secure Key Manager version 8.4.0
• Thales Data Security Manager (DSM) version 6.4.9
  NOTE: Thales ended support and reached end-of-life for the Gemalto SafeNet KeySecure key management server (k150v) on December 31, 2023. Additionally, Thales will discontinue support and end the life of the Data Security Manager (DSM) on June 30, 2024.

Installation and upgrade considerations
Downloading the iDRAC firmware installation file

NOTE: For information about updating iDRAC firmware using various interfaces, see the iDRAC User’s Guide available at iDRAC Manuals.

1. Go to the Dell Support page.
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. 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 the 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 7. xx.

Latest Release Notes
To access the latest Release Notes for this version of iDRAC:

1. Go to the iDRAC manuals page.
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:

Table 59. Direct links for documents

Controller
CMC Manuals| Chassis Management Controller (CMC)
ESM Manuals| Enterprise System Management
Software Serviceability Tools| Serviceability  Tools
Client System Management Manuals| Client System Management

Accessing documents using the product search

1. Go to the Dell Technologies Support site.
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 the Dell Technologies Support site.

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.
   NOTE : For some products, you may need to navigate through the subcategories.

5. Click DOCUMENTATION.

6. Click MANUALS AND DOCUMENTS.

Lifecycle Controller (LC) Remote Services — client tools

Redfish API
For information about Redfish, see the DMTF website DMTF Redfish. This website provides access to schema files, white papers, technical notes, and so on.
For the iDRAC Redfish API guide, go to the Dell Developer Portal.

iDRAC Attribute Registry
For information about iDRAC attributes, go to the Dell QRL Site,

1. Click Look Up,
2. Select iDRAC Attributes,
3. Select the appropriate attribute group.
4. Enter the attribute name.
5. Select the attribute from the suggested list for quick access to relevant details.

Where to get help

• The Dell Technologies Support site contains important information about products and services including drivers, installation packages, product documentation, knowledge base articles, and advisories.
• A valid support contract and account might be required to access all the available information about a specific Dell Technologies product or service.

Notes, cautions, and warnings

• NOTE: A NOTE indicates important information that helps you make better use of your product.
• C AUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.
• WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2024 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.

FAQ

• Q: How can I check the current version of iDRAC on my server?
  • A: You can log in to the iDRAC interface and navigate to the System Overview section to view the current version information.
• Q: Is it necessary to update this release if my system is working fine with the current version?
  • A: While not mandatory, Dell recommends applying updates to ensure compatibility with other system modules and to benefit from feature enhancements.

References

• FTP Root
• Dell Technologies Developer

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>