oracle:iscsi_in_deep_with_wireshark_and_tshark
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
oracle:iscsi_in_deep_with_wireshark_and_tshark [2020/11/30 23:13] – hvillanueva | oracle:iscsi_in_deep_with_wireshark_and_tshark [2020/11/30 23:17] (current) – hvillanueva | ||
---|---|---|---|
Line 135: | Line 135: | ||
===== Status (RFC7143) ===== | ===== Status (RFC7143) ===== | ||
+ | {{: | ||
+ | |||
+ | * WireShark filter for SCSI status of the command | ||
+ | |||
+ | {{: | ||
+ | |||
+ | * WireShark filter for status response | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Reject - Reason - RFC7143 ===== | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Note 1: For iSCSI, Data-Out PDU retransmission is only done if the target requests retransmission with a recovery R2T. However, if this is the data digest error on immediate data, the initiator may choose to retransmit the whole PDU, including the immediate data. | ||
+ | |||
+ | Note 2: A target should use this reason code for all invalid values of PDU fields that are meant to describe a task, a response, or a data transfer. Some examples are invalid TTT/ITT, buffer offset, LUN qualifying a TTT, and an invalid sequence number in a SNACK. | ||
+ | |||
+ | WireShark filter to check if iscsi.opcode is present | ||
+ | |||
+ | iscsi.reject.reason && iscsi | ||
+ | |||
+ | (iscsi.reject.reason==0x00 or iscsi.reject.reason==0x02 or iscsi.reject.reason==0x08 or iscsi.reject.reason==0x18 or iscsi.reject.reason==0x28 or iscsi.reject.reason==0x30 or iscsi.reject.reason==0x40 or iscsi.reject.reason==0x00 or iscsi.reject.reason==0x01 or iscsi.reject.reason==0x80 or iscsi.reject.reason==0xff) && iscsi | ||
oracle/iscsi_in_deep_with_wireshark_and_tshark.1606796006.txt.gz · Last modified: 2020/11/30 23:13 by hvillanueva