HP-UX iSCSI Software Initiator Support Guide (Edition 7)

Table 6 Software Interface Driver Statistics (continued)
Description of FieldCLiscsiutil Statistic
indicates that the Expected Data Transfer Length in the I/O
request was not sufficient.
The total number of I/Os that failed due to a response code
error in the SCSI response PDU. This means that the target
TNumber of I/O failures due to response
code errors
failed to execute the I/Os. A large value here could indicate
that the target is not functioning properly.
The total number of empty Data-In PDUs received by the
initiator.
INumber of Data-In PDUs received without
data
The total number of Request to Transfer (R2T) PDUs from the
target that had an incorrect buffer offset or Data Transfer Length
TNumber of invalid R2T PDUs received
in them. A non-zero value for this stat indicates that the target
is not adhering to the error recovery policy negotiated by the
initiator.
The total number of Request to Transfer (R2T) PDUs that could
not be honored by the initiator due to resource constraints at
DNumber of I/Os that failed to respond to an
R2T due to kernel memory allocation failures
the initiator. A non-zero value for this stat indicates that the
initiator is intermittently running out of resources while handling
iSCSI I/O traffic.
The number of Request to Transfer (R2T) requests sent by the
target for a Read operation. This is an unexpected behavior.
TNumber of unexpected R2T PDUs received
during a Read I/O
The total number of data-in PDUs received by the initiator while
the initiator was doing a write operation to the target. This is
an unexpected behavior.
TNumber of unexpected Data-In PDUs
received during a Write I/O
The total number of I/O requests where the target had an
incorrect residual count value and where the status for the I/O
TNumber of Data-In PDUs with incorrect
residual count
was sent as part of the last Data-In PDU. This might happen
when the target indicated an underflow condition but the
residual count value did not match the expected residual count.
The total number of I/O requests where the target had an
incorrect residual count value set. This might happen when the
TNumber of SCSI Response PDUs with
incorrect residual count
target indicated an underflow condition but the residual count
value did not match the expected residual count. The response
PDU in this case was sent as a separate PDU by the target.
The total number of Request to Transfer (R2T) PDUs that could
not be honored by the initiator due to resource constraints at
DNumber of I/Os that failed to respond to an
R2T due to kernel memory allocation failures
the initiator. A non-zero value for this stat indicates that the
initiator is intermittently running out of resources while handling
iSCSI I/O traffic.
The total number of I/O failures in the inbound path resulting
from a failure of msgpullup call.
DNumber of I/O failures due to streams
message concatenation memory allocation
failures
The total number of PDUs that were received where the status
sequence number of the PDU does not match the expected
D/TNumber of holes seen in the status
sequencing
status sequence number. For error recovery level zero, this will
cause the initiator to do a Session level logout.
The number of asynchronous events received by the initiator.INumber of SCSI Async events received
The total number of times the target sent an asynchronous event
with the AsyncEvent set as "target requests logout".
INumber of "target requests logout" Async
events received
The total number of times the target sent an asynchronous event
with the AsyncEvent set as "target will drop connection".
INumber of "target will drop connection"
Async events received
D.1 iSCSI Software Interface Driver Statistics 57