10 More Discussions You Might Find Interesting
1. Solaris
Hello. I'm a noob, but have managed to get to the point of Solaris storage server running 4 X 3Tb in a RAIDZ pool. My current system is sharing via SMB a few different ZFS devices (puddle/TV, puddle/Movies, puddle/Music, etc).
My main server is going to be OSX, Mountain Lion. What I have set... (4 Replies)
Discussion started by: BillyPrefect
4 Replies
2. AIX
Hi,
I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name.
Please share me the steps to complete this requirements.
Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies
3. Red Hat
Hello Friends,
I am facing issue with the iSCSI configuration on some of our RHEL 5 servers,
When I restart the iSCSI service, it triggers the RHEL server reboot.
Could you please help me with this issue.
Below are the system details :
uname -a :
Linux za-rac-prd-01.abc.local... (2 Replies)
Discussion started by: Jeevanm
2 Replies
4. Linux
I am using Windows Server 2008R2 as a domain controller to 2 other servers and would like to use my Dell Powervault 770N as my NAS for data storage. I have FC that I would like to implement between the servers and the NAS (as an iSCSI target). I am brand new to this world; is this possible? I am... (2 Replies)
Discussion started by: NoviceAdmin
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I want to set up a iscsi high availability with sheepdog distributed storage.
Here is my system set up. Four nodes with sheepdog distributed storage and i am sharing this storage through iscsi using two nodes as well as using a virtual ip set up using ucarp.Two nodes using same iqn. And... (0 Replies)
Discussion started by: jobycxa
0 Replies
6. AIX
I have an Equallogic SAN that I connect to from AIX (as well as Windows)
I had configured the connection and created the volumes and filesystems and all was working great.
Then one day, no communication between the SAN and the AIX (I can ping though) Anything I do on the AIX box at this time... (2 Replies)
Discussion started by: oldmanjoe
2 Replies
7. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
8. Linux
Hi guys, I'd like to share experiences and knowledge about what should I use to install on a new storage server (with a lot of disks) in my network. What I want, is to move all domU's storage to this new storage server with AoE, iscsi or another thing. question:
1. Should I install openfiler or... (1 Reply)
Discussion started by: iga3725
1 Replies
9. AIX
Hi,
I have an iSCSI LUN of 200GB. I increased it to 250GB and when I try to increase the size of the vg, I'm getting an error that none of the volumes have increased in size.
How can I get the OS to see the additional 50GB?
---------- Post updated at 03:22 PM ---------- Previous update... (9 Replies)
Discussion started by: bbbngowc
9 Replies
10. AIX
I just reloaded an IBM P-Series with AIX 5.3 and would like to configure iscsi, can someone point me in the right direction to obtaining the initiator node name?
I ran lsattr -El iscsi0 - but the name that is displayed is not the correct name. I read somewhere the default node name is not... (2 Replies)
Discussion started by: bbbngowc
2 Replies
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)
