PowerFlex rack HW

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Datacenter Infrastructure 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.

This article provides links to PowerFlex software technical documentation.

Nodes are failing to PXE boot during deployment when Intel X710 NICs are present.

Even though the VLT enabled topology provides a loop-free environment in the VLT domain, some non-VLT member ports can end up in a loop scenario. Rapid spanning tree protocol (RSTP) and rapid per-VLAN spanning tree+ (RPVST+) modes of spanning tree protocol in VLT are supported to provide a solution for this scenario. Depending on the network topology, the primary node of the VLT domain can be designated as the root bridge.

Dell Virtual Link Trunking allows Layer 2 information to be shared across the two nodes. For this purpose, the same VLT domain-id should be configured on both VLT nodes. For rapid convergence and optimal service, the same VLT MAC address should be configured on both the nodes using the vlt-mac command (optional). In the absence of vlt-mac configuration, if the primary VLT node goes down, the VLT port channel on the secondary node flaps, causing slight traffic disruption.

Compute Only node upgrade fails with the error BIOS_FIRMWARE_TYPE WARNING: Legacy boot detected ESXi servers running legacy BIOS are encouraged to move to Unified Extensible Firmware Interface (UEFI)

This article explains how to Resynchronize a Compliance file or OS repository that is in an error state.

Procedure to update firmware to mitigate an issue of NVDIMM batteries losing charge on PowerFlex Rack and Appliance (R650, R750) nodes.

This article explains how to Standardizing Data VLAN Tagging After PFxM Upgrade and OS Conversion.

If a user attempts to deploy multiple volumes that exceed the available space, the request may not be blocked by PowerFlex Manager. If it is not blocked, the deployment fails and the volumes are in an error state.

By default, 14G SO nodes are configured to go to sleep to save power when idle. In the sleep state, when PowerFlex Manager issues IOs the response time is impacted while it wakes up. It is possible to set a parameter that does not allow the CPU to go to sleep but that setting will revert back to the default after a service upgrade.

This article explains when it is safe to ignore PowerFlex UI non-compliance when hardware component updates are necessary. The compliance flag in PFxM is a best-practice target matrix. If support and engineering guide the customer community to update hardware to fix issues in the field, such as stated in a KB article, Dell Technical Advisory (DTA), or Dell Security Advisory (DSA), deviation is allowed, supported, and acceptable.

Explore the Dell End of Service Life (EOSL) and End of Life (EOL) list for converged infrastructure, storage, and storage networking products. Access End-of-Life documents for hardware, software, and firmware release and service dates

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.

Deployment of a CO service with PowerFlex Manager 3.6 or later with Intelligent Catalog 36_360_A02.zip may result in having some nodes be noncompliant. The Micron M.2 SATA devices for the BOSS card have firmware E003 instead of E012.

PFxM-3.5.1-5539 with 13G HC and SO services backed up and restored to 3.7.0-7773 loses the cached network connectivity data for 13G nodes. After the restore, the 13G SO service goes into a critical and error state.

PowerFlex Manager installs operating systems during new service deployment or node expansion with Partial Network Automation using iDRAC virtual media. Sometimes when LACP networking is used with Dell OS 10 switches OS installation failures can be seen depending on the switch cabling used.

Node credentials can be changed from the Resources page of PowerFlex Manager. As many nodes as wanted may be selected and updated, but if too many are selected it could cause timeout issues.

In PowerFlex Manager, a disruptive service upgrade fails if the SVM name in vCenter does not match its hostname.

Switch discovery fails if "enable" password is required to activate configure commands.

This article gives the procedure to locate a conflicting/duplicate IP and resolve it by removing the conflicting/duplicate IP.

During deployment, an existing SO service failed with the message "Could not connect to the SDS xxx over SSH due to a timeout. (VXFM00665)" All connectivity between PFxM appliance, gateway, and gateway to SDS data IPs is working and manual SSH was working.

This article describes about how to expand a service when all networks are not mapped to the service.

The host is stuck entering maintenance mode for a long time with no error.

PowerFlex: How to soft reset iDRAC 13G &14G

After upgrading the PowerFlex Management Platform from 4.0.0-161 to hotfix 4.0.0.1-169, the Resource Group Compliance Report shows no software components in the PowerFlex Manager UI.

PowerFlex Manager Platform (PFMP) crashes after restarting network services using "systemctl restart network."

When deploying a Storage-Only Resource Group on PowerFlex 5.x, the deployment wizard fails at IP reservation with error IDENTITYPOOLMANAGER.3004. The root cause is IP pools sized only for the storage nodes, without accounting for the additional MDM virtual IPs required by the deployment.

PowerFlex After the Motherboard is replaced, the node shows R740xd not VxFlex-R740xd in iDRAC.

This article provides links to PowerFlex rack technical documentation.