os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Finish editorial review of iSCSI chapter.

Browse source 
Sponsored by: iXsystems
This commit is contained in:
Dru Lavigne 2014-03-19 13:50:10 +00:00
parent f5b041976f
commit becf1f15a0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=44285
1 changed files with 33 additions and 41 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

74
en_US.ISO8859-1/books/handbook/network-servers/chapter.xml
View file

@ -5857,83 +5857,75 @@ target iqn.2012-06.com.example:target0 {
<title>Configuring an <acronym>iSCSI</acronym> Initiator</title>
<note>
<para>The current <acronym>iSCSI</acronym> initiator is
<para>The <acronym>iSCSI</acronym> initiator described in this section is
supported starting with &os; 10.0-RELEASE. To use the
<acronym>iSCSI</acronym> initiator available in older
versions, refer to &man.iscontrol.8;.
This chapter only applies to the new initiator.</para>
versions, refer to &man.iscontrol.8;.</para>
</note>
<para>The <acronym>iSCSI</acronym> initiator requires the <link
xlink:href="http://www.freebsd.org/cgi/man.cgi?query=iscsid&amp;sektion=8&amp;manpath=FreeBSD+10-current">iscsid(8)</link>
daemon to run. It does not use a configuration file. To
<para>The <acronym>iSCSI</acronym> initiator requires that the &man.iscsid.8;
daemon is running. This daemon does not use a configuration file. To
start it automatically at boot, add this line to
<filename>/etc/rc.conf</filename>:</para>
<programlisting>iscsid_enable="YES"</programlisting>
<para>On a new machine being configured as an
<acronym>iSCSI</acronym> initiator, <link
xlink:href="http://www.freebsd.org/cgi/man.cgi?query=iscsid&amp;sektion=8&amp;manpath=FreeBSD+10-current">iscsid(8)</link>
can be started by running this command as <systemitem
class="username">root</systemitem>:</para>
<para>To start &man.iscsid.8; now,
run this command:</para>
<screen>&prompt.root; <userinput>service iscsid start</userinput></screen>
<para>Connecting to a target can be done with or without an
<link
xlink:href="http://www.freebsd.org/cgi/man.cgi?query=iscsi.conf&amp;sektion=5&amp;manpath=FreeBSD+10-current">iscsi.conf(8)</link>
configuration file.</para>
<filename>/etc/iscsi.conf</filename>
configuration file. This section demonstrates both types of
connections.</para>
<sect3>
<title>Connecting to a Target Without a Configuration
File</title>
<para>To make the initiator connect to a single target, run
this command as <systemitem
class="username">root</systemitem>:</para>
<para>To connect an initiator to a single target, specify the
<acronym>IP</acronym> address of the portal and the name of
the target:</para>
<screen>&prompt.root; <userinput>iscsictl -A -p 10.10.10.10 -t iqn.2012-06.com.example:target0</userinput></screen>
<screen>&prompt.root; <userinput>iscsictl -A -p <replaceable>10.10.10.10</replaceable> -t <replaceable>iqn.2012-06.com.example:target0</replaceable></userinput></screen>
<para>To verify if the connection succeeded, run it without
arguments. The output should look like this:</para>
<para>To verify if the connection succeeded, run
<command>iscsictl</command> without any
arguments. The output should look similar to this:</para>
<programlisting>Target name Target portal State
iqn.2012-06.com.example:target0 10.10.10.10 Connected: da0</programlisting>
<para>This shows that the <acronym>iSCSI</acronym> session was
<para>In this example, the <acronym>iSCSI</acronym> session was
successfully established, with <filename>/dev/da0</filename>
representing the attached <acronym>LUN</acronym>. If the
<literal>iqn.2012-06.com.example:target0</literal> target
exports more than one <acronym>LUN</acronym>, multiple
device nodes will be shown in the <link
xlink:href="http://www.freebsd.org/cgi/man.cgi?query=iscsictl&amp;sektion=8&amp;manpath=FreeBSD+10-current">iscictl(8)</link>
device nodes will be shown in that section of the
output:</para>
<screen>Connected: da0 da1 da2.</screen>
<para>Any errors are reported in the system logs, and also
visible in the <link
xlink:href="http://www.freebsd.org/cgi/man.cgi?query=iscsictl&amp;sektion=8&amp;manpath=FreeBSD+10-current">iscictl(8)</link>
output. For example, this usually means the <link
xlink:href="http://www.freebsd.org/cgi/man.cgi?query=iscsid&amp;sektion=8&amp;manpath=FreeBSD+10-current">iscsid(8)</link>
<para>Any errors will be reported in the output, as well as the system logs.
For example, this message usually means that the &man.iscsid.8;
daemon is not running:</para>
<programlisting>Target name Target portal State
iqn.2012-06.com.example:target0 10.10.10.10 Waiting for iscsid(8)</programlisting>
<para>The following suggests a network-level problem, such as
<para>The following message suggests a networking problem, such as
a wrong <acronym>IP</acronym> address or port:</para>
<programlisting>Target name Target portal State
iqn.2012-06.com.example:target0 10.10.10.11 Connection refused</programlisting>
<para>This means the specified target name was wrong:</para>
<para>This message means that the specified target name is wrong:</para>
<programlisting>Target name Target portal State
iqn.2012-06.com.example:atrget0 10.10.10.10 Not found</programlisting>
<para>This means the target requires authentication:</para>
<para>This message means that the target requires authentication:</para>
<programlisting>Target name Target portal State
iqn.2012-06.com.example:target0 10.10.10.10 Authentication failed</programlisting>
@ -5941,7 +5933,7 @@ iqn.2012-06.com.example:target0 10.10.10.10 Authentication f
<para>To specify a <acronym>CHAP</acronym> username and
secret, use this syntax:</para>
<screen>&prompt.root; <userinput>iscsictl -A -p 10.10.10.10 -t iqn.2012-06.com.example:target0 -u user -s secretsecret</userinput></screen>
<screen>&prompt.root; <userinput>iscsictl -A -p <replaceable>10.10.10.10</replaceable> -t <replaceable>iqn.2012-06.com.example:target0</replaceable> -u <replaceable>user</replaceable> -s <replaceable>secretsecret</replaceable></userinput></screen>
</sect3>
<sect3>
@ -5960,19 +5952,19 @@ iqn.2012-06.com.example:target0 10.10.10.10 Authentication f
chapSecret = secretsecret
}</programlisting>
<para><literal>t0</literal> specifies a nickname for the
configuration file section, used at the initiator side to
specify which configuration to use. The following lines
specify various parameters used during connection. Target
address and name are mandatory, others are optional. In
this example, <acronym>CHAP</acronym> username and secret
<para>The <literal>t0</literal> specifies a nickname for the
configuration file section. It will be used by the initiator to
specify which configuration to use. The other lines
specify the parameters to use during connection. The <literal>TargetAddress</literal>
and <literal>TargetName</literal> are mandatory, whereas the other options are optional. In
this example, the <acronym>CHAP</acronym> username and secret
are shown.</para>
<para>To connect to the target defined above, use:</para>
<para>To connect to the defined target, specify the nickname:</para>
<screen>&prompt.root; <userinput>iscsictl -An t0</userinput></screen>
<screen>&prompt.root; <userinput>iscsictl -An <replaceable>t0</replaceable></userinput></screen>
<para>To connect to all targets defined in the configuration
<para>Alternately, to connect to all targets defined in the configuration
file, use:</para>
<screen>&prompt.root; <userinput>iscsictl -Aa</userinput></screen>