Hi Donald, Hi Lee-man, Thanks for the reply. Both replies were helpful and both replies actually clarified my concepts. And I realized, the question was not clear....You were kind enough to reply in detail even when the question of was not clear !
*The Lee-man*, your guess was right. I was thinking something like that and I realized it makes no sense. *Donald*: Yes, you are right. I took this point of yous "*then doing normal I/O to that iSCSI disk will provide all the traffic you will typically need*"....the wireshark showed me ! I'm a complete novice in Open-iSCSI yet very much interested in it. Please excuse my simple questions. It is written, Open-iSCSI acts as "*kernel driver*" between "*block layer*" and "*network layer*". Therefore following two questions: - Linux block layer perform IO scheduling IO submissions to storage device driver. If there is a physical device, the block layer interacts with it through SCSI mid layer and SCSI low level drivers. So, how *actually* a software initiator (*Open-iSCSI*) interacts with "*block layer*"? I will be really grateful if you can explain me. - What confuses me, where does the "*disk driver*" comes into play? Thanks :-) On Monday, November 4, 2019 at 2:32:00 PM UTC+1, Donald Williams wrote: > > Hello, > > Can you provide a little more info? iSCSI is for storage, so unless > your 'server' is running an iSCSI target service there won't be 'iSCSI' > traffic to monitor. > > If you do have an iSCSI service running then providing a disk via that > service to the 'client' then doing normal I/O to that iSCSI disk will > provide all the traffic you will typically need. I.e. discovering the > device, formatting the disk, doing writes and reads, etc. > > What is it that you are trying to do? iSCSI is the transport for SCSI > commands over a network. You can use SCSI tools to generate SCSI commands > to that disk, then the iSCSI initiator on the 'client' will create the > respective iSCSI packets. > > Regards, > Don > > > > > On Mon, Nov 4, 2019 at 5:49 AM Bobby <[email protected] <javascript:>> > wrote: > >> Hi >> >> I have two virtual machines. One is a client and other is a sever (SAN). >> I am using Wireshark to analyze the iSCSI protocols between them. >> >> Someone recommended me, in addition to a packet analyzer, I can also use >> a packet generator. Any good packet generator for iSCSI client/server model? >> >> Thanks >> >> -- >> You received this message because you are subscribed to the Google Groups >> "open-iscsi" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/open-iscsi/8a89dcdb-8fae-4c97-9a76-db621b01bcaf%40googlegroups.com >> >> <https://groups.google.com/d/msgid/open-iscsi/8a89dcdb-8fae-4c97-9a76-db621b01bcaf%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/open-iscsi/7fe0dd60-7da1-4027-9f1e-c5c717c94ddd%40googlegroups.com.
