Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id gB32EGp05091
	for ips-outgoing; Mon, 2 Dec 2002 21:14:16 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from mail.ivivity.com ([64.238.111.99])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id gB32ECH05084;
	Mon, 2 Dec 2002 21:14:12 -0500 (EST)
Received: by ATLOPS with Internet Mail Service (5.5.2653.19)
	id <Y12VG9ND>; Mon, 2 Dec 2002 21:14:11 -0500
Message-ID: <AEC4671C8179D61194DE0002B328BDD2085F@ATLOPS>
From: Eddy Quicksall <eddy_quicksall@ivivity.com>
To: Julian Satran <Julian_Satran@il.ibm.com>,
   Mark Freedkin
	 <Mark.Freedkin@quantum.com>
Cc: ips@ece.cmu.edu, owner-ips@ece.cmu.edu
Subject: RE: iSCSI - Question about StatSN and NOP-In PDU
Date: Mon, 2 Dec 2002 21:14:09 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C29A71.AA4E37F0"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C29A71.AA4E37F0
Content-Type: text/plain;
	charset="iso-8859-1"

Section 10.19 says:
 
Otherwise, when a target sends a NOP-In that is not a response to a Nop-Out
received from the initiator, the Initiator Task Tag MUST be set to
0xffffffff and the Data Segment MUST NOT contain any data (DataSegmentLength
MUST be 0).

Section 10.19.2 says:
 
The StatSN field will always contain the next StatSN. However, when the
Initiator Task Tag is set to 0xffffffff StatSN for the connection is not
advanced after this PDU is sent.

 
So, this means you should not advance StatSN as you have suggested.
 
Eddy

-----Original Message-----
From: Julian Satran [mailto:Julian_Satran@il.ibm.com]
Sent: Monday, December 02, 2002 8:18 PM
To: Mark Freedkin
Cc: ips@ece.cmu.edu; owner-ips@ece.cmu.edu
Subject: Re: iSCSI - Question about StatSN and NOP-In PDU



Mark, 

I am not sure that I understand what is exceptional in this situation. 
I assume that your Nop-In has TTT (it is ping) and requests a Nop-Out. 


Julo 



Mark Freedkin <Mark.Freedkin@quantum.com> 
Sent by: owner-ips@ece.cmu.edu 


03/12/02 02:04 


To
ips@ece.cmu.edu 

cc

Subject
iSCSI - Question about StatSN and NOP-In PDU

	




Our iSCSI target implementation generates an unsolicited NOP-In PDU as a
"ping" mechanism after 5 minutes of inactivity within an established
connection.  We also increment the StatSN that is carried within that PDU.
If the initiator happens to send a PDU at the exact same time as our NOP-In
PDU, the initiator and target StatSN values will get out-of-sync.

Is there anything in the Draft 19-90 specification that describes how to
handle this unique condition?

Mark Freedkin
Quantum Corporation





------_=_NextPart_001_01C29A71.AA4E37F0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 6.00.2800.1126" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN 
class=054021002-03122002>Section&nbsp;10.19 says:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial color=#0000ff size=2><FONT face=Courier color=#000000>
<P>Otherwise, when a target sends a NOP-In that is not a response to a Nop-Out 
received from the initiator, the Initiator Task Tag MUST be set to 0xffffffff 
and the Data Segment MUST NOT contain any data (DataSegmentLength MUST be 
0).</P></FONT></FONT></DIV>
<DIV><SPAN class=054021002-03122002><FONT face=Arial color=#0000ff 
size=2>Section&nbsp;10.19.2 says:</FONT></SPAN></DIV>
<DIV><SPAN class=054021002-03122002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=054021002-03122002><FONT face=Arial color=#0000ff size=2><FONT 
face=Courier color=#000000>
<P>The StatSN field will always contain the next StatSN. However, when the 
Initiator Task Tag is set to 0xffffffff StatSN for the connection is not 
advanced after this PDU is sent.</P></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=054021002-03122002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=054021002-03122002><FONT face=Arial color=#0000ff size=2>So, 
this means you should not advance StatSN as you have 
suggested.</FONT></SPAN></DIV>
<DIV><SPAN class=054021002-03122002><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=054021002-03122002><FONT face=Arial color=#0000ff 
size=2>Eddy</FONT></SPAN></DIV>
<BLOCKQUOTE>
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Julian Satran 
  [mailto:Julian_Satran@il.ibm.com]<BR><B>Sent:</B> Monday, December 02, 2002 
  8:18 PM<BR><B>To:</B> Mark Freedkin<BR><B>Cc:</B> ips@ece.cmu.edu; 
  owner-ips@ece.cmu.edu<BR><B>Subject:</B> Re: iSCSI - Question about StatSN and 
  NOP-In PDU<BR><BR></FONT></DIV><BR><FONT face=sans-serif size=2>Mark,</FONT> 
  <BR><BR><FONT face=sans-serif size=2>I am not sure that I understand what is 
  exceptional in this situation.</FONT> <BR><FONT face=sans-serif size=2>I 
  assume that your Nop-In has TTT (it is ping) and requests a Nop-Out.</FONT> 
  <BR><BR><BR><FONT face=sans-serif size=2>Julo</FONT> <BR><BR><BR>
  <TABLE width="100%">
    <TBODY>
    <TR vAlign=top>
      <TD width="40%"><FONT face=sans-serif size=1><B>Mark Freedkin 
        &lt;Mark.Freedkin@quantum.com&gt;</B> </FONT><BR><FONT face=sans-serif 
        size=1>Sent by: owner-ips@ece.cmu.edu</FONT> 
        <P><FONT face=sans-serif size=1>03/12/02 02:04</FONT> </P>
      <TD width="59%">
        <TABLE width="100%">
          <TBODY>
          <TR>
            <TD>
              <DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
            <TD vAlign=top><FONT face=sans-serif size=1>ips@ece.cmu.edu</FONT> 

          <TR>
            <TD>
              <DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
            <TD vAlign=top>
          <TR>
            <TD>
              <DIV align=right><FONT face=sans-serif size=1>Subject</FONT></DIV>
            <TD vAlign=top><FONT face=sans-serif size=1>iSCSI - Question about 
              StatSN and NOP-In PDU</FONT></TR></TBODY></TABLE><BR>
        <TABLE>
          <TBODY>
          <TR vAlign=top>
            <TD>
            <TD></TR></TBODY></TABLE><BR></TR></TBODY></TABLE><BR><BR><BR><FONT 
  size=2><TT>Our iSCSI target implementation generates an unsolicited NOP-In PDU 
  as a<BR>"ping" mechanism after 5 minutes of inactivity within an 
  established<BR>connection. &nbsp;We also increment the StatSN that is carried 
  within that PDU.<BR>If the initiator happens to send a PDU at the exact same 
  time as our NOP-In<BR>PDU, the initiator and target StatSN values will get 
  out-of-sync.<BR><BR>Is there anything in the Draft 19-90 specification that 
  describes how to<BR>handle this unique condition?<BR><BR>Mark 
  Freedkin<BR>Quantum 
Corporation<BR><BR></TT></FONT><BR></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C29A71.AA4E37F0--
