PVLinks EVA Paths

[Del_3]

Can someone help me figure out which paths for an EVA LUN are connected to which controller ports? I want to be sure my primary path is on the Preferred Controller.

How do I figure out which devices correspond to which controller ports?

So stealing from another post:

disk 305 255/255/0/3.3 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c21t3d3 /dev/rdsk/c21t3d3


Thanks
BTW I realize the output is from a 5000 and we dont use PVLinks on this model. Example only.

[Uwe Zessin]

You have to follow the hardware path which includes the fibre channel address of the EVA controller port. Unfortunately, I don't have an example present and this: "255/255/0/3.3" is from a Secure Path device.

[Sheriff Andy]

Do you have secure path installed? If so, you run;

# spmgr display

Will give you some kind of output like this;
TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 0 c20t0d0 6005-08B4-0010-3E67-0000-4000-0113-0000 4
255/0.0.0
Controller Path_Instance HBA Preferred? Path_Status
P5849E1AARA078 no
c3t0d1 td1 no Standby
c9t0d1 td2 no Standby

Controller Path_Instance HBA Preferred? Path_Status
P5849E1AARH039 YES
c6t0d1 td1 no Active
c12t0d1 td2 no Active


You can also go in thru your command view on your SMA, then drill down on your LUN to see which path it is taking.

[Pat Obrien_1]

To do what you ask, we have to know which ports of the eva are plugged into which switchports, and the preference the controller is given in cv, and the number of hbas and where the Hba ports have been plugged into the switch. Once I have alal this docs, I can usually figure it out, and then I verify withthe following command on each device file path with no securepath or other multipath software.

time dd if=/dev/rdsk/c#t#d# of=/dev/null bs=1024 count=200000

In my experience, the fast paths respond in about 25 seconds verses the slow paths in 50-54 seconds

[Ivan Ferreira]

You may use the evaperf utility, generate some I/O to your device, and check the ouput to try to identify the controller that serves a particular disk.

[Tim D Fulford]

SecurePath is your best bet... however, you "should" or are "reccomendd" to connect up both ports on each controller to both sides of your SAN (fibre switches). If you have done this there are actually 4 paths. Whilst this makes things more complex securepath really simplifies it.... The reason being is that you can choose which controller is in control of your LUNs (vDisks), so you can load balance it out (spmgr ... cmds ... ). That is the beauty of SecurePath, you control from the host how the IO will pass through the SAN.

Regards

Tim

[Olivier Masse]

I don't have SecurePath and had the same problems, so I wrote an ioscan wrapper to help me. It helps show on which port and lun each device is mapped. It's available here:
http://www.mayoxide.com/toolbox/ioscan_fc.sh

I updated it recently and have a better version on my test system at work, if you like this script write back to the e-mail in it and I'll upload and update.

Olivier

[Olivier Masse]

I don't have SecurePath and had the same problems, so I wrote an ioscan wrapper to help me. It helps show on which port and lun each device is mapped. It's available here:
http://www.mayoxide.com/toolbox/ioscan_fc.sh

I updated it recently and have a better version on my test system at work, if you like this script write back to the e-mail in it or in this thread and I'll upload an update.

Olivier

[Del_3]

I dont have an EVA without Secure Path to get the IOSCAN output from. Once I do I will post it. Thanks for the script Oliver.

[Olivier Masse]

Here is a sample output that shows how to find EVA Lun 3. It reports the port, the hardware paths, the VG associated with the lun and the disk size.

This output is from the updated version, I'll push it my website within a few minutes

The lun is an octal value, so lun 0.3 equals lun 3 in the EVA and lun 1.1 would be equal to lun 9.

root@bonyeune [/usr/local/bin]# ./ioscan_fc.sh -l 0.3

Hardware Path: 1/0/4/1/0/4/0
Description: HP AB465-60001 PCI/PCI-X Fibre Channel 2-port 2Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
Device: /dev/fcd0
World Wide Name: 0x50060b000029ffc8
Visible luns:
0.3 CLAIMED 1/0/4/1/0/4/0.1.0.0.0.0.3 HP HSV210
------- /dev/dsk/c8t0d3 /dev/vgoracle_data
------- /dev/rdsk/c8t0d3 10240Mb
0.3 CLAIMED 1/0/4/1/0/4/0.1.16.0.0.0.3 HP HSV210
------- /dev/dsk/c12t0d3 /dev/vgoracle_data
------- /dev/rdsk/c12t0d3 10240Mb
0.3 CLAIMED 1/0/4/1/0/4/0.1.24.0.0.0.3 HP HSV210
------- /dev/dsk/c14t0d3 /dev/vgoracle_data
------- /dev/rdsk/c14t0d3 10240Mb
0.3 CLAIMED 1/0/4/1/0/4/0.1.8.0.0.0.3 HP HSV210
------- /dev/dsk/c10t0d3 /dev/vgoracle_data
------- /dev/rdsk/c10t0d3 10240Mb

Hardware Path: 1/0/4/1/0/4/1
Description: HP AB465-60001 PCI/PCI-X Fibre Channel 2-port 2Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
Device: /dev/fcd1
World Wide Name: 0x50060b000029ffca
Visible luns:
0.3 CLAIMED 1/0/4/1/0/4/1.2.0.0.0.0.3 HP HSV210
------- /dev/dsk/c0t0d3 /dev/vgoracle_data
------- /dev/rdsk/c0t0d3 10240Mb
0.3 CLAIMED 1/0/4/1/0/4/1.2.16.0.0.0.3 HP HSV210
------- /dev/dsk/c4t0d3 /dev/vgoracle_data
------- /dev/rdsk/c4t0d3 10240Mb
0.3 CLAIMED 1/0/4/1/0/4/1.2.24.0.0.0.3 HP HSV210
------- /dev/dsk/c6t0d3 /dev/vgoracle_data
------- /dev/rdsk/c6t0d3 10240Mb
0.3 CLAIMED 1/0/4/1/0/4/1.2.8.0.0.0.3 HP HSV210
------- /dev/dsk/c2t0d3 /dev/vgoracle_data
------- /dev/rdsk/c2t0d3 10240Mb

[Del_3]

Olivier, based on your output, what value represents the switch port and / or the switch domain?

0.3 CLAIMED 1/0/4/1/0/4/1.2.0.0.0.0.3 HP HSV210
------- /dev/dsk/c0t0d3 /dev/vgoracle_data

I am trying to figure out what port the controler is plugged into.

[Uwe Zessin]

> .2.0.0.

A switch with domain ID 2. Could be port 0, but that depends on the switch model and how it assigns the addresses. The final 0 indicates direct fabric attach (DFA).