iscontrol(8) [freebsd man page]
ISCONTROL(8) BSD System Manager's Manual ISCONTROL(8) NAME
iscontrol -- login/negotiator/control for an iSCSI initiator session SYNOPSIS
iscontrol [-dv] [-c file [-n nickname]] [-p pidfile] [-t target] [variable=value] DESCRIPTION
This command, along with its kernel counterpart iscsi_initiator(4), is obsolete. Users are advised to use iscsictl(8) instead. Internet SCSI (iSCSI) is a network protocol standard, that allows the use of the SCSI protocol over TCP/IP networks, the iscontrol program is the userland side of an iSCSI session, see iscsi_initiator(4). It has 2 modes of operation, if -d (discovery session) is specified, it will print out the target names returned by the target and exit. In the second mode, it will, after a successful login/negotiation, run in daemon mode, monitoring the connection, and will try to reconnect in case of a network/target failure. It will terminate/logout the session when a SIGHUP signal is received. The flags are as follows: -c file a file containing configuration key-options, see iscsi.conf(5). -d do a discovery session and exit. -n nickname if -c file is specified, then search for the block named nickname in that file, see iscsi.conf(5). -p pidfile will write the process ID of the session to the specified pidfile -t target the target's IP address or name. -v verbose mode. variable=value see iscsi.conf(5) for the complete list of variables/options and their possible values. EXAMPLES
iscontrol -dt myiscsitarget will start a discovery session with the target and print to stdout the list of available targetnames/targetadresses. Note: this listing does not necessarily mean availability, since depending on the target configuration, a discovery session might not need login/access permission, but a full session certainly does. iscontrol -c /etc/iscsi.conf -n myiscsi will read options from /etc/iscsi.conf, use the targetaddress found in the block nicknamed myiscsi, login and negotiate whatever options are specified, and start an iscsi-session. SEE ALSO
da(4), iscsi_initiator(4), sa(4), iscsi.conf(5), camcontrol(8), iscsictl(8) STANDARDS
RFC 3720 BUGS
iscontrol should probably load the iscsi_initiator module if needed. Not all functions/specifications have been implemented yet, noticeably missing are the Task Management Functions. The error recovery, though not fully compliant does a brave effort to recover from network disconnects. BSD
October 9, 2014 BSD
Check Out this Related Man Page
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)