PowerFlex Software

戴尔为我们的许多硬件系统提供了客户可更换部件 (CRU) 计划。CRU 计划允许客户更换指定的硬件组件。有关为特定硬件系统指定为 CRU 的硬件组件的列表，请转至戴尔保修和维护页面。

本文档重点介绍 Dell Technologies 企业和数据中心基础架构产品的最低代码版本、建议代码版本和最新代码版本。戴尔会仔细评估和监控代码部署数据，以确保产品版本符合我们严格的期望，从而为客户提供可靠的产品和解决方案。

在 PowerFlex 组件的手动或 PFMP SVM 转换和手动升级期间，如果 rep_tgt.txt 文件未正确创建，SDS 可能会持续失败。

本文介绍如何在 4.x PFMP 环境中修改（删除/添加）DNS 服务器，其中 MVM 节点运行 OS SLES 15 及更高版本。

本文是 PowerFlex 数据块子系统PFX000XX的警报参考指南。XXXXXXX

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.

ESXi 上的 PowerFlex 设备记录以下错误：设备“eui.xxxxxxxxxxxxxxxxx”的 IEC 页面代码错误：0x0”

在 PFxM UI 中，有一则警报，指出未收到来自 MDM 的事件。

在 PFxM UI 中，有一个警报，指出未检索来自 MDM 的事件。

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.

本文详细介绍了更改 ESXi 主机 root 密码的三种方法;vSphere Client、ESXi shell 或 System Customization。本文还详细介绍了如何更新 vCenter 管理员密码。

如何查找 ScaleIO 卷上的磁盘空间使用情况和可用空间。

SO 资源组部署失败，并显示异常“RuntimeError：VxFlex 组件 scaleio-block-legacy-gateway 没有可用于构建的成功服务器。

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

添加卷时，用户会在屏幕截图中看到错误，即数据块组件缺少数据。

本文介绍如何在 ESXi 环境中为 SDS 和 MDM 更改工作 ScaleIO 群集中的 IP 地址。

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

如何更换 PowerEdge 服务器或 PowerFlex 设备中的 NVDIMM。

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