Hi,

Randomly we get Open-iSCSI "conn errors" when connecting to an  
Infortrend A16E-G2130-4 storage array. We had discussed about this  
earlier in the list, see:

  http://tr.im/DVQm
  http://tr.im/DVQp

Open-iSCSI logs this:

===============================================
Nov  2 18:34:02 vz-17 kernel: ping timeout of 5 secs expired, last rx  
408250499, last ping 408249467, now 408254467
Nov  2 18:34:02 vz-17 kernel:  connection1:0: iscsi: detected conn  
error (1011)
Nov  2 18:34:03 vz-17 iscsid: Kernel reported iSCSI connection 1:0  
error (1011) state (3)
Nov  2 18:34:07 vz-17 iscsid: connection1:0 is operational after  
recovery (1 attempts)
Nov  2 18:34:52 vz-17 kernel: ping timeout of 5 secs expired, last rx  
408294833, last ping 408299833, now 408304833
Nov  2 18:34:52 vz-17 kernel:  connection1:0: iscsi: detected conn  
error (1011)
Nov  2 18:34:53 vz-17 iscsid: Kernel reported iSCSI connection 1:0  
error (1011) state (3)
Nov  2 18:34:57 vz-17 iscsid: connection1:0 is operational after  
recovery (1 attempts)
===============================================

Running on CentOS 5.4 with "iscsi-initiator-utils-6.2.0.871-0.10.el5";  
I think it's not a Open-iSCSI bug as Mike suggested at:

http://groups.google.com/group/open-iscsi/msg/fe37156096b2955f

I have only this error when connecting to Infortrend storage, and not  
with NetApp, Nexsan, etc. *connected in the same SAN*.

Using Wireshark I see a lot of "TCP Dup ACK", "TCP ACKed lost  
segment", etc. and iSCSI session finally ends in timeout, see a  
screenshot here:

http://tinyurl.com/ykpvckn

Using Wireshark IO graphs I get this strange report about TCP/IP errors:

http://tinyurl.com/ybm4m8x

And this is another report in the same SAN connecting to a NetApp:

http://tinyurl.com/ycgc8ul

Those TCP/IP errors only occurs when connecting to Infortrend  
storage.. and no with other targets in the same SAN (using same switch  
infrastructure); is there anyway to deal with this using Open-iSCSI?  
As I see in Internet, there're a lot of Infortrend's users suffering  
this behavior.

Thanks!

P.D: speed and duplex configuration is correct in all point, there  
aren't CRC errors in the switch.

-- 
Santi Saez
http://woop.es

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to