Setting up iSCSI: Difference between revisions

From Alpine Linux
(→‎iSCSI Target: reformatted comments)
(replace /etc/init.d with rc-service)
 
(29 intermediate revisions by 9 users not shown)
Line 1: Line 1:
== Introduction ==
{{Tip|Consider using [[Linux_iSCSI_Target_(TCM)|TCM]] instead of iscsitarget}}


iSCSI consists of two pieces:  A target and an initiator.  A target is a large pool of disk space that can be accessed over IP by the initiators. Initiators use the disk space, formatting it and mounting it the same as local disk.
iSCSI consists of two components:  A target (server) and an initiator (client).  A target is a large pool of disk space that can be accessed over IP by the initiators. Initiators use the disk space, formatting it and mounting it the same as local disk.  When an initiator connects to a target, a SCSI device node is created (e.g. /dev/sda, /dev/sdb, etc).


= iSCSI Target =


== iSCSI Target ==
The ''iscsitarget-X.X.apk'' package provides the target functionality.  It includes the ietd service (ietd is the iSCSI Enterprise Target Daemon). The ''iscitarget-grsec'' package includes the kernel drivers for the ''grsec'' flavor of linux kernel.
Install with:
{{Cmd|apk add iscsitarget iscsitarget-grsec}}
Once the packages are [[Alpine_package_management#Add_a_Package|installed]], you can set up a target by editing two conf files.


The iscsitarget-X.X.apk package provides the target functionality.  It includes the iscsi_trgt module and the ietd service (ietd is the iSCSI Enterprise Target Daemon).
Once the package is installed, you can set up a target by editing two conf files.


In /etc/ietd.conf, add the following information:
In /etc/ietd.conf, add the following information:


         Target iqn.2006-01.com.openfiler:disk2.bpbx-vm-1
         Target iqn.2006-01.com.example:disk2.vol1
               Lun 0 Path=/dev/sda1, Type=fileio
               Lun 0 Path=/dev/sda1, Type=fileio


''What does the different fields mean? is iqn.2006-01.com.openfiler a hostname? what is disk2.bpbx-vm-1?''--[[User:Ncopa|Ncopa]] 07:59, 8 November 2007 (UTC)
The iSCSI Qualified Name is documented in [https://www.ietf.org/rfc/rfc3720.txt  RFC 3720], with further examples of names in [https://www.ietf.org/rfc/rfc3721.txt RFC 3721]. Briefly, the fields are:
 
* literal '''iqn'''
* date (yyyy-mm) that the naming authority took ownership of the domain
* reversed domain name of the authority (''org.alpinelinux, com.example, to.yp.cr'')
* Optional ":" prefixing a storage target name specified by the naming authority.
 
From the RFC:
                    Naming    String defined by
      Type  Date    Auth      "example.com" naming authority
      +--++-----+ +---------+ +--------------------------------+
      |  ||    | |        | |                                |   
      iqn.2001-04.com.example:storage:diskarrays-sn-a8675309
      iqn.2001-04.com.example
      iqn.2001-04.com.example:storage.tape1.sys1.xyz
      iqn.2001-04.com.example:storage.disk2.sys1.xyz


The "Target" line above is an example.  This line really just needs to be unique.  /dev/sdx refers to the disk and partition that will be presented to the initiator.   
The "Target" line above is an example.  This line really just needs to be unique.  /dev/sdx refers to the disk and partition that will be presented to the initiator.   
Line 20: Line 38:
In the /etc/initiators.allow file, add the following line:
In the /etc/initiators.allow file, add the following line:


    iqn.2006-01.com.openfiler:disk2.bpbx-vm-1 10.1.194.111
iqn.2006-01.com.example:disk2.vol1 10.1.194.111


The IP address in the line above will be the initiator's ip address.  Now only this ip address is allowed to access this specific target.
The IP address in the line above will be the initiator's ip address.  Now only this ip address is allowed to access this specific target.  You must use IP addresses, not hostnames.


''Can hostnames be used instead of ip addresses?''--[[User:Ncopa|Ncopa]] 08:03, 8 November 2007 (UTC)
If you don't care where the initiator is connecting from, you can use the keyword '''ALL'':


== iSCSI Initiator ==
iqn.2006-01.com.example:disk2.vol1 ALL


To configure the iSCSI initiator, add the initiator name to the file /etc/iscsi/initiatorname.iscsi
= iSCSI Initiator =


    InitiatorName=iqn.1993-08.org.debian:01:4efa151441
{{Warning|1=Please note that Open-iSCSI is broken on Alpine 2.2. See http://groups.google.com/group/open-iscsi/browse_thread/thread/156e938d21f01275#. It works on Alpine 2.1, 2.3 and 2.4 instead.}}


''What does 01 mean? where comes the 4efa151441 number from? Did you made it up? What does it mean?''--[[User:Ncopa|Ncopa]] 08:02, 8 November 2007 (UTC)
The initiator is in the ''open-iscsi'' package.  Load this package on the client.


Verify the file /etc/iscsi/iscsid.conf exists.  If not, it may need to be copied from /etc/iscsid.conf.
To configure the iSCSI initiator, add the initiator name to the file /etc/iscsi/initiatorname.iscsi  The initiator name follows the same iqn naming scheme as the target, but this is identifing the initiator (client).


== Connecting the Initiator to the Target ==
InitiatorName=iqn.2007-11.org.alpinelinux.client:01
 
or
InitiatorName=iqn.2007-11.com.example.me:foo:bar:baz
 
 
The ''01'', ''foo:bar:baz'' are arbitrary.  You can enter anything (or nothing)- as long as the intiator name is a valid iqn.
 
Start the initiator daemon with
{{Cmd|rc-service iscsid start}}
 
= Connecting the Initiator to the Target =


From the iSCSI initiator, first run this command:
From the iSCSI initiator, first run this command:


    iscsiadm --mode discovery --type sendtargets --portal IP_OF_TARGET
{{Cmd|iscsiadm --mode discovery --type sendtargets --portal IP_OF_TARGET}}


This command contacts the target to determine which disks are available.  If all is configured correctly, the target name iqn.2006-01.com.openfiler:disk2.bpbx-vm-1 (from the example above) will be returned.
This command contacts the target to determine which disks are available.  If all is configured correctly, the target name iqn.2006-01.com.example:disk2.vol1 (from the example above) will be returned.


After the target is discovered, run this command to connect:
After the target is discovered, run this command to connect:


    iscsiadm --mode node --targetname NAME_OF_TARGET --portal IP_OF_TARGET --login
{{Cmd|iscsiadm --mode node --targetname NAME_OF_TARGET --portal IP_OF_TARGET --login}}


Replacing --login with --logout will end the connection.   
Replacing --login with --logout will end the connection.   
Line 52: Line 81:
To make this connection persistent (so that it will reconnect after reboot), run this command:
To make this connection persistent (so that it will reconnect after reboot), run this command:


    iscsiadm -m node -T NAME_OF_TARGET -p IP_OF_TARGET --op update -n node.conn[0].startup -v automatic
{{Cmd|iscsiadm -m node -T NAME_OF_TARGET -p IP_OF_TARGET --op update -n node.conn[0].startup -v automatic}}
 
''Any references/links to where to find more details about it?''--[[User:Ncopa|Ncopa]] 16:04, 8 November 2007 (UTC)
 
[[Category:Storage]]

Latest revision as of 10:40, 17 November 2023

Tip: Consider using TCM instead of iscsitarget

iSCSI consists of two components: A target (server) and an initiator (client). A target is a large pool of disk space that can be accessed over IP by the initiators. Initiators use the disk space, formatting it and mounting it the same as local disk. When an initiator connects to a target, a SCSI device node is created (e.g. /dev/sda, /dev/sdb, etc).

iSCSI Target

The iscsitarget-X.X.apk package provides the target functionality. It includes the ietd service (ietd is the iSCSI Enterprise Target Daemon). The iscitarget-grsec package includes the kernel drivers for the grsec flavor of linux kernel. Install with:

apk add iscsitarget iscsitarget-grsec

Once the packages are installed, you can set up a target by editing two conf files.


In /etc/ietd.conf, add the following information:

       Target iqn.2006-01.com.example:disk2.vol1
              Lun 0 Path=/dev/sda1, Type=fileio

The iSCSI Qualified Name is documented in RFC 3720, with further examples of names in RFC 3721. Briefly, the fields are:

  • literal iqn
  • date (yyyy-mm) that the naming authority took ownership of the domain
  • reversed domain name of the authority (org.alpinelinux, com.example, to.yp.cr)
  • Optional ":" prefixing a storage target name specified by the naming authority.

From the RFC:

                   Naming     String defined by
      Type  Date    Auth      "example.com" naming authority
     +--++-----+ +---------+ +--------------------------------+
     |  ||     | |         | |                                |     

     iqn.2001-04.com.example:storage:diskarrays-sn-a8675309
     iqn.2001-04.com.example
     iqn.2001-04.com.example:storage.tape1.sys1.xyz
     iqn.2001-04.com.example:storage.disk2.sys1.xyz

The "Target" line above is an example. This line really just needs to be unique. /dev/sdx refers to the disk and partition that will be presented to the initiator.

In the /etc/initiators.allow file, add the following line:

iqn.2006-01.com.example:disk2.vol1 10.1.194.111

The IP address in the line above will be the initiator's ip address. Now only this ip address is allowed to access this specific target. You must use IP addresses, not hostnames.

If you don't care where the initiator is connecting from, you can use the keyword 'ALL:

iqn.2006-01.com.example:disk2.vol1 ALL

iSCSI Initiator

Warning: Please note that Open-iSCSI is broken on Alpine 2.2. See http://groups.google.com/group/open-iscsi/browse_thread/thread/156e938d21f01275#. It works on Alpine 2.1, 2.3 and 2.4 instead.


The initiator is in the open-iscsi package. Load this package on the client.

To configure the iSCSI initiator, add the initiator name to the file /etc/iscsi/initiatorname.iscsi The initiator name follows the same iqn naming scheme as the target, but this is identifing the initiator (client).

InitiatorName=iqn.2007-11.org.alpinelinux.client:01

or

InitiatorName=iqn.2007-11.com.example.me:foo:bar:baz


The 01, foo:bar:baz are arbitrary. You can enter anything (or nothing)- as long as the intiator name is a valid iqn.

Start the initiator daemon with

rc-service iscsid start

Connecting the Initiator to the Target

From the iSCSI initiator, first run this command:

iscsiadm --mode discovery --type sendtargets --portal IP_OF_TARGET

This command contacts the target to determine which disks are available. If all is configured correctly, the target name iqn.2006-01.com.example:disk2.vol1 (from the example above) will be returned.

After the target is discovered, run this command to connect:

iscsiadm --mode node --targetname NAME_OF_TARGET --portal IP_OF_TARGET --login

Replacing --login with --logout will end the connection.

To make this connection persistent (so that it will reconnect after reboot), run this command:

iscsiadm -m node -T NAME_OF_TARGET -p IP_OF_TARGET --op update -n node.conn[0].startup -v automatic

Any references/links to where to find more details about it?--Ncopa 16:04, 8 November 2007 (UTC)