HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Alternate path for SAN boot disk
Operating System - HP-UX
1827612
Members
3360
Online
109966
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
03-01-2007 05:15 AM
03-01-2007 05:15 AM
Alternate path for SAN boot disk
Hi,
We have an Integrity SuperDome connected to an XP from which we have two LUNs each presented over two fabrics to the server.
Using xpinfo I can clearly identify my primary and alternate paths to these LUNs and I have device files for them all. Obviously one of the disks is the boot disk and has a cxtyd0s2 device file. The alternate path for this disk does not have the s2 device file.
I can't see any option in insf for creating this and believe this is the device file I should be using to vgextend for my pv link. The alternate path for the other LUN is fine btw.
Can anybody shed some light on how I can correctly set a pv link for my Itanium server SAN boot disk?
** We're not mirroring and obviously I do not want to destroy my boot disk by misconfiguring the alternate path :-)
Thanks.
We have an Integrity SuperDome connected to an XP from which we have two LUNs each presented over two fabrics to the server.
Using xpinfo I can clearly identify my primary and alternate paths to these LUNs and I have device files for them all. Obviously one of the disks is the boot disk and has a cxtyd0s2 device file. The alternate path for this disk does not have the s2 device file.
I can't see any option in insf for creating this and believe this is the device file I should be using to vgextend for my pv link. The alternate path for the other LUN is fine btw.
Can anybody shed some light on how I can correctly set a pv link for my Itanium server SAN boot disk?
** We're not mirroring and obviously I do not want to destroy my boot disk by misconfiguring the alternate path :-)
Thanks.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2007 06:08 AM
03-01-2007 06:08 AM
Re: Alternate path for SAN boot disk
Hi,
since the alternate path is refering to the same disk, the device files must be the same.
All boot disks for Integrity systems have a layout like
cxtydzs1
s2
s3
(for HP-UX11iv2) or
diskx_p1
diskx_p2
diskx_p3
for 11.31
Please run
xpinfo -il
to find the pathes and device files and compare them to your vgdisplay output to find the correct device.
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!
since the alternate path is refering to the same disk, the device files must be the same.
All boot disks for Integrity systems have a layout like
cxtydzs1
s2
s3
(for HP-UX11iv2) or
diskx_p1
diskx_p2
diskx_p3
for 11.31
Please run
xpinfo -il
to find the pathes and device files and compare them to your vgdisplay output to find the correct device.
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
03-01-2007 06:56 AM
03-01-2007 06:56 AM
Re: Alternate path for SAN boot disk
minor correction:
the devicefile is not really the same, but it looks the same, e.g.
c1t2d3s1
c1t2d3s2
c1t2d3s3
and
c10t2d3s1
c10t2d3s2
c10t2d3s3
You will see this in your xpinfo output, e.g.
Device File ALPA Tgt Lun Port CU:LDev Type Serial#
================================================================================
/dev/rdsk/c1t2d3 c9 00 01 CL2E 01:ed OPEN-V 00080xxx
/dev/rdsk/c10t2d3 e1 00 01 CL1E 01:ed OPEN-V 00080xxx
...
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!
the devicefile is not really the same, but it looks the same, e.g.
c1t2d3s1
c1t2d3s2
c1t2d3s3
and
c10t2d3s1
c10t2d3s2
c10t2d3s3
You will see this in your xpinfo output, e.g.
Device File ALPA Tgt Lun Port CU:LDev Type Serial#
================================================================================
/dev/rdsk/c1t2d3 c9 00 01 CL2E 01:ed OPEN-V 00080xxx
/dev/rdsk/c10t2d3 e1 00 01 CL1E 01:ed OPEN-V 00080xxx
...
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
03-22-2007 05:34 AM
03-22-2007 05:34 AM
Re: Alternate path for SAN boot disk
Hi Torsten,
Thanks for your replies and apologies for the late response.
What I didn't mention is that at the time I was also battling with changing the device files for VG00 after going through the ioinit process.
It was one of those trying to do too many things at once as not enough hours in the day. I sorted the VG00 device files out and went home.
I was in early the next day and didn't have any problem with the alternate paths now that everything had been straightened out!
Thanks Anyway, Paul
Thanks for your replies and apologies for the late response.
What I didn't mention is that at the time I was also battling with changing the device files for VG00 after going through the ioinit process.
It was one of those trying to do too many things at once as not enough hours in the day. I sorted the VG00 device files out and went home.
I was in early the next day and didn't have any problem with the alternate paths now that everything had been straightened out!
Thanks Anyway, Paul
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP