- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Alternate path to disks not working
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2006 01:10 AM
07-14-2006 01:10 AM
We have an HP 11.11 system attached to an IBM 8300 Shark SAN. The disks are recognized and working fine. When I do a vgdisplay the disks are there and the alternate path as well. When I tested the alternate path (unplugged the primary path FC cable) it did not fail over. So it seems that the alternate path is not working. It could be setup incorrectly by the SAN folks, but I have to exhaust all options on my end first. I just installed the IBMsdd (just to test if I need IBM software to make it work) but have no idea how to use it or what to do with it to set it up. If anyone can help, that would be great.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2006 01:19 AM
07-14-2006 01:19 AM
SolutionHOw long did you wait for the PV to failover ? the default PV timeout is 60 secs. But if you have set it to any longer, then it will take longer for LVM to detect the PV failure and failover.
Can you post the output from the following commands ?
vgdisplay -v | grep dsk
dmesg | grep -i lvm
Sundar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2006 01:35 AM
07-14-2006 01:35 AM
Re: Alternate path to disks not working
do the alternate pathes show up on an IPL search command?
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2006 02:03 AM
07-14-2006 02:03 AM
Re: Alternate path to disks not working
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2006 03:30 AM
07-14-2006 03:30 AM
Re: Alternate path to disks not working
LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000481e8000), from raw device 0x1f210100 (with priority: 0, and current flags: 0x0) to raw device 0x1f110100 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000481e8000), from raw device 0x1f110100 (with priority: 1, and current flags: 0x0) to raw device 0x1f210100 (with priority: 0, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000481de000), from raw device 0x1f210000 (with priority: 0, and current flags: 0x40) to raw device 0x1f110000 (with priority: 1, and current flags: 0x0).
LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000481e8000), from raw device 0x1f210100 (with priority: 0, and current flags: 0x40) to raw device 0x1f110100 (with priority: 1, and current flags: 0x0).
LVM: VG 64 0x010000: PVLink 31 0x04c600 Failed! The PV is still accessible.
LVM: VG 64 0x010000: PVLink 31 0x04c500 Failed! The PV is still accessible.
LVM: VG 64 0x010000: PVLink 31 0x210000 Failed! The PV is still accessible.
LVM: VG 64 0x010000: PVLink 31 0x210100 Failed! The PV is still accessible.
LVM: VG 64 0x010000: PVLink 31 0x04c600 Recovered.
LVM: VG 64 0x010000: PVLink 31 0x04c500 Recovered.
LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000481de000), from raw device 0x1f110000 (with priority: 1, and current flags: 0x0) to raw device 0x1f210000 (with priority: 0, and current flags: 0x80).
LVM: Performed a switch for Lun ID = 0 (pv = 0x00000000481e8000), from raw device 0x1f110100 (with priority: 1, and current flags: 0x0) to raw device 0x1f210100 (with priority: 0, and current flags: 0x80).
LVM: VG 64 0x010000: PVLink 31 0x210000 Recovered.
LVM: VG 64 0x010000: PVLink 31 0x210100 Recovered.