powerpath and serviceguard

[TMcB]

Hi
Just wanting to check, as I've never used powerpath before.

powermt shows the following :

CLARiiON ID=CK200042500043 [BFSSG01]
Logical device ID=60060160335B1100FC33B331EC02DC11 [LUN 201]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
==============================================================================
---------------- Host --------------- - Stor - -- I/O Path - -- Stats ---
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
10 0/4/2/0.2.3.0.0.0.1 c10t0d1 SP B0 active alive 0 0
11 0/4/2/0.2.4.0.0.0.1 c11t0d1 SP A1 active alive 0 0
8 0/5/1/0.4.3.0.0.0.1 c8t0d1 SP A0 active alive 0 0
9 0/5/1/0.4.4.0.0.0.1 c9t0d1 SP B1 active alive 0 0

As far as configuring this as a cluster disk, do I now pick one of these and create my volumes on it.

Eg
pvcreate /dev/rdsk/c10t0d1
and then export this to my 2nd node.

I guess my question is what device for the above LUN do I use to create my cluster data volume?

Thanks very much

[Redhat]

Post the ioscan -fnC disk output of the primary node.

[TMcB]

Hi here's the ioscan result.
There is 2 40GB clariion disks and a 4MB cluster lock disk

Thank

# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/3/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 2 0/1/1/1.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0
disk 3 0/4/2/0.2.3.0.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0
disk 10 0/4/2/0.2.3.0.0.0.1 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c10t0d1 /dev/rdsk/c10t0d1
disk 13 0/4/2/0.2.3.0.0.0.2 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c10t0d2 /dev/rdsk/c10t0d2
disk 5 0/4/2/0.2.4.0.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c11t0d0 /dev/rdsk/c11t0d0
disk 9 0/4/2/0.2.4.0.0.0.1 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
disk 14 0/4/2/0.2.4.0.0.0.2 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c11t0d2 /dev/rdsk/c11t0d2
disk 6 0/5/1/0.4.3.0.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c8t0d0 /dev/rdsk/c8t0d0
disk 8 0/5/1/0.4.3.0.0.0.1 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c8t0d1 /dev/rdsk/c8t0d1
disk 11 0/5/1/0.4.3.0.0.0.2 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c8t0d2 /dev/rdsk/c8t0d2
disk 4 0/5/1/0.4.4.0.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c9t0d0 /dev/rdsk/c9t0d0
disk 7 0/5/1/0.4.4.0.0.0.1 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 12 0/5/1/0.4.4.0.0.0.2 sdisk CLAIMED DEVICE DGC CX500WDR5
/dev/dsk/c9t0d2 /dev/rdsk/c9t0d2

[Redhat]

It seems that the first LUN is c10t0d0 and if you create pv on c10t0d0 you should able to find PVID from c11t0d0 through pvdisplay -v /dev/dsk/c11t0d0.Means all the other divice files are the alternate path ..

same way for c8t0d0 and c9t0d0 .

if so then you can go ahead with vgcreate,lvcreate and then vgexport -p -s -m mapfile etc ...

If you have purchase Sucure path s/w ,Pls install it for getting a single path against all the odd path for the same LUN

[TMcB]

I dont think we have securepath, but I'll double check.

Will I still need to do pvlinks if I'm using powerpath?

Thanks

[Redhat · Accepted solution]

To be safe, set up your pvlinks in LVM the same way you would if Powerpath was not installed. If for any reason Powerpath fails to detect a HBA card failure then you still have the alternate path set and LVM will take care of switching to the alternate path.

But get sure you using the right path while creating vg or expanding vg

[TMcB]

thanks

you've helped clear things up.