Operating System - HP-UX
1827612 Members
3360 Online
109966 Solutions
New Discussion

Alternate path for SAN boot disk

 
Paul McCleary
Honored Contributor

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.

3 REPLIES 3
Torsten.
Acclaimed Contributor

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!   
Torsten.
Acclaimed Contributor

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!   
Paul McCleary
Honored Contributor

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