determine lun size

[John Dvorchak]

I have been out of HPUX admin for a while and I know I should know this. Please help me remember.

I have just had the SAN team add some Hitachi array disk luns to a system. I can see them with ioscan -fnCdisk. Now what I would like to know is the disk size of those LUNs but don't remember how. We are using lvm.

disk 106 4/0/10/1/0.14.0.109.0.2.4 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c12t2d4 /dev/rdsk/c12t2d4
disk 107 4/0/10/1/0.14.0.109.0.2.5 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c12t2d5 /dev/rdsk/c12t2d5

Thank you in advance.

[Patrick Wallek · Accepted solution]

Use diskinfo.

# diskinfo /dev/rdsk/c12t2d4
# diskinfo /dev/rdsk/c12t2d5

Note that you have to use the '/dev/rdsk' device file with the diskinfo command.

[John Dvorchak]

Patrick that is what I was looking for. Now it just occured to me that I am not sure of the alternate path to the same LUN. I used to use inq -sortysymm but that is with EMC. These are Hitachi do they have a similar utility?

[TTr]

The early XP models had their uitilities installed under /opt/HORCM. The utility was called "inquiry" or "inquiryXXX" where XXX was the XP model number such as inquiry256 for XP256.

[John Dvorchak]

Thank you TTr but I don't seem to have that set of utilities.

[Tim Nelson]

another quick option is to match up the hardware addresses of the devices..

there should be some hitachi utility for hpux to ID the wwn of the lun. EVAs provide evainfo.

[John Dvorchak]

Tim I only gave you 9 because you were close but got me thinking. I was able to use lunstat -ts and that gave me the serial numbers along with a lot of other info. From that I was able to pair up disks but still not by /dev/dsk/ctd number which I need to add them to a vg.

[TTr]

I just remembered that the recent XP models use the CommandViewXP utilities. I never had CommandViewXP but I used commandviewVA and the array utilities for the VAs were armdiscover and armdsm. They might be the same in C-viewXP.

Look under opt for a "commandview" subdirectory or look at "swlist" listing.

[TTr]

xpinfo might do it.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1431840

[chris huys_4]

Hi John,

TTr mentioned /opt/HORCM which is part of raidmanager, but if you dont use businesscopy or continuous access, or the hitachi equivalents of the xp namings, it will probably not installed on the system.

commandview for XP does exist, but it runs on a windows system and is more alike the sanappliance commandview that runs on a EVA, and is used to administer a XP, then anything remotely like commandviewVA. Also it will for the hitachi be named differently.

xpinfo utility would probably work on a hitachi system that is equal to a xp, however normally hp support would not give this utility to view the luns of a competitor storage array , and anyway a hitachi DF600F is a lun of one of hitachi's midrange storage, AMS or something like that, so the utility would not work anyway..

The long way, is offcourse to check on the hitachi diskarray what luns are defined to what histachi frontendports. And then check how these hitachi frontendports are zoned in with which host fc hba ports and then to see how these luns are then translated into device files..

But there is a shorter way, through vxvm, you could configure vxvm, with vxinstall, and normally it should give the different paths for each of device files, or if you dont want to configure vxvm, you can also use..

/etc/vx/diag.d/vxdmpinq, which will give for each /dev/rdsk device file the serial# of the lun.
f.e.

# /etc/vx/diag.d/vxdmpinq /dev/rdsk/c14t11d5

Inquiry for /dev/rdsk/c14t11d5, evpd 0x0, page code 0x0
Vendor id : HP
Product id : OPEN-V
Revision Number : 5001
Serial Number : 50 127120571

#/etc/vx/diag.d/vxdmpinq /dev/rdsk/c8t11d5

Inquiry for /dev/rdsk/c8t11d5, evpd 0x0, page code 0x0
Vendor id : HP
Product id : OPEN-V
Revision Number : 5001
Serial Number : 50 127120571

>> CONCLUSION -- same serial#, they are alternate links..

Greetz,
Chris

[Bill Hassell]

> locating alternate links...

The easiest way is to list the devices with the same TD numbers (CTD = controller or I/O card, T=target, D=disk) so if you're looking for alternate links for c12t2d4, do this:

ll /dev/dsk/c*t2d4

Then if you run pvcreate on one of the links, you can verify that it is the same disk with dd and xd:

dd if=/dev/rdsk/c12t2d4 bs=1k skip=9 count=1 2>/dev/null | xd -x

0000000 4c56 4d52 4543 3031 69ea 86f7 4b60 5af7
0000010 69ea 86f7 4b60 5c4a 0445 dcc8 0000 0006

The last two numbers (4b60 5af7) is the VGID (unique among every VG), and the 4th and 5th numbers on line 0000010 (4b60 5c4a) is the unique LUN or PV identification. Only alternate links will have the same exact PVID.

[Bill Hassell]

> dd if=/dev/rdsk/c12t2d4 bs=1k skip=9 count=1 2>/dev/null | xd -x

Oops, that should be: skip=8:

dd if=/dev/rdsk/c12t2d4 bs=1k skip=8 count=1 2>/dev/null | xd -x

That pesky keyboard put the 9 too close to the 8.

[Uday_S_Ankolekar]

If you have Hitachi arrays then probably you will have HDLM(Hitachi Dynamic Link Manager) installed on servers. It's load balancing software from Hitachi.
you can run dlnkmgr commands to see lun details and alt paths etc. It's useful utility to have if you are dealing with Hitachi Storage disks.

USA..