This class parses a NOP-Out message defined in the iSCSI Standard (RFC3720).
A NOP-Out may be used by an initiator as a "ping request" to verify that a connection/session is still active and all its components are operational. The NOP-In response is the "ping echo".
A NOP-Out is also sent by an initiator in response to a NOP-In.
A NOP-Out may also be used to confirm a changed ExpStatSN
if another PDU will not be available for a long time.
Upon receipt of a NOP-In with the Target Transfer Tag set to a valid value (not the reserved 0xffffffff
), the initiator MUST respond with a NOP-Out. In this case, the NOP-Out Target Transfer Tag MUST contain a copy of the NOP-In Target Transfer Tag.
These fields have these specific meanings:
Initiator Task Tag:@author Volker Wildi
The NOP-Out MUST have the Initiator Task Tag set to a valid value only if a response in the form of NOP-In is requested (i.e., the NOP-Out is used as a ping request). Otherwise, the Initiator Task Tag MUST be set to0xffffffff
.When a target receives the NOP-Out with a valid Initiator Task Tag, it MUST respond with a Nop-In Response (see Section 10.19 NOP-In).
If the Initiator Task Tag contains
0xffffffff
, theI bit
MUST be set to1
and theCmdSN
is not advanced after this PDU is sent.Ping Data
Ping data are reflected in the NOP-In Response. The length of the reflected data are limited toMaxRecvDataSegmentLength
. The length of ping data are indicated by theDataSegmentLength
.0
is a valid value for theDataSegmentLength
and indicates the absence of ping data.
|
|
|
|