Kyle McDonald schrieb:
> Hi all,
> 
> Can anyone explain to me, or point me to any docs that explain how the 
> following numbers map together?
> 
> I have multiple LUNS exported to my HBA's from multiple EMC arrays.
> 
> zpool status, and /dev/dsk show device names like:
> 
>         c0t6006048000038794003753594D333837d0  ONLINE       0     0     0
>         c0t6006048000038794003753594D333838d0  ONLINE       0     0     0
>         c0t6006048000038794003753594D333839d0  ONLINE       0     0     0
>         c0t6006048000038794003753594D333841d0  ONLINE       0     0     0
>         c0t6006048000038794003753594D333842d0  ONLINE       0     0     0
>         c0t6006048000038794003753594D333843d0  ONLINE       0     0     0
>         c0t6006048000038794003753594D333844d0  ONLINE       0     0     0
> 
> but cfgadm shows disk names like:
> 
> c4::5006048dc7dfb170
> c5::5006048dc7dfb17e
> c7::5006048dc7dfb17e
> 
> How do these numbers break down?
> 
> I noticed the zpool or /dev/dsk nubmers all have a 'D' in them, what is 
> represented by the number after the 'D'?
> What is the number before the 'D' made up from?
> 
> I'm guessing at least part of the number befre the 'D' comes from the 
> WWN of the array? Does part come from the Disk in the array? or does the 
> array make up part of it so that that part is unique to the LUN? Or is 
> all the LUN info in the number after the 'D'?
> 
> I've also noticed that if you change the leading 5 in the cfgadm output, 
> to a 6, then the first 7 digits of cfgadm output match up with the first 
> 7 digits of Y in the cXtYdZ number. I've tried converting the remainder 
> 'dc7dfb170' from Hex to Dec, and I don't get anythign that even 
> resembles the '000038794003753594' part of the target.
> 
> How does this work?
> 
> These LUNs are all 11GB slices from the EMC Arrays which are filled with 
> 146GB drives. Since this is a lab environment I beleive the EMC arrays 
> are configured with no redundancy. What I'd like to know, is how can I 
> tell which LUNs might live on the same physical drives?


I don't have a Symmetrix here to check (have to wait 'til tomorrow), but 
your Symmetrix should have a serial number of
        387940037
and you have mapped the symmetrix IDs 387-38D in the above example:

6006048000038794003753594D333837

. 006048
        should be the vendor identifier for EMC

. 0000387940037
        Serial-No. of your Symmetrix

. 53594D
        ASCII code of "SYM"

. 333837
        ASCII code of "387"


Some of the information above was built from the WWN information, some 
from the SCSI inquiry (esp. the serial number). You can get a full 
inquiry of your disk with:

        # format -e c0t6006048000038794003753594D333837d0s2
        format> scsi
        scsi> inquiry

In the hexdump of the full inquiry information you can find
        . 8 bytes vendor ID ("EMC     "),
        . followed by 16 bytes product ID ("SYMMETRIX       ")
        . folled by (up to) 20 bytes serial number.
In the serial number you will find again the symdev (387) of this device 
and the last few digits of the serial number.


With the EMC SE tools you can query more information of your symdevs:

        symdev -sid 037 show 387

will show under "Backend Configuration" the real disks where this device 
is located.


Daniel

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to