Recommended version of Kernel, Initiator, Target

Hello open-iscsi-Group! I fail to run iSCSI over ISER (Infiniband) transport (see my older posting for the logs). iSCSI over TCP over IPoIB (Infiniband) runs without problems. So I assume the iSCSI-configuration of Target and Initiator is ok. This is my setup: * Hardware :Peer-to-Peer connected

Re: Recommended version of Kernel, Initiator, Target

Dr. Volker Jaenisch wrote: > Hello open-iscsi-Group! > > I fail to run iSCSI over ISER (Infiniband) transport (see my older > posting for the logs). > iSCSI over TCP over IPoIB (Infiniband) runs without problems. So I > assume the iSCSI-configuration of Target and Initiator is ok. > > This is my

[PATCH 0/4 2.6.28] cxgb3i - Add iSCSI driver

Hi, everyone, Please review our new version of the iSCSI Initiator drivers for Chelsio S3 adapters. The cxgb3i driver provides iscsi acceleration (PDU digest offload and payload direct-placement) to the open-iscsi initiator. It accesses the hardware through the cxgb3 module. The accelerated i

[PATCH 2/4 2.6.28] cxgb3 - handle ARP replies for private iSCSI IP address

[PATCH 2/4 2.6.28] cxgb3 - handle ARP replies for private iSCSI IP address From: Karen Xie <[EMAIL PROTECTED]> stg can be tricky ... [adding @adapter in cxgb3_arp_process doxygen header] The accelerated iSCSI traffic uses a private IP address unknown to the OS. The driver has to reply to ARP req

[PATCH 1/4 2.6.28] cxgb3 - manage a private ip address for iSCSI

[PATCH 1/4 2.6.28] cxgb3 - manage a private ip address for iSCSI From: Karen Xie <[EMAIL PROTECTED]> Create a per port sysfs entry to pass an IP address to the NIC driver, and a control call for the iSCSI driver to grab it. The IP address is required in both drivers to manage ARP requests and

[PATCH 3/4 2.6.28] open-iscsi - support for digest offload and payload DDP

[PATCH 3/4 2.6.28] open-iscsi - support for digest offload and payload DDP. From: Karen Xie <[EMAIL PROTECTED]> Added PDU digest offload and payload direct-placement support in open-iscsi. Signed-off-by: Karen Xie <[EMAIL PROTECTED]> --- drivers/scsi/iscsi_tcp.c| 61

Re: Recommended version of Kernel, Initiator, Target

Hello Mike! Mike Christie wrote: > On the initiator side running 2.6.24 and 2.0.865.15, I > # start opensm and give the initaitor ib port an ip. > # start open-iscsi etc/init.d/open-iscsi start > # do discovery to a the port setup on the target in the attached script. > > iscsiadm -m discovery -t

Re: Recommended version of Kernel, Initiator, Target

Hi Mike! Thank you very much! You gave a push in the right direction! Mike Christie schrieb: > On the initiator side running 2.6.24 and 2.0.865.15, I > I simply booted both machines with 2.6.24 and now the connection handshake runs. iscsi_discovery 10.6.0.2 -tiser iscsiadm: No active session

Re: Recommended version of Kernel, Initiator, Target

> > So I ended up at a iSCSI Connection over TCP/IP over IPoIB. And not over > iSER. Did you build the stgt target with iser in? To make stgt you have to do: make ISCSI=1 ISCSI_RDMA=1 --~--~-~--~~~---~--~~ You received this message because you are subscribed to

Re: Recommended version of Kernel, Initiator, Target

Dr. Volker Jaenisch wrote: > Hi Mike! > > Thank you very much! You gave a push in the right direction! > > Mike Christie schrieb: >> On the initiator side running 2.6.24 and 2.0.865.15, I >> > I simply booted both machines with 2.6.24 and now the connection > handshake runs. > > iscsi_discov

Re: Recommended version of Kernel, Initiator, Target

Hi Mike! Mike Christie schrieb: > Then use only the > tools in the open-iscsi tarball release (do not use the open-iscsi > tarball modules (I guess you have figured that out already to make this > work)). > I have used so far the open-iscsi-tools from the debian Lenny package 2.0.869-2. Wh