SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


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

    RE: iSCSI: LUN in a ping



    Yes, I remember that but the necessity for the target to set it should be up
    to the target because the initiator should not be trying to interpret it (it
    should only be required to echo it).
    
    Is there a case where the initiator will interpret the LUN?
    
    Eddy
    
    -----Original Message-----
    From: Julian Satran [mailto:julian@cs.haifa.ac.il]
    Sent: Wednesday, January 22, 2003 12:43 AM
    To: 'Eddy Quicksall'; ips@ece.cmu.edu
    Subject: RE: iSCSI: LUN in a ping
    
    
    TTT & LUN uniquely identify the "origin" (if target is a "composite"
    each of the parts can issue their own TTTs - no coordination needed).
    
    Regards,
    Julo
    
    
    -----Original Message-----
    From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu] On Behalf Of
    Eddy Quicksall
    Sent: 22 January, 2003 00:07
    To: ips@ece.cmu.edu
    Subject: iSCSI: LUN in a ping
    
    
    Does anyone know why we added "the LUN must be valid" for a target
    initiated ping? It would seem that it is N/A when the ping is just being
    used to checkup on the connection.
     
    What will the initiator do with the LUN anyway?
     
    10.19.3 LUN
    A LUN MUST be set to a correct value when the Target Transfer Tag is
    valid (not the reserved value 0xffffffff).
     
    Eddy
    mailto: Eddy_Quicksall@iVivity.com
     
    


Home

Last updated: Wed Jan 22 14:19:28 2003
12227 messages in chronological order