> -----Original Message----- > From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi- > ow...@vger.kernel.org] On Behalf Of Jeremy Linton > Sent: Monday, January 28, 2013 10:05 AM > To: Bart Van Assche > Cc: Hannes Reinecke; Ewan D. Milne; linux-scsi@vger.kernel.org > Subject: Re: [PATCH RFC 0/9] [SCSI] Enhanced sense and Unit Attention > handling > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 1/24/2013 8:38 AM, Bart Van Assche wrote: > > > Let me ask this another way. SAN users expect that the LUN list at the > > initiator side gets updated automatically after a SAN configuration change. > > How should a SAN system communicate to a SCSI initiator that the LUN > > list has been changed ? Some FC SAN systems send a LIP after a > > configuration change to force the initiator to rescan LUNs. But how to > > What I think your looking for is RSCN (Registered State Change > notification) . Hook that, and then check the name server. This will tell you > when ports get added/removed. You can then report luns against lun 0 of all > the known target ports. This allows you to transparently detect changes.
iSNS based SCN registrations - Open iSCSI facilitates a subset of such SCNs. http://linux.dell.com/files/presentations/Red_Hat_Summit_2009/Simplifying_Linux_iSCSI_management_with_iSNS-v0.7.pdf Now if you want SCSI to do SCN registrations that will be a topic to discuss.. though I would say we don't go down that path.. Since both FC/FCoE and iSCSI can register with an iSNS/SNS server this should solve it atleast for the login/logout scenario. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
