I'm sorry, I forgot one aspect of the answer to your question Andreas,
so I added it, below, at the bottom.
On 10/29/2013 02:27 AM, Lee Duncan wrote:
On 10/25/2013 02:43 PM, Andreas Jaeger wrote:
Lee, I need some more background:
This is the client side of iscsi, you want to enable, correct?
Client-side means, you have a server/SAN that
provides iscsi storage and
your local machine will access that remote server/SAN.
More likely you have an ethernet network and some hard or soft
clients. I think of a SAN as separate from the other network traffic,
and usually FC (though of course not always).
So, do I need to edit anything to access the remote storage? Or is this
done via command-line tools delivered with the package that need the
After installing open-iscsi, if it is configured correctly,
i.e. either set up for socket-based activation (as I wish to do with
systemd), or with the daemon already running, here are the steps you
might use to get access to a remote device:
root# iscsiadm -m discovery -t st -p 192.168.20.2 -l
Logging in to [iface: default, target: iqn.2001-04.net.gonzoleeman:test.disk.laptop.001,
portal: 192.168.20.2,3260] (multiple)
Login to [iface: default, target: iqn.2001-04.net.gonzoleeman:test.disk.laptop.001,
portal: 192.168.20.2,3260] successful.
In other words, I have asked the iscsiadm program to discover targets
at 192.168.20.2, and try to login to any targets it finds.
If finds one target and succeeds at logging into it. After this step,
a new device appears, /dev/sdb in my case. If I happened to have a
partition from /dev/sdb listed in /etc/fstab as containing a
filesystem and mark it appropriately then systemd will take care of
mounting it for me.
As part of this process it builds a target and node database, so that
next time I don't need to rediscover targets unless I want to.
Note: this example is only using the iscsid.socket and iscsid.serivce
I also created (taken from open-iscsi upstream) an "iscsi.service" unit.
This higher-level unit is based on iscsid.service, and provices iscsi
sessions as a service. So starting this unit logs into any iSCSI nodes
you have marked appropriately in your iscsi node database, and stopping
this service logs out of those targets.
This optional higher-level service, if used, automates creating and
destroying sessions on your favorite iSCSI targets, so that you don't
have to manually log into and out of said targets unless you want to.
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org