swejis wrote:
> Hello everyone. I'm not very experienced with iscsi, so please excuse
> me if asking stupid questions.
> 
> I'm evaluation opensuse 11 (Beta1) for my servers and have found some
> worrying errors in the log. The following error quite frequently shows
> up.
> 
> May  5 21:15:05 manjula klogd:  connection1:0: ping timeout of 5 secs
> expired, last rx 4626267449, last ping 4626264949, now 4626269949


It looks like the nop code it broken. If you use


node.conn[0].timeo.noop_out_interval = 0
node.conn[0].timeo.noop_out_timeout = 0

Set that for each portal or set it in your /etc/iscsi/iscsi.conf file 
and then redo discovery.


> May  5 21:15:05 manjula klogd:  connection1:0: detected conn error
> (1011)
> May  5 21:15:05 manjula iscsid: Kernel reported iSCSI connection 1:0
> error (1011) state (3)
> May  5 21:15:09 manjula iscsid: connection1:0 is operational after
> recovery (1 attempts)
> 
> The target is the infamous Promise m500i and the initiator "transport
> class version 2.0-869. iscsid version 2.0-868"
> Nic : Broadcom NetXtreme BCM5721 Gigabit Ethernet PCI Express (tg3)
> Kernel  2.6.25-rc9-17-default x86_64
> 
> There is really no load on this system yet. I used a sniffer to record
> the traffic and it seem the target "all the sudden" sends a reset
> (frame 65). I'm not sure if this happens at the same time as the error
> printed to the log. I have uploaded the capture file here:
> http://www.wehay.com/iscsi.cap.gz
> 
> To my first stupid question. The target is equipped with 2 x 1GB nics
> having address 192.168.43.5 & 6. When I did the discovery I only
> pointed to one of these addresses still both where found  and used
> (magic). Also I noticed that every lun is registered twice (sdc & d

This is expected. Normally if you do discovery to one port it will tell 
you about all of them on the target.

The multiple sd entries is also expected. The scsi layer does not know 
or care if it can see the same LU from different paths, so it creates a 
sd everytime it sees it. You could then use multipath to assemble all 
the sds into one multipath device.

> for lun1 etc), is the reason for this performance, fail over or
> perhaps both ? I've spotted in the target the following setting "Max
> Connections 1" (non-configurable) and was thinking perhaps this reset
> was related to this. I have left all configuration to it's defaults
> only changing the login information.
> 

max connections is not used so do not worry about it.

--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to