EVA 6000 vdisk map to HP-UX device file

[David L Brewster]

On EVA 6000 I have vdisks 1-94.
How would this line up with an ioscan?
Thanks,
Dave

[Steven E. Protter]

Shalom,

This is one of those deals where you will have to at least provide a copy of part of the output and the ioscan.

SEP

[David L Brewster]

Ok, let me try to explain my issue...

We have 94 Virtual Disks on one of our servers. Several of them are not currently allocated.
We want to move some of the 94 vdisks to another server, but we want to make sure that the Vdisk is not already allocated.
IE: Zeus_Vdisk015 points to which HP-UX device?

[Steven E. Protter]

I understand the question.

There really isn't a magic trick here.

You may be able to cobble together a script.

ioscan -fn

vgdisplay -v

strings /etc/lvmtab

From this point you will be able to assemble a list of disks that are actually allocated to volume groups, and likely to be in use.

ioscan shows you all available disks, should show all 94. The other commands provide various ways to see what disk is allocated.

SEP

[David L Brewster]

Yeah, we've used ioscan and see (of course) the 94 disks.

Someone mentioned to me we can "unpresent" the virtual disk and then do another ioscan and which ever disk shows No Hardware determines the one-to-one relation.

That's what I really need...Zeus_Vdisk012 is mapped to /dev/rdsk/c8t0d6

[SoorajCleris]

Hi David,

If you unpresent a disk which is already used by the system it will be a proble.

as SEP told, you may check the following things,

1. strings /etc/lvmtab
2. verify the same with vgdisplay
3. vxdisklist - any vxvm disk if you are using
4. bdf ( if anyone mounted disk directly, now a days noone use it)
5. swapinfo -tam , if anybody used the full disk as swap

Compare this with Ioscan.

Which OS you are using ? if 11.31
check #ioscan -m dsf
also to find out if there any alternate paths are there

Regards,
Sooraj

[Torsten.]

Hi Dave,

probably the best way to identify the vdisks is to use evainfo command.

[shanmuhanandam]

Hi,
Eva info is the good tool to identify the lun wwn, then you can match it with EVA side. But you are not mentioned the OS version. Here is the link you can download the same tool related to your OS version..

http://h20000.www2.hp.com/bizsupport/site/search/r4_0/jsp/search.jsp?lang=en&cc=us&prodTypeId=12169&prodSeriesId=471497&tx=EVA%20info


Thanks,
Shanmugam.

[shanmuhanandam]

OR Else find the tool here

http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=3439051〈=en&cc=us&prodTypeId=18964&prodSeriesId=471497&taskId=135

[David L Brewster]

Ok, thanks.
Checking the links.
Sooraj and Torsen...I made a mistake assigning points. Post reply and I will correct. Should be 7.

[Gordon Sjodin]

If you have autopath in stalled, you can use

autopath discover
then
autopath display

This will map luns to disks.

[Tim Nelson · Accepted solution]

How about id'ing by lun number ?

x/x/x/x.y.y.0.0.0.1 LUN1
x/x/x/x.y.y.0.0.0.2 LUN2
...
x/x/x/x.y.y.0.0.1.0 LUN8
x/x/x/x.y.y.0.0.1.1 LUN9
...
x/x/x/x.y.y.0.5.1.5 LUN93
x/x/x/x.y.y.0.5.1.6 LUN94

[Denver Osborn]

What model FC Switch and do you know what port(s) the EVA is connected to on the switch? Once you have this info, it should be easy enough to figure out.

Here's a script I've been working on and looking to improve on at the moment--I'm not the best at scripting, but it does what I need it to. You're free to pick it apart to see how the hardware path can be mapped to the LUN based on where the EVA is connected to on the switch.

Works with 11i v1/2/3 and mpio devices.

Change the "ARRAY" variables to match your config.

# Config Format: "Array_Alias[Port_Index]=Ctl_Port_SwitchDomain_SwitchPort"

Hope this is of some use.

-denver

[David L Brewster]

Thanks to all.
You've given us a lot to work with.
Cheer us on!