This class parses a NOP-In message defined in the iSCSI Standard (RFC3720).
NOP-In is either sent by a target as a response to a NOP-Out, as a "ping" to an initiator, or as a means to carry a changed ExpCmdSN
and/or MaxCmdSN
if another PDU will not be available for a long time (as determined by the target).
When a target receives the NOP-Out with a valid Initiator Task Tag (not the reserved value 0xffffffff
), it MUST respond with a NOP-In with the same Initiator Task Tag that was provided in the NOP-Out request. It MUST also duplicate up to the first MaxRecvDataSegmentLength
bytes of the initiator provided Ping Data. For such a response, the Target Transfer Tag MUST be 0xffffffff
.
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
).
This fields have these specific meanings:
A LUN MUST be set to a correct value when the Target Transfer Tag is valid (not the reserved value 0xffffffff
).
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.
@author Volker Wildi
|
|
|
|