Hi Nab, This is with reference to RFC 3720 section 10.18. Which stats that the unsolicited NOP-in from target as ping should contain valid TTT and this should be carried on to NOP-Out. However, I do not see this is happening. The NOP-out is holding the TTT of 0xFFFFFFFF instead of a valid TTT. This looks like RFC break in LIO? Please comment. 10.18. NOP-Out <SNIP> 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. I have attached pcap. The concerning frames are 10 and 11. [root@wfsc iscsi]# uname -a Linux wfsc 3.14.0-rc6+ #2 SMP Tue Apr 29 04:55:14 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux [root@wfsc iscsi]# [root@wfsc iscsi]# cat /sys/kernel/config/target/iscsi/lio_version Datera Inc. iSCSI Target v4.1.0 [root@wfsc iscsi]# Thanks, Arshad
Attachment:
unsolicited_nopin_lio.pcapng
Description: Binary data
