PowerFlex Software

This article provides links to PowerFlex software documentation.

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.

Generating a PowerFlex license fails when using the UI's 'Installation ID'.

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

Using PowerFlex Manager Deployment or Upgrade will fail in Diskless nodes due to the backplane. When performing deployments on diskless Compute Only (CO) nodes, if the backplane shows as non-compliant PFxM attempts to upgrade and it Fails.

This article explains using the Boot Optimized Storage Solution - S2 (BOSS-S2) configuration utility to import a foreign virtual disk, a feature only when the controller detects a foreign disk.

The guide explains converting a hard drive to non‑RAID by iDRAC, then claiming it for a PowerFlex Virtual Storage Area Network (VSAN) cluster and assigning cache or capacity roles.

The user is checking performance using FIO (also seen with vdbench) and reports high latency during a rebuild.

This article explain how to fix the restore operation failure when password is not encoded as mentioned in the admin guide

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.

After successfully unmapping, a volume from an SDC the corresponding block device (/dev/sciniX) is still visible on the SDC side. This problem can occur when PowerFlex 3.6 SDC is installed in a PowerFlex cluster running an older version of the code (3.5, 3.0.x, etc.)

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

ESXi SDC crashes with PSOD.

LIA Authentication field resulted in Invalid while performing "Retrieve system topology" from Gateway/Installation Manager's Maintain tab.

This article provides instructions on how to check the vm.overcommit_memory and vm.overcommit_ratio settings and how to modify the settings to match best practices.

Top PowerFlex Software and Hardware Dial Home Alerts; PowerFlex

This article explains the step by step procedure to restore PFMP from a backup file

Unable to clear alert after PowerFlex Appliance deployment

Memory errors and CMCI storm entries in logs cause load, SDS stalls and decoupling; a failing Dual In-line memory module (DIMM) triggers interrupts, EDAC CMCI rate exceeds threshold, causing storm.

RestAPI calls to collect volume statistics sometimes fail with Error 500.

SDCs disconnect from SDSs under heavy read IO load.

This KB explains how to perform the WSFC conversion at a high-level. It also covers converting an Oracle RAC environment from RDMs to shared VMDKs on NVMe/TCP, even though Oracle RAC does not require SCSI3‑PR. Oracle RAC can run on an SDC‑based VMFS datastore, but because PowerFlex does not support Clustered VMDK on SDC‑based VMFS, SCSI3‑PR‑dependent applications cannot use that configuration. Oracle RAC explanations are also high-level.

The customer is using PowerFlex SDR replication to test failover but the destination volume gets mounted "RO" in the multipath -ll output on the Oracle Linux server.

PFxM was initially linked to a PowerFlex system, but at a certain point, the PowerFlex system was either removed or deleted.

After adding a new SDS to the PowerFlex cluster, and rebalancing data to the new SDS, some SDCs show I/O errors

PowerFlex 3.x UI is inaccessible, receive a 404 error when trying to open it. PowerFlex 3.x is reachable from the CLI.