sam showing two/three volume groups having the same path

[slydmin]

Here is the setup

HPUX B.11.11, connected to XP SAN 10k using qlogic fibrechannel card (i will post the verion/name soon)



The storage administrator presented a total of 7 LUs to the server. (LUs: 600GB, 600GB, 100GB 100GB, 100GB, 300GB)

If I use SAM to look at and create new volume groups from these presented LUs, I see something unusual. I see the first 3 LUs (600, 600, 100)correctly, however the fourth one shows up as a 100 GB size with 6 paths to the LU. And I don't the two remaining LUs (100GB , 300GB).

Now, I was able to add the 4th and 5th LUs as volume groups vg_p04 and vg_p05 using the command line. These show up without a problem on bdf (mounted as /p04 and /p05). But when I look at disk-devices from within SAM, I see an output where vg_p04/vg_p05 are one the same LU with 4 paths to the LU.(image attached)


Following is the ioscan output when all of the LUs are presented to the server.


ioscan -fnC disk provides output:
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/0/3/0.5.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 0/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0
disk 7 0/0/4/1/0.11.23.0.0.0.0 sdisk CLAIMED DEVICE HP OPEN-V*6
/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0
disk 15 0/0/4/1/0.11.23.0.0.0.1 sdisk CLAIMED DEVICE HP OPEN-V*6
/dev/dsk/c10t0d1 /dev/rdsk/c10t0d1
disk 16 0/0/4/1/0.11.23.0.0.0.2 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c10t0d2 /dev/rdsk/c10t0d2
disk 17 0/0/4/1/0.11.23.0.0.0.3 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c10t0d3 /dev/rdsk/c10t0d3
disk 52 0/0/4/1/0.11.23.0.0.0.4 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c10t0d4 /dev/rdsk/c10t0d4
disk 53 0/0/4/1/0.11.23.0.0.0.5 sdisk CLAIMED DEVICE HP OPEN-V*3
/dev/dsk/c10t0d5 /dev/rdsk/c10t0d5
disk 18 0/0/4/1/0.11.23.0.0.1.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t1d0 /dev/rdsk/c10t1d0
disk 19 0/0/4/1/0.11.23.0.0.2.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t2d0 /dev/rdsk/c10t2d0
disk 20 0/0/4/1/0.11.23.0.0.3.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t3d0 /dev/rdsk/c10t3d0
disk 21 0/0/4/1/0.11.23.0.0.4.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t4d0 /dev/rdsk/c10t4d0
disk 22 0/0/4/1/0.11.23.0.0.5.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t5d0 /dev/rdsk/c10t5d0
disk 23 0/0/4/1/0.11.23.0.0.6.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t6d0 /dev/rdsk/c10t6d0
disk 24 0/0/4/1/0.11.23.0.0.7.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t7d0 /dev/rdsk/c10t7d0
disk 25 0/0/4/1/0.11.23.0.0.8.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t8d0 /dev/rdsk/c10t8d0
disk 26 0/0/4/1/0.11.23.0.0.9.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t9d0 /dev/rdsk/c10t9d0
disk 27 0/0/4/1/0.11.23.0.0.10.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t10d0 /dev/rdsk/c10t10d0
disk 28 0/0/4/1/0.11.23.0.0.11.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t11d0 /dev/rdsk/c10t11d0
disk 29 0/0/4/1/0.11.23.0.0.12.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t12d0 /dev/rdsk/c10t12d0
disk 30 0/0/4/1/0.11.23.0.0.13.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t13d0 /dev/rdsk/c10t13d0
disk 31 0/0/4/1/0.11.23.0.0.14.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t14d0 /dev/rdsk/c10t14d0
disk 32 0/0/4/1/0.11.23.0.0.15.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c10t15d0 /dev/rdsk/c10t15d0
disk 6 0/0/4/1/1.10.23.0.0.0.0 sdisk CLAIMED DEVICE HP OPEN-V*6
/dev/dsk/c11t0d0 /dev/rdsk/c11t0d0
disk 14 0/0/4/1/1.10.23.0.0.0.1 sdisk CLAIMED DEVICE HP OPEN-V*6
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
disk 33 0/0/4/1/1.10.23.0.0.0.2 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c11t0d2 /dev/rdsk/c11t0d2
disk 34 0/0/4/1/1.10.23.0.0.0.3 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c11t0d3 /dev/rdsk/c11t0d3
disk 35 0/0/4/1/1.10.23.0.0.0.4 sdisk CLAIMED DEVICE HP OPEN-V
/dev/dsk/c11t0d4 /dev/rdsk/c11t0d4
disk 51 0/0/4/1/1.10.23.0.0.0.5 sdisk CLAIMED DEVICE HP OPEN-V*3
/dev/dsk/c11t0d5 /dev/rdsk/c11t0d5
disk 36 0/0/4/1/1.10.23.0.0.1.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t1d0 /dev/rdsk/c11t1d0
disk 37 0/0/4/1/1.10.23.0.0.2.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t2d0 /dev/rdsk/c11t2d0
disk 38 0/0/4/1/1.10.23.0.0.3.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t3d0 /dev/rdsk/c11t3d0
disk 39 0/0/4/1/1.10.23.0.0.4.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t4d0 /dev/rdsk/c11t4d0
disk 40 0/0/4/1/1.10.23.0.0.5.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t5d0 /dev/rdsk/c11t5d0
disk 41 0/0/4/1/1.10.23.0.0.6.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t6d0 /dev/rdsk/c11t6d0
disk 42 0/0/4/1/1.10.23.0.0.7.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t7d0 /dev/rdsk/c11t7d0
disk 43 0/0/4/1/1.10.23.0.0.8.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t8d0 /dev/rdsk/c11t8d0
disk 44 0/0/4/1/1.10.23.0.0.9.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t9d0 /dev/rdsk/c11t9d0
disk 45 0/0/4/1/1.10.23.0.0.10.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t10d0 /dev/rdsk/c11t10d0
disk 46 0/0/4/1/1.10.23.0.0.11.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t11d0 /dev/rdsk/c11t11d0
disk 47 0/0/4/1/1.10.23.0.0.12.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t12d0 /dev/rdsk/c11t12d0
disk 48 0/0/4/1/1.10.23.0.0.13.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t13d0 /dev/rdsk/c11t13d0
disk 49 0/0/4/1/1.10.23.0.0.14.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t14d0 /dev/rdsk/c11t14d0
disk 50 0/0/4/1/1.10.23.0.0.15.0 sdisk CLAIMED DEVICE HP DISK-SUBSYSTEM
/dev/dsk/c11t15d0 /dev/rdsk/c11t15d0
disk 5 0/0/8/1/0/1/0.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 2 1/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c4t6d0 /dev/rdsk/c4t6d0
disk 3 1/0/0/3/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
disk 4 1/0/1/1/0/1/1.6.0 sdisk CLAIMED DEVICE HP 73.4GST373453LC
/dev/dsk/c7t6d0 /dev/rdsk/c7t6d0


What could be the problem with SAM showing incorrect multiple paths to the same LU?

Thanks in advance.

[slydmin]

The commands I used to create the vg/lvs are
pvcreate /dev/rdsk/c10t0d4
mkdir /dev/vg_p05
mknod /dev/vg_p05/group c 64 0x050000
vgcreate -s 32 /dev/vg_p05 /dev/dsk/c10t0d4
lvcreate -n lv_p05 -L 102144 /dev/vg_p05
newfs -F vxfs /dev/vg_p05/rlv_p05
/dev/vg_p05/lv_p05 /p05 vxfs defaults 0 2




Information about the fibre card:
ioscan output
==================================================================
fc 0 0/0/4/1/0 fcd CLAIMED INTERFACE HP 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (Port 1)
/dev/fcd0
fc 1 0/0/4/1/1 fcd CLAIMED INTERFACE HP 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (Port 2)
/dev/fcd1




fcmsutil output:
V I T A L P R O D U C T D A T A
--------- ------------- -------

Product Description : "Dual Port 2Gbps/1Gbps Fibre Channel Universal PCI-X Adapter"

Part number : "A6826-60001"

Engineering Date Code : "A-4450"

Part Serial number : "US00033467"

Misc. Information : "PW=15W;PCI 66MHZ;PCI-X 133MHZ"

Mfd. Date : "4507"

Check Sum : 0xba

EFI version : "001.42"

ROM Firmware version : "003.003.150"

Asset Tag : "NA"

[Tim Nelson · Accepted solution]

SAM bad, using real unix commands is good.

After many years you will learn not to trust menu driven utilities, SAM has been buggy since its inception.

I would recommend to always check your configs and/or admin them with commands.

ioscan
pvcreate
pvdisplay
vgdisplay
vgcreate
vgextend
lvdispaly
lvcreate
lvextend
newfs
mkdir
vi /etc/fstab
mount

[Avinash Agarkar]

Hi Dear,

Please do not create the new vg's lv's with
SAM, discover the new luns and use command line to create the same.

Thanks,
Avinash