I've been doing a lot of this recently so I'll add some commentary. To access the iscsi server/san you need to... - configure IP networking for the iscsi devices - enable/start iscsid.service - add software iscsi interfaces - add ethernet interface names to iscsi interfaces - discover iscsi targets - login to iscsi targets If you're using multipathing you need to configure it before any iscsi, and if those multiple targets are on the same IP Subnet, such as Dell Equallogic and FusionIO/NexGenStorage ioControl SAN's, you need to disable FW_KERNEL_SECURITY in the firewall and prevent arp flux and reverse path filtering before multipathing. -- Later, Darin On Fri, Oct 25, 2013 at 5:43 AM, Andreas Jaeger <aj@suse.com> 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.
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 service enabled?
Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org