oracle:iscsi_in_deep_with_wireshark_and_tshark
Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
oracle:iscsi_in_deep_with_wireshark_and_tshark [2020/11/30 22:55] โ created hvillanueva | oracle:iscsi_in_deep_with_wireshark_and_tshark [2020/11/30 22:59] โ hvillanueva | ||
---|---|---|---|
Line 35: | Line 35: | ||
{{: | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Using ITT to filter the secuence of read and write operations. ===== | ||
+ | |||
+ | * You must follow the iSCSI data flow using the initiator task tag (ITT) field. | ||
+ | |||
+ | **Initiator Task Tag (ITT)โ.** Storage Networking Protocol Fundamentals This is 32 bits long. It contains a tag assigned by the initiator. An ITT is assigned to each iSCSI task. Likewise, an ITT is assigned to each SCSI task. A SCSI task can represent a single SCSI command or multiple linked commands. Each SCSI command can have many SCSI activities associated with it. A SCSI task encompasses all activities associated with a SCSI command or multiple linked commands. Likewise, an ITT that represents a SCSI task also encompasses all associated activities of the SCSI command(s). An ITT value is unique only within the context of the current session. The iSCSI ITT is similar in function to the FC fully qualified exchange identifier (FQXID). | ||
+ | |||
+ | * You must filter in wireshark using the field iscsi.initiatortasktag == 0xa1500f4a to follow the read or write operations. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | * You can create a flow graph with wirekshark | ||
+ | |||
+ | {{: | ||
+ | |||
+ | * Check - Limit do display filter | ||
+ | |||
+ | {{: | ||
oracle/iscsi_in_deep_with_wireshark_and_tshark.txt ยท Last modified: 2020/11/30 23:17 by hvillanueva