Re: LUN field in R2T
[email protected] Wed, 2 Jan 2008 17:19:36 -0500
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <OFFA6F0708.4EAA4550-ON852573C4.007A408F-852573C4.007AA4C6@attotech.com> |
Hi Bill, I know from experience that some initiators will fill in the LUN field in the data out with the actual LUN specified in the SCSI write. While that may not be compliant with 10.8.5, you may see interop problems if you're depending on the initiator to echo that LUN back to you. regards, david Java: The elegant simplicity of C++ and the blazing speed of smalltalk. David J Cuddihy Principal Engineer ATTO Technology, Inc. (716) 691-1999 x157 www.attotech.com Power Behind the Storage [email protected] 01/02/2008 01:28 PM To <[email protected]> cc Subject [Ips] LUN field in R2T Just a quick clarification: 10.8.5. Target Transfer Tag [...]The Target Transfer Tag and LUN are copied in the outgoing data PDUs and are only used by the target. Does this mean that the LUN field in the R2T does not need to contain the actual LUN number specified by the SCSI write? Since the field is ?only used by the target? I assume this text means that the target may place anything it wants in the LUN field of the R2T and have it echoed back by the initiator. _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips