Dapper 6.06 ISCSI target HOW TO

[iduriduridur]

This is for a clean install, since ISCSI is a task intensive process. It will use ISCSI enterprise target software from

http://iscsitarget.sourceforge.net/

version iscsitarget-0.4.13.tar.gz. download it to your desktop.
unarchive it to a folder on your desktop.

You will need 2 disk drives, say /dev/hda for ubuntu OS

and /dev/sda for iscsi data

first install dapper
then login and update the normal Software updates way.

reboot because of the kernel update.

go to synaptic and install

make
libssl-dev
linux-headers-2.6.15-26-386 - do a uname -r to make sure what you are running.
gcc

install

then get a terminal window up and do sudo su to be root.
type:
ln -s /usr/src/linux-headers-2.6.15-26-386 /usr/src/linux

cd to your desktop iscsi folder you created previously from unarchiving
Example:
cd /home/user/Desktop/iscsi

make KERNELSRC=/usr/src/linux

then I had to type:

make KERNELSRC=/usr/src/linux install

Not exactly sure why i needed to do the make part 2x but it works

cp /home/user/Desktop/iscsi/etc/ietd.conf /etc

It is now installed. But we need to setup the ietd.conf file

vi /etc/ietd.conf

go to the line that says Lun 0 Path=

edit it to point to your iSCSI disk.

Lun 0 Path=/dev/sda

save

/etc/init.d/iscsi-target start

It should say:

Starting iSCSI enterprise target service: succeeded.

Now get the IP address of your box, install MS iscsi initiator free download and test away.

I have an athlon 64 3000+ and 2 gb ram IDE disks, 1 Gig Ethernet with a crossover cable , jumbo frames set on both NICS to an XP box same specs and got 30-40 MBps on IDE and on a unbuntu ram disk i got 70MBps max. It seems on a 1 Gig ethernet the network is the limiting factor.

Now i need to buy 4 PCI express gig nics from Dlink and bond them together to see what i can get.

I have tested this in a VMWARE server session and it works but it is slow since it is a vm and no jumbo Frames as far as i can tell.

[si285]

Hi,
I'm trying to install thie iscsi target but have problems when I follow the instructions here.

The problems start when I issue the command

sudo make KERNELSRC=/usr/src/linux

Here is the output with error

make -C usr
make[1]: Entering directory `/home/adam/Desktop/iscsi/usr'
cc -O2 -fno-inline -Wall -Wstrict-prototypes -g -I../include -c -o ietd.o ietd.c
make[1]: cc: Command not found
make[1]: *** [ietd.o] Error 127
make[1]: Leaving directory `/home/adam/Desktop/iscsi/usr'
make: *** [progs] Error 2


I'm using a fresh install of Ubuntu 6.06.1 and installed
make
libssl-dev
linux-headers-2.6.15-26-386
gcc -- I used gcc4 since it did not specify which version...

I must be missing something simple (or maybe not)...

Any help would be greatly appreciated

Thanks

[iduriduridur]

When you go to synaptic package manager choose to install


gcc

It will install these as dependencies.

binutils
cpp
cpp-4.0
gcc-4.0


Yoiu can't just pick gcc-4.0 it leaves out gcc

hence you get this error.

make[1]: cc: Command not found



This should fix you up.

[christhemonkey]

<offtopic>ISCSI being?
Googling wouldnt tell me anything useful.
</offtopic>


EDIT: Should have searched more carefully, to answer my own question:

iSCSI (Internet SCSI) A protocol that serializes SCSI commands and converts them to TCP/IP

[si285]

Boy do I feel stupid. but hey, I'm learning Ubuntu...

You got me "on-track", I followed the rest of your instructions and it worked perfectly.

Thank you so very much for your help!!!!

[iduriduridur]

Glad you got it working.

What can ISCSI be used for?
I needed an ISCSI target to test a Windows cluster. It is also useful in MS Exchange situations It is used in large storage SAN environments. Anywhere you would need to add storage to a box but don't want to add a physical drive to it. Just install an ISCSI initiator and point it at the iscsi target and you have disks.

[EmmEff]

Here's minor update in the installation procedure that makes things a little simpler.

First off, to install the correct version of linux-headers for the currently booted kernel, do the following:

sudo apt-get install linux-headers-`uname -r`

Next, configure the symlink into the kernel source tree:

sudo ln -s /usr/src/linux-headers-`uname -r` /lib/modules/`uname -r`/build

Using this symlink instead of the suggested symlink means the KERNELSRC parameter to make isn't necessary. From the top of the iscsitarget source tree, simply do the following:

make
make install

Following these steps keeps the installation procedure kernel version agnostic.

[Yyrkoon]

A little off topic, sorry:

Does anyone know what would be involved bonding NICs in Linux, and Windows for such a case ? I know that Linux can do it via software with two NICs, but AFAIK, in Windows, you would either need 802.11-a/d hardware (NICs, and a switch), or some sort of software that I'm un-aware of. nVidia DualNet does not offer true 802.11 link aggregation(outgoing packets only). At least, this is what I've been led to believe after about a weeks worth of "research".

I'm very interrested in iSCSI, have been for close to a year, the only thing that had me set back, was the "network speed issue". Although I dont own such, I'm under the impresion that Intel Pro cards have drivers/software to do 802.11 link aggregation in Windows, but this is what I've read, and have no personal experience.

iSCSI is deffinatly a very interresting technology, and now that it's possible my Favorite Linux Distro (Debian), I'm starting to get that Ole experimentation "tingle" all over again

[iduriduridur]

Intel Pro 1000 cards are the easist to bond in both Windows and linux boxes. I have 2 Intel pro 1000 PCI Express cards. They work well but bonding them together just gave me redundancy not a faster disk read and write for iscsi. I may not have it all figured out but here is a good writeup of nic bonding.


http://linux-ip.net/html/ether-bonding.html

[Yyrkoon]

Originally Posted by iduriduridur Intel Pro 1000 cards are the easist to bond in both Windows and linux boxes. I have 2 Intel pro 1000 PCI Express cards. They work well but bonding them together just gave me redundancy not a faster disk read and write for iscsi. I may not have it all figured out but here is a good writeup of nic bonding. http://linux-ip.net/html/ether-bonding.html

Sounds like you set up for fail over instead, I've read A LOT on ethernet bonding, and I've probably read that same exact page (more than once). The thing is, once I learned that ethernet channel bonding would only work for Linux to Linux (peer to peer), I gave up on it for a while. I've since been told that you could do Linux->Windows if you had a switch that supported 802.3ad link aggregation.

For bonding of two machines, wouldnt you need 4 cards, and a switch for link aggregation ? I said 802.11 a/d in my first post, sorry, was tired (and I'm already a bit forgetful . . .) I actually mean 802.3ad. Anyhow, anyone have an idea of what exactly it would take to get link aggregation working between Linux, and windows ?

[EDIT]

Oh, and iduriduridur, I was actually considering the dual port PT cards in that same family