PowerFlex Software

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Data Center Infrastructure products. Dell carefully evaluates and monitors 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 documentation for PowerFlex Rack, PowerFlex Appliance, PowerFlex Custom Node, VxFlex Ready Node, PowerFlex Software, PowerFlex for AWS, PowerFlex for Azure and CloudLink.

This article explains how to modify (remove/add) DNS servers in a 4.x PFMP environment with the MVM nodes running OS SLES 15 and higher.

This guide catalogs PowerFlex Block alerts for subsystem PFX000XX.XXXXXXX, detailing each alert code, description, severity level and potential system impact without providing remediation steps.

This article shows how to use PuTTY to enable session logging and perform the appropriate show tech‑support commands on Cisco Nexus or PowerSwitch switches, capturing logs and CPU data for analysis.

System Configuration Reporter (SCR) for PowerFlex provides reports, health readiness assessments for 3.x‑to‑4.x upgrades, and logs for troubleshooting, downloadable from the PowerFlex portal.

In the PFxM UI, there is an alert stating that events from the MDM are not being received.

PowerFlex devices on ESXi are logging following error: "IEC page to device "eui.xxxxxxxxxxxxxxxxxxxxxxxxx" has bad pagecode: 0x0"

The UI shows a UNABLE_TO_RECEIVE_MDM_EVENTS alert because the manager cannot reach the ActiveMQ broker on port 61714; the broker is blocked or the service is down, so MDM events are not displayed.

Use this procedure to verify and upgrade the CPLD firmware version on PowerFlex nodes. PowerFlex Manager does not verify or upgrade CPLD.

Use the procedures in this section to upgrade the Cisco Nexus switches from NX-OS 9.3.x to NX-OS 10.x.

Details the graceful reboot of PowerFlex Management Platform (PFMP) VMs for version 4.X, including labeling, draining, and rebooting MVMs while keeping two nodes active and checking PostgreSQL health. In the scope of this procedure, MVM1 is the postgres Leader. It is drained and rebooted last.

This article details three ways to change the ESXi host root password; by vSphere Client, ESXi shell, or System Customization. The article also details how to update the vCenter admin passwords.

How to find the disk space usage and free space on the ScaleIO volume.

A SO resource group deployment fails with an exception - 'RuntimeError: VxFlex component, scaleio-block-legacy-gateway, does not have a successful server to build with'.

Dell PM1735a NVMe (Non-Volatile Memory Express) drive failing in PowerEdge servers

While adding a volume, the user sees the error in the screenshot, which is that the block component is missing data.

This article explains how to change the IP Addresses in the working ScaleIO Cluster for SDSs and MDMs in ESXi Environment.

This article will explain the differences between a rebuild and a rebalance.

This article explains how to troubleshoot the dial home alert SDC_MULTIPLE_DISCONNECTIONS_FROM_SDS -SIO01.07.0000007

This article explains how to reclaim space on the Management Virtual Machine (MVMs).

Client servers are experiencing I/O errors against PowerFlex-backed devices. The overall backend (MDMs and SDSs) appears to be healthy. PowerFlex replication is active, and RPO errors are affecting one or more RCGs.

On AIX, a volume group built on PowerFlex (scinid) disks does not vary on at boot and its filesystems do not mount. The root cause is a boot-order race: the PowerFlex Storage Data Client (SDC) enumerates the scinid block devices only after the network is up and the SDC connects to the MDM (about two minutes into boot), which is later than AIX's automatic vary-on and mount pass. The fix is to disable auto vary-on and auto-mount for the affected volume group, then bring it up from a small, bounded post-network script sequenced after the SDC daemon. This article assumes the scini parent device already comes up at boot; if it does not, resolve that first (see the companion article on the cfgscini log path).

After every reboot of an AIX LPAR running the PowerFlex Storage Data Client (SDC), the scini device is not configured automatically and the PowerFlex disks are missing until cfgmgr is run by hand. The root cause is the predefined-device (PdDv) cfgscini log directory pointing to /opt, which is not yet mounted at rc.boot phase 2, so the cfgscini device method fails with return code 11. Relocating the log directory to /var (a filesystem mounted at phase 2) restores automatic configuration of the scini device at boot. This is a boot-time configuration issue only; it is not caused by ODM corruption or an invalid client GUID.

This article explains how to troubleshoot the issue of being unable to exit service mode during a gateway upgrade.

This article explains how to troubleshoot error code MEM9037

This article explains how to troubleshoot events PFX00001.0704001 PFX00001.0704002 PFX00001.0704003 PFX00001.0704004

This article explains how to troubleshoot the alert PFX00102.0000207 - The PowerFlex management platform message bus health diagnostic failed.

When an Operating System (OS) replacement is performed from Community ENTerprise Operating System (CentOS) to SUSE Linux Enterprise Server (SLES) using the "Replace Node OS" operation, any preconfigured static routes are removed automatically.

SDS devices have errors stating "Device has fixed read errors"