ioscan numbering versus EMC volume identication (LUN)

[Paulo A G Fessel]

Hello UX'ers,

Hope this is a quick one.

I need to remove access from a volume in a EMC box we have here in a HP-UX machine. Question is, ioscan reports devices like

0/6 ba Local PCI Bus Adapter (782)
0/6/2/0 fc HP Tachyon TL/TS Fibre Channel Mass Storage Adapter
0/6/2/0.33 fcp FCP Domain
0/6/2/0.33.4.19.0 ext_bus FCP Array Interface
0/6/2/0.33.4.19.0.0 target
0/6/2/0.33.4.19.0.0.0 disk EMC SYMMETRIX
0/6/2/0.33.4.19.0.1 target
0/6/2/0.33.4.19.0.1.0 disk EMC SYMMETRIX
0/6/2/0.33.4.19.0.1.1 disk EMC SYMMETRIX
0/6/2/0.33.4.19.1 ext_bus FCP Array Interface
0/6/2/0.33.4.19.1.4 target
0/6/2/0.33.4.19.1.4.1 disk EMC SYMMETRIX
0/6/2/0.33.4.19.1.4.2 disk EMC SYMMETRIX
0/6/2/0.33.4.19.1.4.3 disk EMC SYMMETRIX
0/6/2/0.33.4.19.1.4.4 disk EMC SYMMETRIX
0/6/2/0.33.4.19.1.6 target
0/6/2/0.33.4.19.1.6.0 disk EMC SYMMETRIX
0/6/2/0.33.4.19.1.6.2 disk EMC SYMMETRIX
0/6/2/0.33.4.19.1.8 target
0/6/2/0.33.4.19.1.8.0 disk EMC SYMMETRIX
0/6/2/0.33.4.255.1 ext_bus FCP Device Interface
0/6/2/0.33.4.255.1.3 target
0/6/2/0.33.4.255.1.3.0 ctl EMC SYMMETRIX

Now, in Symmetrix and VLogix all I have are LUN's and SYMDEV ID's. How to know which LUN is corresponding to the disks seen by the HP-UX box?

I found that Emulex has a document which describes how to interpretate the entries of a FC adapter; however, I noticed very quickly that they are appliable only to Emulex FC cards, not HP Tachyon's.

Is there some magical formula to convert back and forth from LUN ID's to HP-UX ID's and vice-versa?

TIA,
Paulo Fessel

[Paulo A G Fessel]

I've found that syminq solves my immediate issues (notice the three middle digits of the "Ser Num" field):

bash-2.05# ./syminq

Device Product Device
---------------------- --------- --------------------- ------------------
Name Type Vendor ID Rev Ser Num Cap (KB)
---------------------- --------- --------------------- ------------------

/dev/rdsk/c0t5d0 HP DVD-ROM 305 1.01 2000/09 619704
/dev/rdsk/c1t15d0 HP 18.2GB C 80-D94N D94N 5EGMH825 17783240
/dev/rdsk/c3t15d0 HP 18.2GB C 80-D94N D94N 5EGND903 17783240
/dev/rdsk/c4t0d0 EMC SYMMETRIX 5566 82000000 7680
/dev/rdsk/c4t1d0 M(5) EMC SYMMETRIX 5566 82024000 48600000
/dev/rdsk/c4t1d1 M(5) EMC SYMMETRIX 5566 82029000 48600000
/dev/rdsk/c6t4d1 BCV EMC SYMMETRIX 5566 820A6000 48600000
/dev/rdsk/c6t4d2 BCV EMC SYMMETRIX 5566 820AB000 48600000
/dev/rdsk/c6t6d0 M(5) EMC SYMMETRIX 5566 820F1000 48600000
/dev/rdsk/c6t8d0 M(5) EMC SYMMETRIX 5566 82330000 50990400

However, I'm still interested to know how HP-UX gives its device numbers to FC Tachyon adapters. Does anybody know about some reference on this?

TIA,
Paulo Fessel

[Denver Osborn]

This example assumes the EMC is using volume set addressing...

example path = 0/6/2/0.33.4.19.1.6.0

HBA = 0/6/2/0
FC Path = 33.4.19
Domain ID = 33
Area ID (port on switch) = 4
Port ID = 19
Virtual SCSI2 path = 1.6.0

In other words... this is about all I can remember without having to dig out manuals and read!

Have a look at this online doc, it might help.

http://docs.hp.com/hpux/onlinedocs/J2635-90014/00/00/6-con.html

The fabric migration guide should explain better than what I can...

Good luck!
-Denver