Hi Alexander,
I have that info now from mounting a Windows iSCSI target on both Windows and CentOS. Mounted on Windows the VPD information shown is:
VPD Page 83h Identifier
60003FF44DC75ADC95073BAE3FB24DA5
VPD Serial Number
0A1C3A57-5117-425A-9507-3BAE3FB24DA5
And then the result of the query you mentioned when mounted on CentOS is this:
[root@iscsi1 iscsi]# sg_inq --vpd --page=0x83 /dev/sdc
VPD INQUIRY: Device Identification page
Designation descriptor number 1, descriptor length: 20
designator_type: NAA, code_set: Binary
associated with the addressed logical unit
NAA 6, IEEE Company_id: 0x3ff
Vendor Specific Identifier: 0x44dc75adc
Vendor Specific Identifier Extension: 0x95073bae3fb24da5
[0x60003ff44dc75adc95073bae3fb24da5]
Designation descriptor number 2, descriptor length: 256
designator_type: vendor specific [0x0], code_set: Binary
associated with the addressed logical unit
vendor specific: mf?
Designation descriptor number 3, descriptor length: 51
transport: Internet SCSI (iSCSI)
designator_type: SCSI name string, code_set: Binary
associated with the target port
<< expected UTF-8 code_set>>
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...............
Designation descriptor number 4, descriptor length: 8
designator_type: Relative target port, code_set: Binary
associated with the target port
Relative target port: 0x0
Designation descriptor number 5, descriptor length: 45
transport: Internet SCSI (iSCSI)
designator_type: SCSI name string, code_set: UTF-8
associated with the target device that contains addressed lu
SCSI name string:
I couldn't test with fcinfo because it doesn't look like its available for Windows 2012 which is what I'm dealing with here. BTW while doing some more Googling on this issue I found this post for iscsitarget-devel. It goes over my head but maybe it makes sense for you?
http://iscsi-enterprise-target.996254.n3.nabble.com/scsi-id-scsi-sn-and-vpd-83-type-8h-td11560.html
Thanks,
Doug
On May 4, 2013, at 10:51 PM, Alexander Nezhinsky <nezhinsky@xxxxxxxxx> wrote:
> On Sun, May 5, 2013 at 12:08 AM, Doug Clow <doug.clow@xxxxxxxxxxx> wrote:
>> Hi Alexander,
>>
>> This is very informative, thanks. The COMSTAR disk that Windows liked was actually
>> a fibre channel device and this Linux machine doesn't have a fibre adapter.
>> But I have an even better idea, I'll make an iSCSI target in Windows and then
>> run the query you showed me and report my findings.
>>
>> Regards,
>> Doug
>
>> On May 4, 2013, at 7:39 AM, Alexander Nezhinsky <nezhinsky@xxxxxxxxx> wrote:
>>
>>> Could you mount the same target your Windows is happy about from Linux
>>> and run sg_inq?
>>>
>>> Then we shall see which of the descriptors appears on Windows, and
>>> this may help to pinpoint
>>> the problem. If we know that Windows expects another descriptor type,
>>> it is not too hard to add it to VPD page in tgt.
>
> Doug,
>
> We'd bee better off if we understand the expectations of Windows initiator
> by comparing its report and the actually returned VPD data.
> So we need to connect the *same* target from both Windows and Linux.
> Could you connect to Windows iscsi target locally, from the Windows machine?
>
> And regarding fibre channel in Windows, does this tool provide any useful info?
> http://www.microsoft.com/en-us/download/details.aspx?id=17530
>
> Alexander
> --
> To unsubscribe from this list: send the line "unsubscribe stgt" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
