That's what I thought too since that's true for FC devices, but disable is set to no in iscsi.conf (as it ships that way).
-------------------------------------------------- From: <[EMAIL PROTECTED]> Sent: Thursday, August 07, 2008 2:28 PM To: "William Yang" <[EMAIL PROTECTED]> Cc: <[email protected]> Subject: Re: [storage-discuss] iSCSI initiator on Solaris 10 > i'm still fairly new at iSCSI, but you probably have mpxio > enabled in your iscsi.conf: > > > # tail /kernel/drv/iscsi.conf > # Global mpxio-disable property: > # > # To globally enable MPxIO on all iscsi ports set: > # mpxio-disable="no"; > # > # To globally disable MPxIO on all iscsi ports set: > # mpxio-disable="yes"; > # > mpxio-disable="no"; > > > c1t0100000C76949240000002A0045DE016Ad0 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ^^^^^^^ target num ^^^^^^^^^^^^^^ > > the target-num (tX) gets changed when multipathing/mpxio > are involved. if mpxio is disabled, you'll get "short names", > as you say. > > /andrew > > > William Yang wrote: >> In a lot of the documents and blogs online, when working with iSCSI >> people seem to get a really long target ID (the GUID?) when working with >> devices in /dev/dsk (e.g. c1t0100000C76949240000002A0045DE016Ad0). For >> some reason, I get short target numbers much like on a local SCSI >> controller (c1t0d0). Is there a configuration change to use GUIDs, or is >> this a configuration change that needs to be made on the target side? >> I'm running Solaris 10 update 5 (x86 and SPARC). >> Thanks, >> William Yang >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> storage-discuss mailing list >> [email protected] >> http://mail.opensolaris.org/mailman/listinfo/storage-discuss > _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
