Identifying the HP EVA LUNs on HP-UX 11iv3

June 15, 2010 — 6 Comments

Yesterday’s post about CLARiiON reminded me a similar issue I observed when the storage array is an HP EVA. If you ask for the disk serial number with scsimgr you always get the same number, in fact this number is the serial of the HSV controller.

The key to match your disk in the HP-UX host with the LUN provided by the EVA arrays is the wwid attribute of the disk.

root@ignite:/ # scsimgr get_attr -D /dev/rdisk/disk10 -a wwid

        SCSI ATTRIBUTES FOR LUN : /dev/rdisk/disk10

name = wwid
current = 0x600508b40006cb700000600008bb0000
default =
saved = 

root@ignite:/ #

If you look for this value in Command View will see that is the same as the World Wide LUN Name and the UUID.

### UPDATE ###

Thanks to my friend Jean and to Greg who reminded me that like Greg said in his comment is much easier to match the Word Wide LUN Name with the evainfo tool. Thanks to both of you :-)

root@hpux-server # evainfo -aP

Devicefile                      Array                   WWNN                            Capacity        Controller/Port/Mode
/dev/rdisk/disk20       5001-4380-04C7-2D90 6005-08B4-000F-3EED-0000-5000-003A-0000      204800MB       Ctl-A/FP-2/Optimized
/dev/rdisk/disk21       5001-4380-04C7-2D90 6005-08B4-000F-3EED-0000-5000-0042-0000      204800MB       Ctl-A/FP-1/Optimized
/dev/rdisk/disk22       5001-4380-04C7-2D90 6005-08B4-000F-3EED-0000-5000-004A-0000       20480MB       Ctl-A/FP-1/Optimized
/dev/rdisk/disk23       5001-4380-04C7-2D90 6005-08B4-000F-3EED-0000-5000-004E-0000       71680MB       Ctl-A/FP-2/Optimized
/dev/rdisk/disk24       5001-4380-04C7-2D90 6005-08B4-000F-3EED-0000-5000-0052-0000       10240MB       Ctl-A/FP-1/Optimized
/dev/rdisk/disk25       5001-4380-04C7-2D90 6005-08B4-000F-3EED-0000-5000-0056-0000       10240MB       Ctl-A/FP-1/Optimized
/dev/rdisk/disk26       5001-4380-04C7-2D90 6005-08B4-000F-3EED-0000-5000-005A-0000       20480MB       Ctl-A/FP-1/Optimized
/dev/rdisk/disk27       5001-4380-04C7-2D90 6005-08B4-000F-3EED-0000-5000-005E-0000      245760MB       Ctl-A/FP-1/Optimized

Where can I get EVAinfo? Like Greg said EVAinfo is distributed on the HP StorageWorks Storage System Scripting Utility CD (SSSU) since 8.0 version. Unfortunately I couldn’t find, yet, a public download URL but the CD is distributed with the hardware so if you own an EVA is probably you already have the media.

Thanks to Jean, man it seems that I owe you more than a couple of beers ;-D, here it is the URL of the CD. You will find the EVAinfo utility inside the HP StorageWorks Command View SSSU v9.2 software ISO.



6 responses to Identifying the HP EVA LUNs on HP-UX 11iv3


    It’s much easier to just use the evainfo tool that comes with the CommandView EVA media – I believe it’s on the SSSU disk. If you don’t have the media, you can download the ISOs at

    syntax is as follows:
    usage: /usr/local/bin/evainfo [-a|-d ] [-l] [-f fmt][-u KB|MB|GB][-w [-W][-g] [{-P|-p}]
    -a : Display information for all EVA Luns presented to this host.
    -d : Display information for the specified EVA Lun.
    -l : Display information in long/full format.
    -v : Display EVAInfo tool version details.
    -f : Specify output format. The supported values for are:
    tab (default)
    -u : Specify output format for Capacity {KB|MB|GB}, default is MB.
    -W : Collate output based on WWN of Luns.
    -w : Display information for the specified Lun WWN.
    -g : Use SCSI generic (sg) interface on Linux.
    -P : Display only persistent device special files.
    -p : Display persistent device special files along with legacy files.
    -h : Help


    Thanks for your comment Greg and for providing the URL of the evainfo tool. I updated the post with your info.
    UPDATE: The URL is not for the EVAinfo tool but for the HP-UX web server in HP Software Depot.



    If you don’t mind hard coded CommandView passwords, or are willing to take the time to develop something to store encrypted CommandView passwords then evainfo can be combined with SSSU, to do everything in one command and map to actual vDisk names rather than just WWIDs – I showed a very simple example in an ITRC forum post here:




      Hi Duncan. That’s a nice way of getting the vDisk names and match them to your disks, the only thing is the hard coded password of course but if your server is properly secure and the connection is established through secure channels it’s a minor issue. Thanks for sharing it :-)


    Hi, i think that i saw you visited my site so i came to “return
    the favor”.I am trying to find things to improve my web site!
    I suppose its ok to use a few of your ideas!!


    But the Focus has better fuel economy Unlike several other competitors, jdmyard offers additional options allowing for snowblowers
    to be customized for specific uses and conditions.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s