2010-08-09 12:36:36 +00:00
|
|
|
.\" Copyright (c) 2007-2010 Daniel Braniss <danny@cs.huji.ac.il>
|
2007-07-24 15:35:02 +00:00
|
|
|
.\" All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
.\"
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
|
|
|
.\" $FreeBSD$
|
|
|
|
.\"
|
2014-10-11 05:18:22 +00:00
|
|
|
.Dd October 9, 2014
|
2007-07-24 15:35:02 +00:00
|
|
|
.Dt ISCONTROL 8
|
|
|
|
.Os
|
|
|
|
.Sh NAME
|
|
|
|
.Nm iscontrol
|
|
|
|
.Nd login/negotiator/control for an iSCSI initiator session
|
|
|
|
.Sh SYNOPSIS
|
|
|
|
.Nm
|
2010-08-09 12:36:36 +00:00
|
|
|
.Op Fl dv
|
2007-07-24 15:35:02 +00:00
|
|
|
.Oo
|
2010-08-09 12:36:36 +00:00
|
|
|
.Fl c Ar file
|
2007-07-24 15:35:02 +00:00
|
|
|
.Op Fl n Ar nickname
|
|
|
|
.Oc
|
2010-08-09 12:36:36 +00:00
|
|
|
.Op Fl p Ar pidfile
|
2007-07-24 15:35:02 +00:00
|
|
|
.Op Fl t Ar target
|
|
|
|
.Op Ar variable Ns = Ns Ar value
|
|
|
|
.Sh DESCRIPTION
|
2014-10-11 05:18:22 +00:00
|
|
|
.Bf -symbolic
|
|
|
|
This command, along with its kernel counterpart
|
|
|
|
.Xr iscsi_initiator 4 ,
|
|
|
|
is obsolete.
|
|
|
|
Users are advised to use
|
|
|
|
.Xr iscsictl 8
|
|
|
|
instead.
|
|
|
|
.Ef
|
|
|
|
.Pp
|
2007-07-24 15:35:02 +00:00
|
|
|
Internet SCSI (iSCSI) is a network protocol standard, that allows the
|
|
|
|
use of the SCSI protocol over TCP/IP networks,
|
|
|
|
the
|
|
|
|
.Nm
|
|
|
|
program is the userland side of an iSCSI session, see
|
2007-07-24 18:08:16 +00:00
|
|
|
.Xr iscsi_initiator 4 .
|
2007-07-24 15:35:02 +00:00
|
|
|
It has 2 modes of operation, if -d (discovery session) is specified,
|
|
|
|
it will print out the
|
|
|
|
.Em target names
|
|
|
|
returned by the target and exit.
|
2007-07-24 18:08:16 +00:00
|
|
|
In the second mode, it will, after a successful login/negotiation, run
|
2007-07-24 15:35:02 +00:00
|
|
|
in daemon mode, monitoring the connection, and will try to reconnect
|
2007-07-24 18:08:16 +00:00
|
|
|
in case of a network/target failure.
|
|
|
|
It will terminate/logout the session
|
2007-07-24 15:35:02 +00:00
|
|
|
when a SIGHUP signal is received.
|
|
|
|
The flags are as follows:
|
|
|
|
.Bl -tag -width variable=value
|
|
|
|
.It Fl c Ar file
|
|
|
|
a file containing configuration
|
|
|
|
.Em key-options ,
|
2007-07-24 18:08:16 +00:00
|
|
|
see
|
2010-08-09 12:36:36 +00:00
|
|
|
.Xr iscsi.conf 5 .
|
|
|
|
.It Fl d
|
|
|
|
do a
|
|
|
|
.Em discovery session
|
|
|
|
and exit.
|
2007-07-24 15:35:02 +00:00
|
|
|
.It Fl n Ar nickname
|
|
|
|
if
|
|
|
|
.Sy -c file
|
|
|
|
is specified, then search for the block named
|
|
|
|
.Em nickname
|
2007-07-24 18:08:16 +00:00
|
|
|
in that file, see
|
2010-08-09 12:36:36 +00:00
|
|
|
.Xr iscsi.conf 5 .
|
|
|
|
.It Fl p Ar pidfile
|
|
|
|
will write the process ID of the session to the specified
|
|
|
|
.Em pidfile
|
2007-07-24 15:35:02 +00:00
|
|
|
.It Fl t Ar target
|
2010-08-09 12:36:36 +00:00
|
|
|
the target's IP address or name.
|
|
|
|
.It Fl v
|
|
|
|
verbose mode.
|
2007-07-24 15:35:02 +00:00
|
|
|
.It Ar variable Ns = Ns Ar value
|
2007-07-24 18:08:16 +00:00
|
|
|
see
|
|
|
|
.Xr iscsi.conf 5
|
|
|
|
for the complete list of variables/options and their
|
2007-07-24 15:35:02 +00:00
|
|
|
possible values.
|
|
|
|
.El
|
|
|
|
.Sh EXAMPLES
|
|
|
|
.Dl iscontrol -dt myiscsitarget
|
|
|
|
.Pp
|
2010-08-09 12:36:36 +00:00
|
|
|
will start a
|
2007-07-24 15:35:02 +00:00
|
|
|
.Em 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
|
2010-08-09 12:36:36 +00:00
|
|
|
not need login/access permission, but a
|
2007-07-24 15:35:02 +00:00
|
|
|
.Em full session
|
|
|
|
certainly does.
|
|
|
|
.sp
|
|
|
|
.Dl iscontrol -c /etc/iscsi.conf -n myiscsi
|
|
|
|
.Pp
|
2007-07-24 18:08:16 +00:00
|
|
|
will read options from
|
|
|
|
.Pa /etc/iscsi.conf ,
|
|
|
|
use the targetaddress
|
2007-07-24 15:35:02 +00:00
|
|
|
found in the block nicknamed myiscsi, login and negotiate
|
|
|
|
whatever options are specified, and start an iscsi-session.
|
|
|
|
.Sh SEE ALSO
|
2007-07-24 18:08:16 +00:00
|
|
|
.Xr da 4 ,
|
2007-07-24 15:35:02 +00:00
|
|
|
.Xr iscsi_initiator 4 ,
|
2007-07-24 18:08:16 +00:00
|
|
|
.Xr sa 4 ,
|
2007-07-24 15:35:02 +00:00
|
|
|
.Xr iscsi.conf 5 ,
|
2013-09-14 15:29:06 +00:00
|
|
|
.Xr iscsictl 8 ,
|
2007-07-24 18:08:16 +00:00
|
|
|
.Xr camcontrol 8
|
2007-07-24 15:35:02 +00:00
|
|
|
.Sh STANDARDS
|
|
|
|
RFC 3720
|
|
|
|
.\"Sh HISTORY
|
|
|
|
.Sh BUGS
|
|
|
|
.Nm
|
|
|
|
should probably load the iscsi_initiator module if needed.
|
|
|
|
.br
|
|
|
|
Not all functions/specifications have been implemented yet, noticeably
|
2007-07-24 18:08:16 +00:00
|
|
|
missing are the Task Management Functions.
|
2007-07-24 15:35:02 +00:00
|
|
|
The error recovery, though not
|
|
|
|
.Em fully compliant
|
|
|
|
does a brave effort to recover from network disconnects.
|