Novell LINUX ENTERPRISE SERVER 11 - STORAGE ADMINISTRATION GUIDE 2-23-2010, Administration Manual, Page: 122 / 140

122 SLES 11: Storage Administration Guide
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
The next menu configures the access restrictions of the target. The configuration is very similar to
the configuration of the discovery authentication. In this case, at least an incoming authentication
should be setup.
Next finishes the configuration of the new target, and brings you back to the overview page of the
Target tab. Activate your changes by clicking Finish .
13.2.3 Configuring an iSCSI Target Manually
Configure an iSCSI target in
/etc/ietd.conf
. All parameters in this file before the first Target
declaration are global for the file. Authentication information in this portion has a special
meaning—it is not global, but is used for the discovery of the iSCSI target.
If you have access to an iSNS server, you should first configure the file to tell the target about this
server. The address of the iSNS server must always be given as an IP address. You cannot specify
the DNS name for the server. The configuration for this functionality looks like the following:
iSNSServer 192.168.1.111
iSNSAccessControl no
This configuration makes the iSCSI target register itself with the
iSNS
server, which in turn provides
the discovery for initiators. For more about iSNS, see Chapter 12, “iSNS for Linux,” on page 109 .
The access control for the iSNS discovery is not supported. Just keep
iSNSAccessControl no
.
All direct iSCSI authentication can be done in two directions. The iSCSI target can require the iSCSI
initiator to authenticate with the
IncomingUser
, which can be added multiple times. The iSCSI
initiator can also require the iSCSI target to authenticate. Use
OutgoingUser
for this. Both have the
same syntax:
IncomingUser <username> <password>
OutgoingUser <username> <password>
The authentication is followed by one or more target definitions. For each target, add a
Target
section. This section always starts with a
Target
identifier followed, by definitions of logical unit
numbers:
Target iqn.yyyy-mm.<reversed domain name>[:identifier]
Lun 0 Path=/dev/mapper/system-v3
Lun 1 Path=/dev/hda4
Lun 2 Path=/var/lib/xen/images/xen-1,Type=fileio
In the
Target
line,
yyyy-mm
is the date when this target is activated, and
identifier
is freely
selectable. Find more about naming conventions in RFC 3722 (http://www.ietf.org/rfc/rfc3722.txt) .
Three different block devices are exported in this example. The first block device is a logical volume
(see also
Chapter 4, “LVM Configuration,” on page 27 ), the second is an IDE partition, and the third
is an image available in the local file system. All these look like block devices to an iSCSI initiator.
Before activating the iSCSI target, add at least one
IncomingUser
after the
Lun
definitions. It does
the authentication for the use of this target.
To activate all your changes, restart the iscsitarget daemon with
rcopen-iscsi restart
. Check
your configuration in the
/proc
file system: