Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

iscsi(4) [freebsd man page]

ISCSI(4)						   BSD Kernel Interfaces Manual 						  ISCSI(4)

iscsi -- iSCSI initiator SYNOPSIS
To compile this driver into the kernel, place the following line in the kernel configuration file: device iscsi Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): iscsi_load="YES" DESCRIPTION
The iscsi subsystem provides the kernel component of an iSCSI initiator. The initiator is the iSCSI client, which connects to an iSCSI tar- get, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are configured using iscsictl(8). The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol. SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables: kern.iscsi.ping_timeout The number of seconds to wait for the target to respond to a NOP-Out PDU. In the event that there is no response within that time the session gets forcibly restarted. kern.iscsi.iscsid_timeout The number of seconds to wait for ctld(8) to establish a session. After that time iscsi will abort and retry. kern.iscsi.login_timeout The number of seconds to wait for a login attempt to succeed. After that time iscsi will abort and retry. kern.iscsi.maxtags The maximum number of outstanding IO requests. kern.iscsi.fail_on_disconnection Controls the behavior after an iSCSI connection has been dropped due to network problems. When set to 1, a dropped connection causes the iSCSI device nodes to be destroyed. After reconnecting, they will be created again. By default, the device nodes are left intact. While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished. SEE ALSO
iscsi.conf(5), iscsictl(8), iscsid(8) HISTORY
The iscsi subsystem first appeared in FreeBSD 10.0. AUTHORS
The iscsi subsystem was developed by Edward Tomasz Napierala <> under sponsorship from the FreeBSD Foundation. BSD
September 11, 2014 BSD

Check Out this Related Man Page

ISCONTROL(8)						    BSD System Manager's Manual 					      ISCONTROL(8)

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
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
Man Page