PowerPath for AIX

A slow blinking amber light showing internally from the switch model DS6620B-V2, not from the switch panel, is confirmed by Brocade to be the LED from the eUSB card (on the motherboard).

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

This article explains the procedure to open a Service Request (SR) using the Dell support page. Get help fast for your Dell device. No more waiting on hold. No more tech headaches. Dell makes it simple to fix problems, schedule repairs, or get support—right from your device or our support website.

Although the Operating System is correctly discovering all the paths of the device, PowerPath is missing one path.

This article explains Dell guidelines on company administrator assignment.

This article explains how to assign an Initial Company Administrator.

This article explains how to promote Company Administrators.

This article displays a list of Dell Software Products and related articles on how to obtain the Software Unique ID (SWUID) for each specific product. The SWUID is required for streamlining the processes related to both the Software License Renewal process and opening a Support Case.

There can be different reasons for PowerPath not to pick-up a path and the most common reason is a "reserve_policy" mismatch between the hdisk and the pseudo device ... but insuch a case, the pseudo device remains "defined" since PowerPath doesn't know which reserve_policy needs to be applied to the pseudodevice. Here, both the hdiskpower and the leftover hdisk are available, resulting into a duplicate PVID issue (same PVID on the pseudo-device as the one on the leftover hdisk).

Is the Windows PowerPath Viewer application supported for use with the new PowerPath Linux vAPP?

This article explains the solution when the PowerPath command powermt display stops responding in an AIX VIOS environment.

PowerPath for AIX is causing an unexpected host reboot everyday around midnight after an installation of (or an upgrade to) PowerPath 7.0 or PowerPath 7.0 P01.

PowerPath IBM AIX ODM reserve lock attributes not converting to reserve_policy.

PowerPath 6.0 (or earlier) is installed and configuring VMAX devices fine. However, after upgrading to PowerPath 6.1, configuring devices is failing with no error message. The devices are not configured for PowerPath and no pseudodevice is created.

PowerPath cannot run powermt command in AIX host

PowerPath for AIX 6.4: powerdd: MpxPeriodicCallbackDaemon race condition crash

In an NPIV configuration with two virtual HBA, when one virtual HBA goes down, and although there is one path left for the I/Os, LVM_IO_FAIL are logged in errpr with ERROR CODE AS DEFINED IN sys/errno.h set to 22 (EINVAL). Because of these LVM errors, the application using the volume crashes. The issue could also occur in a non NPIV environment.

Write are failing from time to time, leading to an LVM error (LVM_IO_FAIL - EWRPROTECT) for no obvious reason, as if the device was "write protected." The error was reported as: "AIX shows disk operation error on array with PowerPath. No error showed in the array…."

How to install ODM definitions on IBM AIX for EMC Symmetrix

Following a Powerpath upgrade, VTD with VMAX3 devices backing devices remain defined.

When PowerPath for Windows version 6.1 is installed on Windows Server 2016, validation alerts indicate that many drivers have dates earlier than the OS, because the PowerPath release predates the OS.

After the installation of Windows 2016, all the connected SAN disks are visible, but as soon as Powerpath 6.1 is installed, the SAN disks disappear in the Disk Management and PowerPath is not able to show the disks. This only happens after the first installation of PowerPath.

powerpath migration enabler 6.2 reported PPME(error 22)Target faulted, must abort migration when attempting PPME migration in 4 node cluster

Customer had an issue AIX Power 7 running PowerPath 6 booting from Unity 400F . They where unable to successfully upgrade the boot image on the SAN,but could upgrade it to the internal disk. PowerPath was uninstalled before the upgrade on the SAN disks..

Path failures and reserve conflict errors noted

This article explains how to uninstall PowerPath 5.7 SP1 on the cluster node where it says migrations are pending.

Kernel panics may occur on Red Hat Enterprise Linux (RHEL) 7.x systems running PowerPath for Linux version 6.3 in conjunction with Symantec software (VRTSvxvm any version) may result in data unavailability.

Server hung while PPME migration was in progress at which TargetLUfault errors are received in powermig info.

With PowerPath 6.4 for AIX, the emc_reserve_v3.sh script fails with "PowerPath version Version not >= 5.5".

In an AIX environment, rootvg is being migrated with NDM. Following the cutover, rootvg becomes "read-only" so that the system stops responding and must be rebooted.