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.

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.

Initial copy progress is stuck. Sometimes, it might succeed to reach 100% completion for small volumes, while large volumes failed to complete the initial copy.

Oracle ASM fails to load and errors with ORA-00600 while drv_cfg times out on Powerflex volumes.

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

While performing a Replication Consistency Group (RCG) Switchover or 'Test Failover', the command completes successfully without any error, but the PowerFlex UI, the Presentation Server (PS), shows an alert.

Datastore reclaim is not freeing space on PowerFlex OS thin volumes either automatically or through manual means.

The article explains how Kubernetes supports the PowerFlex Management Platform, covering containers, Pod, services, namespaces and controllers like Deployment and StatefulSet within a PFMC cluster.

Installation of SDC version 3.6.0.4 fails on Windows hosts.

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.

Attempting to modify a storage pool's journal capacity shows a greyed‑out button; the issue stems from a UI flaw that only enables the control after replication traffic refreshes the pool view.

Unable to collect PFxM 4.x Troubleshooting Bundle. Log collection Job automatically ends in 60 seconds.

After daylight‑saving time shift, the management UI cannot be reached because Keycloak issues a token that is wrongly considered invalid, impacting a small number of clusters with active jobs.

This section provides the PowerFlex Manager 3.X compatibility details for PowerFlex rack components.

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.

Retrieve the OS device paths in a Linux-based or ESXi based Storage Virtual Machine (SVM) server PowerFlex system with an HBA330 controller.

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

User may encounter a static route configuration error when attempting to re-add an existing HCI Resource Group to PowerFlex Manager. This issue prevents the successful addition of the resource group and can block planned upgrades

get_info.sh - collect diagnostic information from a PowerFlex host and pack it into a support bundle

After MDM switchover, SDSs cannot reconnect and MDMs crash.

SDS gets decoupled - the system might experience DU occasionally if more than one SDS decouples concurrently or in case the SDS decouples during a rebuild.

When a vMotion clone of a VM guest is submitted, it takes a lot longer than expected. Scenario Due to an environmental configuration issue, there was contention on the vMotion configured NICs that conflicted with iSCSI and VxFlex SDC traffic, causing reduced performance.

SDS fails to start up.

After restart of ESXi/SVM, the SDS comes up but is in a disconnect state in the UI/CLI.

After following NDU flow and switching to 1_node MDM cluster, upgrading Secondary/TB MDMs and trying to put the back into the cluster, MDM throws an error.

Upgrade will not start/finish the Finalize step, since the MDM is shown in an upgrade state in progress.