PowerEdge R470

Unsure about the procedure to update a specific component's firmware in a PowerEdge system? Learn how to in this specific article.

The article describes how to troubleshoot network connectivity issues for network cards.

This article shows how to use and set up the virtual media function of Integrated Dell Remote Access Controller (iDRAC) 6, 7, 8, or 9.

This article shows how to add additional disks to a virtual disk or reconfigure a virtual disk.

PowerEdge Server catalogs are an aggregation of all bundles and Dell Update Packages' metadata used by Dell OpenManage Repository Manager, Dell OpenManage Enterprise, and other tools for listing the current versions of software and firmware for respective servers and devices.

iDRAC Service Module (iSM) stops after several days, showing "Not Running" and logging ISM0007 warnings. The issue is caused by exceeding the 20‑temporary‑user limit, which triggers session cleanup.

This article provides links to download Dell trial 30 and 90-day evaluation license collection including iDRAC Enterprise, iDRAC Datacenter, Chassis Management Consoles (CMC) Enterprise, OpenManage Enterprise, and OpenManage Integration.

This document highlights minimum, recommended, and latest code versions for Dell Technologies PowerEdge products. We carefully evaluate and monitor code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.

PowerEdge 17th Generation Servers with Delta Power Supplies may not show correctly in iDRAC UI and SEL logging after AC cycle.

Dell PowerEdge servers with common design components are grouped into generations, for example PowerEdge 17th generation servers, 16th generation, 15th generation, or 14th generation. This article provides general guidance for PowerEdge server model naming convention to identify the generation and common components. This article also lists all PowerEdge servers by model including type, CPU, generation, and remote management components.

This article explains what disk errors PDR1001 and PDR3 mean on Dell PowerEdge servers and the best practices to resolve these issues. By understanding these alerts and acting promptly, you can maintain storage health, prevent downtime, and protect critical data.

How to Identify the physical slot number in iDRAC based off the device name in vSphere/VSAN.

This article explains the requirements to deploy VMware ESXi 9 virtual machines with 4Kn end‑to‑end (E2E) storage when using Dell PowerEdge PERC12 (H965) and newer controllers. It also covers how to identify when ESXi is using 4Kn software emulation (SWE) instead of true 4Kn E2E, and what conditions prevent E2E.

This article provides some checklist to prevent unnecessary components replacement on DC power supply implementation.

The BIOS setting changes may not appear in iDRAC if configured using the F11 Boot Manager on Dell PowerEdge 16G and 17G platforms.

The CTL137 event is new to iDRAC code 4.xx.xx.xx. The CTL137 event exist to notify the end user that the iDRAC lost communication with an endpoint device within the system.

This article provides steps to troubleshoot a chassis intrusion, chassis open message for PowerEdge servers.

After BIOS update on a 17G system, the Max Speed field in the System Management BIOS (SMBIOS) differs from the Central Processing Unit (CPU) spec because it reports capability, not turbo rating.

Kioxia CM6 NVMe SSDs on 17‑generation servers experience I2C (Inter‑Integrated Circuit) communication issues. The fan speed stays locked at 100 % after OS boot. This behavior is observed on 17G servers only running Integrated Dell Remote Access Controller (iDRAC) 10 firmware version 1.20.80.51 or older.

This article provides a high‑level guide to downloading vendor‑specific firmware and drivers for common PowerEdge NICs such as NVIDIA, Broadcom, and Intel. These processes complement Dell Update Packages (DUPs) and are used when vendor‑specific firmware or drivers are required beyond Dell’s updates.

PowerEdge servers do not support operating system installation, or boot from direct CPU‑attached NVMe SSD drives if the metadata format size is not set to 0.

PowerEdge connected Dell NVMe SSDs with the Limited Retry (LR) bit set may experience an increase in failures due to elevated media and data‑integrity error rates.

Servers can stop during POST at Configuring Memory.

PowerEdge 14G, 15G, 16G, and 17G servers skip Preboot eXecution Environment (PXE) boot when an "Unavailable" entry is last in the boot order.

Fans reporting FAN0000/FAN0001 errors (RPM below warning or critical) should be removed and swapped to another connector; if the error follows the fan, replace it.

Dell PowerEdge 17G servers added MEMHOT error monitoring in iDRAC10 firmware version 1.20.80.50 combined with supported Field-Programmable Gate Array (FPGA) firmware. Servers configured with Power Supply Cold Redundancy feature enabled can record random SYS565 memory temperature warning events.

On Dell PowerEdge 17G servers using Broadcom 5719 QP OCP NX1 cards (DPN M2PYY), firmware installation fails when Secure Boot is enabled on SUSE Linux Enterprise Server (SLES). Additionally, the installed firmware version is not detected by the Operating System (OS). Disabling Secure Boot allows the firmware to install and be detected correctly.

Dell PowerEdge 17G servers record inaccurate CPU index within iDRAC10 life cycle Log (LCLOG) and System event log (SEL) when machine check event (MCE) is recorded.

Dell PowerEdge 17G Intel servers may record memory module temperature warning events in the Lifecycle Log and System Event Log during the server cold boot sequence.

Dell PowerEdge Toshiba MG08 and MG09 hard drives may encounter uninterruptible Background Media Scanning (BMS), causing I/O errors, or timeouts.