-----Original Message----- From: Mike Christie [mailto:[email protected]] Sent: Thursday, June 16, 2011 3:22 PM To: [email protected] Cc: Seth Simons; Kallickal, Jayamohan Subject: Re: unable to login to targets with be2iscsi
On 06/16/2011 02:31 PM, Seth Simons wrote: > ...and here's some wireshark dumps showing this happen, from server > reboot until the initramfs prompt. From this point, i ran iscsistart > -f followed by iscsistart -b. > Jay, Did you see the wireshark trace in the previous mail? The problem starts in packet 8687. This is open-iscsi logging in using be2iscsi (I can tell by the isid). The other logins in the trace seem to be emulex bios initiator ones or something else (I do not know your isid off the top of my head). Yes, Pkt 8687 is login from open-iscsi. I would assume the login response came as the Ack wentup from 1 to 86 (pkt 8688). Looking at the trace, I am unable to say who (iniitaor/target) initiated the Reset Is it possible to get a trace in both directions? A couple packets after we login the RSTs start happening. Packet 8690 is the first one we see the initiator send a RST,ACK. This is in response to the target's RST right? You cannot see the target packets in the trace so I am just assuming this is what the initiator does and does not do it for some other reason. It does not seem to be iscsi related, because after that initial sequence we see other tcp connections get created and reset, but no iscsi commands even sent on them. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
