PowerPath VE 5.8 causes vSphere 5.5 Hosts a PSOD

PowerPath VE 5.8 causes vSphere 5.5 Hosts a PSOD

Yes, its the Powerpath version 5.8 caused the vSphere 5.5 Hosts a PSOD.


As you can see the PSOD screen it is pointing to the Power Path issue. When investigated, going through the PSOD, VMKernel Logs its the Powerpath which was the culprit for the PSOD.

Now, why the Powerpath thrown the PSOD?

Its because the EMC PowerPath/VE release which was not compatible with the version of vSphere we have it installed that is vSphere 5.5. Here is the compatibility Matrix that I collected from the VMware KB: kb.vmware.com/kb/1019844

Why installed the version which is not compatible with the vSphere 5.5?



Yep, that's the right question asked!! why was the Powerpath version installed when its not supported on vSphere 5.5. To answer this question, need to explain the environment. We had the hosts already running with the vSphere 5.1 and with the powerpath 5.8 installed, and as a upgrade project we had our hosts upgraded vSphere 5.5 and the Powerpath plugin was missed to install during the upgrade project. As a result of this miss, we had our ESXi hosts going for the PSOD Screen. The Host shows that the Powerpath 5.9 version is missing



Here is what we did to fix this?

1. We have Downloaded and Installed the PowerPath/VE 5.9 from here and created the basesline in VMware Update Manager to push the Powerpath through update Manager. 
2. Then we have registered the Powerpath instances installed on the ESXi hosts to the Powerpath License server
3. Since we have upgraded the existing version of the Powerpath 5.8 to powerpath 5.9, the management server "RTOOLS" runs outdated and we installed the updated one. RTOOLS upgrade was needed to support Powerpath 5.9 management options.

 How to Install the Powerpath using the Update Manager?

Create a new extension baseline containing the PowerPath/VE software.

• In the Update Manager Administration view, click the Baselines and Groups tab.
• Click Create above the Baselines pane to start the New Baseline wizard.
• Use the wizard to create a new host extension baseline that contains PowerPath/VE.

Attach the extension baseline to the host or container object that you want to remediate.

• In the vSphere Client navigation bar, select Home > Inventory > Hosts and Clusters.
• In the Update Manager Compliance view, select the ESX/ESXi host or container object to which you want to attach the extension baseline.
• Click Attach.
• In the Attach window, attach the extension baseline to hosts.

Scan the hosts against the extension baseline.

• In the Update Manager Compliance view, right-click the ESX/ESXi host or container object and select Scan for Updates.
• In the Confirm Scan window, verify that the Patches and Extensions check box is selected.
• Click Scan.

To install or update PowerPath/VE on ESX/ESXi hosts, remediate the hosts against the extension baseline.

• In the Update Manager Compliance view, click Remediate.
• Use the Remediate wizard to apply the PowerPath/VE extension to ESX/ESXi hosts in your inventory.

 Step 2: Download and install the latest version for the RTOOLS package to support 5.9 version.

Step 3: Register the Powerpath

rpowermt register host=192.168.1.1



Reference:

 http://www.emc.com/collateral/TechnicalDocument/docu49354-PPVE-VM59-4-1-14.pdf

http://www.emc.com/collateral/software/white-papers/h6340-powerpath-ve-for-vmware-vsphere-wp.pdf