Unsolved
This post is more than 5 years old
2 Intern
•
5.7K Posts
0
7600
January 14th, 2011 03:00
How can I safely reset the PowerPath config ?
I'm sure PPath might be only part of the solution, but the thing I'm facing is that a particular HPUX host sometimes looses 1 path which won't come back automatically. A reboot always helps.
I've advised to make sure that the FCID as well as the domain id are set to fixed.
A colleague of mine asks whether he can use the following procedure to remove all LUN's from PowerPath and get them all back again:
Remove all devices.
[root@srv1] / # powermt remove dev=all
Get the devices back
After a rescan of the disks with ioscan and the creation of the device files with insf run the following command to make sure the disks return to PowerPath
[root@srv1] / # powermt config
PPath is version 5.1.0.
RRR
2 Intern
•
5.7K Posts
0
February 10th, 2011 04:00
I see this on both hosts:
*** HP-UX Patch checks ***
WARNING : None of the Fibre Channel Mass Storage Patch patches are installed on this host. Consider installing the latest patch .
*** Patch bundle checks ***
NOTICE : HP-UX 11i v3 Feature11i version B.11.31.0903.334c installed on this host.
WARNING : HP-UX 11i v3 Feature11i version B.11.31.0903.334c is older than the latest version B.11.31.1009.353a.
NOTICE : HP-UX 11i v3 HWEnable11i version B.11.31.0903.334d installed on this host.
WARNING : HP-UX 11i v3 HWEnable11i version B.11.31.0903.334d is older than the latest version B.11.31.1009.353a.
NOTICE : HP-UX 11i v3 QPKBASE version B.11.31.0903.334a installed on this host.
WARNING : HP-UX 11i v3 QPKBASE version B.11.31.0903.334a is older than the latest version B.11.31.1009.353a.
NOTICE : HP Patch Bundle revisions may be downloaded from http://itrc.hp.com/.
And Powerpath is 5.1.1 and I know 5.1.2 is out there.
Could the above noted patches be the resolution ? Should I upgrade PPath to 5.1 SP2 as well or is SP1 just fine ?
SKT2
2 Intern
•
1.3K Posts
0
March 5th, 2011 15:00
I had gone thorugh the fixed problems on the release notes, no such things listed there. Also dont have V3 hosts so far, so no comments on the patch side. But it is always possible to have a newer version of patch available especially when you patch the servers once in an year, like my case.
RRR
2 Intern
•
5.7K Posts
0
March 9th, 2011 04:00
The customer now updated his HPUX hosts, but the problem still exists. Once we have a path failure, PowerPath doesn't bring the bad path bad online when it should be up and running again. VMware and Windows hosts don't have this issue.
christopher_ime
2K Posts
1
March 22nd, 2011 20:00
RRR,
If you suspect a PowerPath configuration issue, do you know if support ran the host grab through the PowerPath Configuration Checker (PPCC)? It is avialable via the following breadcrumb trail:
Home > Support > Product and Diagnostic Tools > Environment Analysis Tools > PowerPath Configuration Checker (PPCC)
There is a short PDF describing the tool available from the following location:
Home > Support > Technical Documentation and Advisories > Software ~ P-R ~ Documentation > PowerPath Family > PowerPath > Installation/Configuration
If you have just one host grab, it can be as simple as running but of course have a quick scan of the README and the PDF:
ppcc.exe -i
Just a thought.
RRR
2 Intern
•
5.7K Posts
0
March 23rd, 2011 02:00
Hey guys, thanks for all the tips and hints. The solution was to update the HPUX OS itself. PPath was ok.
We sent EMCGRABs to EMC and EMC came up with a few patches and commands that needed to be performed.
Bottomline: keep your OS up to date and do what the EMCGRABs tell you to do.