HP-UX

I was conveniently excluded from some EVA8000 training, and now find myself with an EVA zoned, but no physical devices

My ioscan appears as follows:

ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
fc 0 0/1/0/0 td CLAIMED INTERFACE HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
/dev/td0
fcp 2 0/1/0/0.1 fcp CLAIMED INTERFACE FCP Domain
ext_bus 11 0/1/0/0.1.12.0.0 fcparray CLAIMED INTERFACE FCP Array Interface
target 16 0/1/0/0.1.12.0.0.0 tgt CLAIMED DEVICE
ctl 9 0/1/0/0.1.12.0.0.0.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t0d0
target 17 0/1/0/0.1.12.0.0.1 tgt CLAIMED DEVICE
ctl 10 0/1/0/0.1.12.0.0.1.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t1d0
target 18 0/1/0/0.1.12.0.0.2 tgt CLAIMED DEVICE
ctl 11 0/1/0/0.1.12.0.0.2.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t2d0
target 19 0/1/0/0.1.12.0.0.3 tgt CLAIMED DEVICE
ctl 12 0/1/0/0.1.12.0.0.3.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t3d0
target 20 0/1/0/0.1.12.0.0.4 tgt CLAIMED DEVICE
ctl 13 0/1/0/0.1.12.0.0.4.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t4d0
target 21 0/1/0/0.1.12.0.0.5 tgt CLAIMED DEVICE
ctl 14 0/1/0/0.1.12.0.0.5.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t5d0
target 22 0/1/0/0.1.12.0.0.6 tgt CLAIMED DEVICE
ctl 15 0/1/0/0.1.12.0.0.6.0 sctl CLAIMED DEVICE HP HSV210
/dev/rscsi/c11t6d0


We have two controllers zoned to the same luns, but It is my understanding that we may need a product called secure path.

Is there a way to configure an EVA w/pvlinks (no secure path)?
There appear to be a few failover modes on the EVA...

server OS = 11.0

any assistance would be appreciated,
manny

bouncing the server resoved the problem...I think?
The following devices are now visable:

------------------------------------------------------------------------
DEVICE :VEND :PROD :REV :SER NUM :CAP(kb)
------------------------------------------------------------------------
/dev/rdsk/c1t0d0 :SEAGATE :ST173404LC :HP03 :3CE0HMM2 :71687368
/dev/rdsk/c1t2d0 :SEAGATE :ST173404LC :HP03 :3CE0JAD2 :71687368
/dev/rdsk/c2t0d0 :SEAGATE :ST173404LC :HP03 :3CE0JPS8 :71687368
/dev/rdsk/c2t2d0 :SEAGATE :ST173404LC :HP03 :3CE0JQZ9 :71687368
/dev/rdsk/c3t2d0 :HP VD-ROM 305 :1.01 : 2000/09 : 658948
/dev/rdsk/c11t0d1 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c11t0d2 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c13t0d1 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c13t0d2 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c15t0d1 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c15t0d2 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c17t0d1 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c17t0d2 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c19t0d1 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c19t0d2 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c21t0d1 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c21t0d2 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c23t0d1 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c23t0d2 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c25t0d1 :HP :HSV210 :5031 :8398ASF0 :104857600
/dev/rdsk/c25t0d2 :HP :HSV210 :5031 :8398ASF0 :104857600
#

A question I now have, is I see 16 100GB devices...
I believe the EVA guy only setup TWO 100GB luns.

Also, they all appear tobe the SAME device...

the c10 and above are visable from one HBA, while the c19 and above are visable from the other HBA.

Hi

You can use alternated PV links for each PV link if you can't use SecurePath. But SecurePath has more advantages than alternated PV links

you can look at man page of pvcreate,

There is a section from man

When a pv_path refers to one of the physical volumes already in the volume group by a different pv_path name to indicate the use of a different controller, this new path becomes an alternate link to the physical volume. When two paths that reference the same disk are provided in the pv_path list, the order of the paths is important. The first path becomes the "primary link" to the physical volume, the second becomes an "alternate link" to the physical volume. The primary link is the path used to access the physical volume unless the primary link becomes unavailable in which case LVM automatically switches to the alternate link to access the physical volume. Currently LVM supports a maximum of 8 paths to a physical volume (7 alternates and one primary).

I hope it helps to your problem

I am very interested in using pvlinks for fail-over, as secure-path may not be an option...
It sounds like the EVA has 8 back-end ports, which explains why I see 8 hwpaths for each lun?
I opened a case w/HP last night, and they talked about a tool called sssu.
this tool would allow me to query the eva from cli on hpux, and retrieve lun info, like wwn.

Is there a way to configure a non-secure path box, so I don't see 8hwpaths for each lun?
having 10 (x8) is one thing, but having 355 (x8) is not something I look forward too...

thanks,
manny