Re: iSCSI - Question about StatSN and NOP-In PDU

[Luben Tuikov <ltuikov@yahoo.com>]

--- Mark Freedkin <Mark.Freedkin@quantum.com> wrote:
> 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?

StatSN is not advanced when then Target initiates the NOP-In.

I.e. for target initiated NOP-In (i.e. NOT as a reply to a NOP-Out)
the Initiator Task Tag MUST be set to the reserved value (10.19)
(since it is not a reply). And thus, no status is being reported,
so StatSN is NOT advanced (10.19.2).

-- 
Luben

[[Reference used: iSCSIv19 as of 2002/11/03.]]


.


=====
--

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com