|
Replies:
2
-
Last Post:
Nov 26, 2009 9:15 AM
by: thekid
|
|
|
Posts:
53
From:
US
Registered:
6/9/06
|
|
|
|
iSCSI GUID => cXt${GUID}d0 ?
Posted:
Nov 24, 2009 11:35 AM
To: Communities » storage » discuss
|
|
I am trying to come up with a "nicer" way of mapping iSCSI luns that are being exported from a Unified Storage 7410 (fishworks) to disks on my xVM machines. The fishworks box seems to focus on "GUID" in all the lists. I haven't found a way (without dropping to a shell) to expose the LUN number, and of course per my previous thread, the LUN alias is also not available. It seems to me like in every case I have see that the scsi_vhci controllers c6t(BLAH)d0, the (BLAH) is the GUID of the iSCSI lun. Is this *always* the case... like reliably enough that I could make it determine the right disk based on GUID. Also, GUID sounds like it should be "globaly unique ID" .. but is there really any way to be sure its unique for anything more than the target (or server) its on?
~tommy
|
|
|
Posts:
24
From:
Registered:
9/2/06
|
|
|
|
Re: [storage-discuss] iSCSI GUID => cXt${GUID}d0 ?
Posted:
Nov 26, 2009 3:01 AM
in response to: thekid
|
|
Hi Tommy,
I'm thinking about it in another way..
Does a new option to list the OS name of a specific lun from iscsiadm
sound reasonable?
E.g.,
--------------------------------------
#iscsiadm list taget iqn....... -l 5
/dev/rdsk/c<x>t<GUID>d0s2
--------------------------------------
Best regards,
Jack
Tommy McNeely wrote:
> I am trying to come up with a "nicer" way of mapping iSCSI luns that are being exported from a Unified Storage 7410 (fishworks) to disks on my xVM machines. The fishworks box seems to focus on "GUID" in all the lists. I haven't found a way (without dropping to a shell) to expose the LUN number, and of course per my previous thread, the LUN alias is also not available. It seems to me like in every case I have see that the scsi_vhci controllers c6t(BLAH)d0, the (BLAH) is the GUID of the iSCSI lun. Is this *always* the case... like reliably enough that I could make it determine the right disk based on GUID. Also, GUID sounds like it should be "globaly unique ID" .. but is there really any way to be sure its unique for anything more than the target (or server) its on?
>
> ~tommy
>
_______________________________________________
storage-discuss mailing list
storage-discuss at opensolaris dot org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
|
|
|
|
|
Posts:
53
From:
US
Registered:
6/9/06
|
|
|
|
Re: [storage-discuss] iSCSI GUID => cXt${GUID}d0 ?
Posted:
Nov 26, 2009 9:15 AM
in response to: ran.meng
To: Communities » storage » discuss
|
|
Hi Jack,
Take a look at what /usr/lib/xen/scripts/iscsi-disk is doing (its python). I think if you could add an option to iscsiadm list by lun would be great. It would also be nice if it could list (filter?) by "target alias" (-a ALIAS). That would make the iscsi-disk script a lot easier to implement.
The problem that *I* specifically have, is that the fishworks box doesn't tell me the LUN number, it only tells me the GUID. I might RFE that to them too. I was talking to John about potentially implementing the "guid" style name, and thats what my question is based on. I'd rather not see the iqn.blahblahblah, so I was wondering whether I could use /guid/60.......123B or whether I should use /guid/${GUID}/${targetAlias}
Tommy
|
|
|
|
|
