SRP and login with initiator port identifier already in use

[Nixon, Bob]

* From the T10 Reflector (t10 at t10.org), posted by:
* "Nixon, Bob" <Bob.Nixon at emulex.com>
*
Rob, my interpretation of this was a little different.  I thought this was to be used within the SRP implementation to establish multiple paths that were _totally invisible_ to the SCSI initiator and target.  They were to be used at the discretion of the SRP SCSI delivery system for performance enhancement, failover, etc of an I_T nexus.  In general, SCSI target devices / ports / LUs were be unaware of the channel structure used by SRP to implement an I_T nexus.  

If this were the intention, the behaviors you noted for reservations and access contols would fall out naturally.

Or was there somethiing in the drinks at that meeting that I had a low tolerance for?

   - Bob

"Elliott, Robert" wrote:
> 
> * From the T10 Reflector (t10 at t10.org), posted by:
> * "Elliott, Robert" <Robert.Elliott at compaq.com>
> *
> This is how I understand SRP targets should behave if a login with a
> MULTI-CHANNEL ACTION of 01h occurs that specifies an initiator port
> identifier which is already in use.
> 
> The logical units behind the target treat the login as if a separate
> initiator port identifier were being used.  In most regards, everything that
> comes in would run independently.
> 
> If a reservation has been established, however, the permission would be
> checked only on the initiator port identifier sent during login.  Thus one
> reservation can apply to multiple "initiator ports".
> 
> Access control transport ID checkign will behave the same way.
> 
> UAs and other things for "other initiators" would treat this new channel
> nexus as having a different initiator.
> 
> Any agreement or disagreement?  What should SRP say to clarify this state?
> Is the SAM-2 mapping annex where this needs to be explained?
> ---
> Rob Elliott, Compaq Server Storage
> Robert.Elliott at compaq.com
> 
> *
> * For T10 Reflector information, send a message with
> * 'info t10' (no quotes) in the message body to majordomo at t10.org
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org