Login or Register to Ask a Question and Join Our Community


Filesystems, Disks and Memory

iSCSI client setup difficulties

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory iSCSI client setup difficulties
# 1  
Old 05-28-2009
iSCSI client setup difficulties
I am trying to set up iscsi linux clients and am having some problems. iscsid is running, I can do discovery fine, but adding the iscsi lun I get the following error:
Code:
iscsiadm -m node -T iqn.xxxxxxxxxxxxxx -p y.y.y.y:3260 -l Logging in to [iface: default, target: iqn.xxxxxxxxxxxxxx, portal: y.y.y.y,3260] iscsid: session [iqn.xxxxxxxxxxxxxx,y.y.y.y,3260] already running. iscsiadm: Could not login to [iface: default, target: iqn.xxxxxxxxxxxxxx, portal: y.y.y.y,3260]: iscsiadm: initiator reported error (15 - already exists)

So far I have this fully working on centos but this does not work at all on debian with the same command lines copied and pasted to be sure, I get the already exists error every time centos iscsi-initiator-utils-6.2.0.868-0.18.el5 debian open-iscsi 2.0.870~rc3-0.4 Any ideas on this?
Last edited by humbletech99; 05-28-2009 at 08:19 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. HP-UX

ISCSI initiator (client) for HP-UX 10.20

Is there one? If so where can it be found? I have the 10.20 CD set but I don't think that there's an iSCSI initiator on there. Thank you Dave (0 Replies)
Discussion started by: perdrix
0 Replies

2. UNIX for Dummies Questions & Answers

Facing difficulties to untar a tra.gz file

Hi , I trying to cp a files to one location and trying to untar there,the tar.gz files get copied to the specified location but wont untar. Here is what i did if cp /path/of/the/file.tar.gz /path/to/the/file/file.tar.gz then tar -zxvf /path/to/the/file/file.tar.gz echo "FILE... (2 Replies)
Discussion started by: vikatakavi
2 Replies

3. Red Hat

Difficulties with pam_tally2! :-(

Dear All I have having some trouble with pam_tally2 on RHEL 6.0 which I am getting quite frustrated with and I am sure it is a simple problem. I have the following lines in system-auth and password-auth: - auth required pam_tally2.so onerr=fail file=/var/log/faillog... (1 Reply)
Discussion started by: gz3xzf
1 Replies

4. UNIX for Dummies Questions & Answers

How to change ethernet cable of iscsi initiator (iscsi client)?

how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies

5. AIX

Setup Window server to accept AIX SFTP client

To all the expert out there, I have successfully setup a AIX to AIX auto-SFTP with no password requested. Now my aim is to setup a AIX to Window auto-SFTP with no password requested as well. But I faced some problem that I do not know how to solve it. I have followed the setting of AIX's... (8 Replies)
Discussion started by: kwliew999
8 Replies

6. UNIX for Dummies Questions & Answers

Sorting Difficulties

Hey guys, I am sort of new to unix and I am having difficulty sorting. What I am trying to do is sort a particular field in reversed order and another field in alphabetic order to create a new file that looks like this: MILLER,EDWARD AL 14 101293 9341 MOORE,HENRY 15 ... (6 Replies)
Discussion started by: nthamma
6 Replies

7. AIX

How to setup Thinclient server and client in AIX

Hi, I want to setup Thinclient server-clinet in AIX. How I can do that? In linux I do it with LTSP. Can LTSP works with AIX? Thanks Neelesh (2 Replies)
Discussion started by: neel.gurjar
2 Replies

8. Shell Programming and Scripting

trying to cope with awk difficulties

The data we are searching is populated in this way: ----IP---------DAY----MONTH----DATE--------TIME---------YEAR 12.3234.34-----Fri------Nov-------15-------18:05:14 GMT---2008 I want the user to be able to search for the data according to month and year. However, I cannot quite figure out... (8 Replies)
Discussion started by: amatuer_lee_3
8 Replies

9. IP Networking

Proxy ARP Difficulties

edited ... (7 Replies)
Discussion started by: TheMaskedMan
7 Replies

10. Programming

Simple Network Program Difficulties

I'm trying to write 2 programs, client & server, that communicate with integers, however, all resources I have found on the net assume that you want to send and recieve information as a character array. I don't want to send my integers as characters, I want to send them as ints (casting them to... (2 Replies)
Discussion started by: Mistwolf
2 Replies
Login or Register to Ask a Question

LEARN ABOUT REDHAT

iscsid

ISCSID(8)						      System Manager's Manual							 ISCSID(8)

NAME

       iscsid - establish iSCSI connections

SYNOPSIS

       iscsid [ -b bindingfile ] [ -d ] [ -f configfile ] [ -l basedir ] [ -m mode ] [ -n ]

DESCRIPTION

       iscsid establishes connections with iSCSI targets defined in /etc/iscsi.conf.

       Once the Linux iSCSI driver is activated, a discovery process for iSCSI storage devices will proceed as follows:

       -      The  iSCSI  daemon requests available iSCSI targets from the iSCSI target, and passes the information discovered to the iSCSI kernel
	      module.

       -      The iSCSI kernel module establishes connections to the targets.

       -      Linux queries targets for device information.

       -      Linux creates a mapping from SCSI device nodes to iSCSI targets.

       iscsid should be started after networking is configured and stopped after all iSCSI devices have been unmounted.

       Warning: Data corruption can occur if you do not unmount iSCSI devices before disabling network interfaces!

DEVICE NAMES

       Because Linux assigns SCSI device nodes dynamically whenever a SCSI logical unit is detected, the mapping from device nodes (e.g  /dev/sda,
       /dev/sdb) to iSCSI targets and logical units may vary.

       Variations  in  process scheduling and network delay may result in iSCSI targets being mapped to different SCSI device nodes every time the
       driver is started.  Because of this variability, configuring applications or operating system utilities to use  the  standard  SCSI  device
       nodes to access iSCSI devices may result in SCSI commands being sent to the wrong target or logical unit.

       To  provide  a more reliable namespace, the iSCSI driver will scan the system to determine the mapping from SCSI device nodes to iSCSI tar-
       gets, and then create a tree of directories and symbolic links under /dev/iscsi to make it easier to use a particular iSCSI target's  logi-
       cal units.

TARGET BINDINGS

       The  iSCSI  driver  automatically maintains a bindings file /var/iscsi/bindings.  This file contains persistent bindings to ensure that the
       same iSCSI bus and target id number are used for every iSCSI session to a particular iSCSI TargetName, no matter how many times the  driver
       is restarted.

       This feature ensures that the SCSI numbers in the device symlinks described above will always map to the same iSCSI target.

       Note  that  because  of	the  way  Linux dynamically allocates SCSI device nodes as SCSI devices are found, the driver does not and can not
       ensure that any particular SCSI device node (e.g. /dev/sda) will always map to the same iSCSI TargetName.  The symlinks	described  in  the
       section	on  Device  Names  are intended to provide a persistent device mapping for use by applications and fstab files, and should be used
       instead of direct references to particular SCSI device nodes.

       If the bindings file grows too large, lines for targets that no longer exist may be manually removed by editing the file.   Manual  editing
       should not normally be needed, since the driver can maintain up to 65535 different bindings.

OPTIONS

       -b bindingfile
	      Specify an alternative bindings file instead of /var/iscsi/bindings, which is the default.

       -d     Turns on debug mode.  Each occurence of -d will increment the debug level by one.  The default is zero (off).

       -f configfile
	      Specify an alternative configuration file instead of /etc/iscsi.conf, which is the default.

       -l basedir
	      Specify  the base directory under which to build a tree of directories containing symlinks to SCSI device nodes, in a manner similar
	      to the devfs Linux kernel option.  Using these symlinks hides variations in the mapping from SCSI device nodes  to  SCSI	device	id
	      numbers.

       -m mode
	      Specify the directory permission mode (in octal) to use when creating directories.

       -n     Avoid auto-backgrounding.

       -v     Print version and exit.

SIGNALS

       iscsid reacts to a set of signals.  You may easily send a signal to iscsid using the following:

	      kill -SIGNAL `cat /var/run/iscsid.pid`

       SIGTERM
	      The daemon and all of it's children will die.

       SIGHUP sent  to the main daemon process will restart all discovery processes and reprobe LUNs on all targets.  iscsid and all of it's chil-
	      dren will die after shutting down all of the kernel's iSCSI sessions.

       SIGCHLD
	      Wait for children.

NOTES

       The iSCSI Driver for Linux provides IP access to a maximum of sixteen remote SCSI targets.  Each target will be probed for up to 256  LUNs,
       until the Linux kernel's limit of SCSI devices has been reached.

       The iSCSI drivers, README files, and example configuration files are available on the Linux-iSCSI homepage at:

       http://linux-iscsi.sourceforge.com/ <http://linux-iscsi.sourceforge.com/>

FILES

       /etc/iscsi.conf
	      target address and LUN configuration

       /var/run/iscsi.pid
	      the process id of the running daemon

       /var/iscsi/bindings
	      persistent bus and target id bindings for iSCSI TargetNames

       /proc/scsi/iscsi
	      information about iSCSI devices

       /dev/iscsi
	      a directory tree containing symlinks to iSCSI device nodes.

SEE ALSO

       iscsi.conf(5)

$Revision: 1.8 $					   $Date: 2002/09/20 19:27:32 $ 						 ISCSID(8)