SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


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

    iSCSI : LUN field in NOP-OUT & NOP-IN PDUs.


    • To: IPS Reflector <ips@ece.cmu.edu>
    • Subject: iSCSI : LUN field in NOP-OUT & NOP-IN PDUs.
    • From: Santosh Rao <santoshr@cup.hp.com>
    • Date: Mon, 23 Apr 2001 12:14:54 -0700
    • Content-Type: multipart/mixed;boundary="------------900380A96804E78CEAFF3B07"
    • Organization: Hewlett Packard, Cupertino.
    • Sender: owner-ips@ece.cmu.edu

    
    At the risk of raising a subject that has been beaten to death [and
    still not resolved ?], could someone please clarify on what was the
    outcome of the prior thread discussing the usage of the LUN field in
    NOP-OUT & NOP-IN PDUs ?
    
    As has been discussed in the past, the NOP-OUT and NOP-IN PDUs are
    transport specific and are used without any LUN context. Hence, it is
    not clear why a LUN field is required in either the NOP-OUT or NOP-IN
    PDUs. 
    
    Some side notes on this subject :
    a) the LUN field description is missing in the NOP-OUT description and
    it is not clear from either the figure or the text whether this field
    can be reserved. If so, what would be the reserved value for LUN in
    NOP-OUT ? 
    
    b) The NOP-IN PDU description shows a value of LUN 0 as reserved in the
    NOP-IN PDU diagram. Is not LUN 0 a valid LU number for a LU (?) 
    
    - Santosh
    begin:vcard 
    n:Rao;Santosh 
    tel;work:408-447-3751
    x-mozilla-html:FALSE
    org:Hewlett Packard, Cupertino.;SISL
    adr:;;19420, Homestead Road, M\S 43LN,	;Cupertino.;CA.;95014.;USA.
    version:2.1
    email;internet:santoshr@cup.hp.com
    title:Software Design Engineer
    x-mozilla-cpt:;21088
    fn:Santosh Rao
    end:vcard
    


Home

Last updated: Tue Sep 04 01:04:55 2001
6315 messages in chronological order