PowerFlex rack RCM Software

This article provides links to PowerFlex software technical documentation.

This article provides links to PowerFlex rack technical documentation.

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.

This article explains what disk errors PDR1001 and PDR3 mean on Dell PowerEdge servers and the best practices to resolve these issues. By understanding these alerts and acting promptly, you can maintain storage health, prevent downtime, and protect critical data.

Deployment of a CO service with PowerFlex Manager 3.6 or later with Intelligent Catalog 36_360_A02.zip may result in having some nodes be noncompliant. The Micron M.2 SATA devices for the BOSS card have firmware E003 instead of E012.

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.

PowerFlex Manager installs operating systems during new service deployment or node expansion with Partial Network Automation using iDRAC virtual media. Sometimes when LACP networking is used with Dell OS 10 switches OS installation failures can be seen depending on the switch cabling used.

Node credentials can be changed from the Resources page of PowerFlex Manager. As many nodes as wanted may be selected and updated, but if too many are selected it could cause timeout issues.

In PowerFlex Manager, a disruptive service upgrade fails if the SVM name in vCenter does not match its hostname.

Switch discovery fails if "enable" password is required to activate configure commands.

This article gives the procedure to locate a conflicting/duplicate IP and resolve it by removing the conflicting/duplicate IP.

During deployment, an existing SO service failed with the message "Could not connect to the SDS xxx over SSH due to a timeout. (VXFM00665)" All connectivity between PFxM appliance, gateway, and gateway to SDS data IPs is working and manual SSH was working.

This article describes about how to expand a service when all networks are not mapped to the service.

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

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."

Procedure to update firmware to mitigate an issue of NVDIMM batteries losing charge on PowerFlex Rack and Appliance (R650, R750) nodes.

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.

The MDM reports device errors from an SDS, but the SDS or DAX device in question is being used by the cluster and is healthy.

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

UI pages load slowly during normal navigation.

SDS devices are missing data after reboot.

This article provides PowerEdge server troubleshooting for No Power, No POST, No Boot and No Video issues. This includes blade, rack, and tower servers.

This article explains the procedure to perform a clean Shut Down or Startup of a PowerFlex system running in ESXi or Two Tier Environment.

This KB provides a high-level procedure for removing a network/VLAN from PowerFlex Manager and a PowerFlex Rack and PowerFlex Appliance environment. PowerFlex Manager will not remove network/VLAN configurations implemented in VMware vCenter or network switches when deleting a network within the PowerFlex Manager UI. Modifying configurations in these components will be a manual effort.

User wanted to remove data IP of obsolete network from Cluster Use in Single node Cluster.

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

An LDAP-enabled user gets a "no role assigned to user" error when making API calls.