Re: Setting iSCSI SCSI ID with LIO?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2015-11-30 at 02:54 +0000, Sam McLeod wrote:
> >Please don't top post.  It's annoying.
> 
> Sorry, don't use mailing lists much these days.
> >
> >I'm still not sure what you mean by 'SCSIID'.
> 
> The SCSIID is comprised of:
> 
> - NAA 6, IEEE Company_id: 0x1405
> - Vendor Specific Identifier: 0xbff3f42a4
> - Vendor Specific Identifier Extension: 0x9d84cfcb64e2b933
> 
> Which is an ID of:
> 
> 0x6001405bff3f42a49d84cfcb64e2b933
> 

Ok, good.

> 
> >That is, you need to make sure that:
> >
> >   /sys/kernel/config/target/core/$HBA/$DEV/wwn/vpd_unit_serial
> >
> >contains the same value across device + export fail-over.
> >
> >Have you confirmed that yet..?
> 
> We can set the vpd_unit_serial, that is not our issue.
> What needs to be set on the target is the Company_id, VSI and VSIE as above.

The Company ID, VSI, and VSIE are generated by LIO based upon the
current vpd_unit_serial configfs attribute value.

So as long as vpd_unit_serial is persistent, and the same value for
backend devices across export failover to different nodes, Xen will
always see the same EVPD information.

Are you saying that vpd_unit_serial is already persistent across export
failover, but Xen is still having problems..?

Have you confirmed with sg_inq -i both before and after the export
failover occurs..?

--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux