If ImmediateData is set to Yes and InitialR2T is set to No, then the initiator MAY send unsolicited immediate data and/or one unsolicited burst of Data-Out PDUs. If you look at the Login command header(packet.no 23) from initiator the ImmediateData=Yes and InitialR2T=no and if you look at the Login response(packet.no 24)header the Immediatedata=NO and InitialR2T=yes. So no data is exactly written to the target and no error responses were seen.Let me know if i am missing anything here. The attached link reflects the capture BEFORE I made that change.Īt least in the packet capture you uploaded the total packet length displaying is 102 bytes (from initiator for the data write case) which means 14bytes eth header + 20 bytes IP header + 20 bytes TCP Header + 48 bytes ISCSI header. It made no difference in the final outcome however. Update: I noticed that ExpCmdSN was looking a little higher than would be expected.
It should also be noted that if I accept this Write(10) request and handle it as defined in the spec, it will continue Sending me 0 length Write requests until the the Initiator reports "Device I/O Error". it isn't very long.ĭownload the Capture of MS iSCSI initiator making bad requests to my iSCSI Development Server I've attached a capture if anyone is so motivated to look at it. I expected, with 1 logical block being written, that the DataSegmentLength field would be 0x00000200 (512 bytes). My problem, however, which I do not necessarily blame on the client, is that the first Write(10) command that comes to my server appears to request that I write 1 Logical Block to the disk, however, the payload for the packet is not existent and the "DataSegmentLength" field is 0. I got through a whole bunch of it, comparing the results of my server against a known SAN device.
There's a LOT of setup required before you can even get to doing your first Read and Write commands. Things have been going relatively smoothly until recently.
Anyone here familiar with iSCSI protocol? I have been sniffing around at some iSCSI traffic and have been working on making a compliant iSCSI server app.
0 kommentar(er)
