PowerFlex Software

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.

PowerFlex Management server default port 8443 is blocked and the site cannot be reached.

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.

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

A partial network configuration service failed because none of the nodes could export their system configuration file.

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.

MDM login does not work with LDAP authentication on Ubuntu 16.04 and higher, with PowerFlex 3.5 and higher.

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

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.

This issue may occur when "Add Resource" > "Add Node"/Node Scale Up operation is performed shortly after a "Remove Resource"/Node Tear Down. "Add Node"/Node Scale Up operation expects all server facing data interfaces for the nodes in the service to be 9216.

If PowerFlex Manager cannot find encrypted paths for some node drives in CloudLink for a service where "Encryption" is requested, the service fails.

The amount of time that it takes to complete a Rebalance is erratic.

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

Some data is unavailable to clients following SDS disconnection and reconnection

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.

Unable to run ScaleIO command, error: "MDM failed command. Status: Invalid session Login and try again."

The OS does not recognize a disk after adding it back into a server.

This article provides links to several Dell Community pages.

ElasticSearch Data corrupted or locked is commonly due to storage being full. /var is where Elasticsearch data is stored.

All the masking view information is visible in SYMCLI. The customer is unable to see the masking view information for all local arrays. Within Unisphere, none of the array masking view details are visible.

SDS devices are missing data after reboot.

PowerFlex Upgrade Customer Preparation Guide