PowerFlex custom node HW

Information about customer replaceable unit (CRU) videos for Dell Technologies VxFlex Ready node products

This article contains information about customer replaceable unit (CRU) videos for Dell Technologies VNX and VNXe products.

Information about customer replaceable unit (CRU) videos for Dell Technologies PowerProtect and Data domain products

Information about customer replaceable unit (CRU) videos for Dell Technologies Powerflex products

Information about customer replaceable unit (CRU) videos for Dell Technologies ECS products

PowerEdge servers crash with PCIe fatal errors while updating Kioxia CM6 NVMe drive firmware.

When trying to register or de-register Alert Connector, PFxM UI shows error (500) or (VXFM0004)

Dell Samsung Serial Attached SCSI (SAS) PM1653 and PM1655 solid state drives may report excessive Sense Key faults 0x3, 0x11, 0x0, or 0x4, 0x29, 0x4. These faults have the potential to cause unexpected drive issues.

This article contains the initial steps to take on all PowerFlex performance-based issues when observing performance degradation, low Input Output Operations Per Second (IOPs), low MB per sec, or high latency.

Article outlines symptoms where PowerFlex nodes report “Non‑Volatile Dual Inline memory module (NVDIMM) battery not ready” during boot, after outage, or on install, caused by batteries left uncharged.

User has one node in the system where the NVDIMM battery status reports as 'Unknown' but that is not one of the three options listed for the status.

PowerFlex components such as the MDM are disconnecting and reconnecting quickly and frequently. Lost connection followed by connected found in MDM events Connecting after 80-190ms

How to clear device errors on Dell PowerFlex using Presentation Server

In SLES15, the service name was changed to "sdc", from the commonly used service name "scini".

Attempting to upgrade the PowerFlex Production or MDS Gateway resource fails stating that it could not connect to LIA on a specific IP address.

PowerFlex versions 3.0.1.6, 3.5.1.4, and 3.6.0.2 and lower have a bug that causes the rotation mechanism of the eventlog.db file to not work at all, which causes a continuous increase in the file size.

This article describes the basic steps required to collect support data from a Kubernetes-based PowerFlex Manager Platform (PFMP) system and the PFMP installer. Support data is collected using a standalone, single-file utility, pfmp_support. As such, the utility's executable can be copied to and run on the host from which support data is to be collected. Using this utility does not require a functioning PFMP. As such, support data can be collected during PFMP installation or when the PFMP UI is inaccessible.

This procedure describes how to add another IP address subnet for use by the MDM cluster. This addresses scenarios where the MDM cluster uses a single network, or when an existing network must be replaced by a different one or to simply add another network (to an already multiple-network cluster). The MDM supports up to eight networks.

The guide explains that devices may show error notifications within PowerFlex version 3.6, typically caused by hardware or communication faults, requiring the errors to be cleared from the UI.

Retrieve the OS device paths in a Linux-based or ESXi based SVM server PowerFlex system with NVMe devices configured.

Retrieve the OS device path for a specific virtual drive (VD) in a Linux-based, Windows, or ESXi running PERCCLI server PowerFlex system with an H730p/H740p controller.

Configure network throttling to control the flow of traffic over the network.

Collecting logs using the Installation Manager (Gateway) times out and fails on SDCs running on ESXi v7.x.

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

The ScaleIO Data Server (SDS) panics at startup, producing stack traces and causing a single‑point‑of‑failure state; a Security-Enhanced Linux (SELinux) rule set is suspected, on version 3.5.1.1.

PowerFlex upgrade from 3.6.0.6 to 4.5.2 fails, logs show “Failed to fork wrapper” and “Get Installed Components command was not successful” on nodes, caused by low memory and vCPU resources for SVMs.

Storage‑Only Resource Group (RG) deployment fails with missing MDM IPs, connection timeouts and ARP errors; the cause is unconfigured port channels required by Partial Network Automation (PNA).

Upgrade is blocked because a decommissioned vCenter remains in a compute‑only resource group on PFxM 3.6, preventing PowerFlex Management Platform from complying with the intelligent catalog.

The Collects Logs feature collects the logs from all the system nodes although only a few were selected.

The PowerFlex Gateway upgrade operation fails to upgrade the MDM cluster.