How To Configure iSCSI Initiator on SLES

This document (7001308) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 10 Service Pack 2
SUSE Linux Enterprise Server 9 Service Pack 4

Situation

This document is a brief 'how to' on configuring the iSCSI initiator on  SUSE Linux Enterprise Server 9 Service Pack 4 and 10 Service Pack 2.

Resolution

On SLES10SP2, the open-iscsi package must first be installed.  Once installed, time must be in sync.  It is suggested that NTP be configured on the iscsi initiators as well as the iscsi target host.

Configuring the initiator through YaST is a breeze.

First, configure the initiator service to start automatically upon boot by checking the radio box, When Booting.


Next, unless you need to give the initiator a specific name because of infrastructure or corporate policy, click on the Discovered Targets tab.  Click on the [Discovery] button, and enter the iSCSI target host's IP address.  After clicking [Next], you should see the iSCSI target under the target(s) name(s).  Select the desired target, and click on the [Log In] button.  For our example, no authentication will be configured, so simply click on [Next].  Now, on the Discovered Targets tab, you should see that this particular target is connected by the [True] in the Connected column.


Finally, click on the Connected Targets tab, and change the start-up mode from Manual to Automatic by clicking on the [Toggle Start-Up] button.


After clicking [Finish], a new device should be detected and ready for use by other services.  A good, quick check to verify it's availability is to run 'cat /proc/partitions'.
 

On SLES9SP4, the linux-iscsi package must first be installed.  Again, once installed, time must be in sync.  It is suggested that NTP be configured on the iscsi initiators as well as the iscsi target host.

Modify /etc/iscsi.conf.  On SLES9, this file is used solely for the initiator configuration.  There are many great examples in this file, such as: authentication configuration, CRC digest checking, subnet-specific settings, etc.,.  For our example, neither authentication nor CRC digest checking will be configured, so the only addition that need be made is:

DiscoveryAddress=10.0.0.129

The service can then be started manually by entering '/etc/init.d/iscsi start' and should be configured to start automatically upon boot by entering 'chkconfig iscsi on'.  Once properly configured and started, a new device should be detected and ready for use by other services.  Again a good, quick check to verify it's availability is to run 'fdisk -l'.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7001308
  • Creation Date: 08-Sep-2008
  • Modified Date:24-Mar-2021
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center