diff --git a/articles/iscsi.asm.xml b/articles/iscsi.asm.xml index ff73a506c..986dee9a8 100644 --- a/articles/iscsi.asm.xml +++ b/articles/iscsi.asm.xml @@ -76,11 +76,11 @@ - Introduction to iSCSI - Understanding iSCSI allows you to treat remote network storage as a locally attached hard drive, giving you the power to run high-performance applications like databases and virtual machines + Understanding iSCSI Target and Initiator on Linux + Configure iSCSI target and initiator storage on Linux - Use iSCSI to manage your storage + Learn how iSCSI transmits SCSI commands over IP networks to provide systems with block-level access to remote storage configured as local drives diff --git a/concepts/intro-iscsi.xml b/concepts/intro-iscsi.xml index 9f23de80d..86c0bcca1 100644 --- a/concepts/intro-iscsi.xml +++ b/concepts/intro-iscsi.xml @@ -16,7 +16,7 @@ xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:trans="http://docbook.org/ns/transclusion"> - About iSCSI + What is iSCSI? @@ -29,6 +29,8 @@ Note that LU (Logical Unit) is the data container or virtual disk and LUN (Logical Unit Number) is the numerical address of the container. Linux iSCSI provides iSCSI initiator and iSCSI LIO (Linux-IO) target software for connecting Linux servers to central storage systems. +
+ What is iSCSI and how does it work? In a physical iSCSI environment, the initiator is the server’s software that requests data, the LIO target is the physical storage appliance that hosts the data and the LUN (Logical Unit Number) represents the specific physical disk capacity assigned to the server. The iSCSI Initiator:The initiator is the physical server that needs to consume the storage. It initiates the conversation with the target. @@ -47,6 +49,7 @@ +
Key characteristics of remote iSCSI storage Following are some the common characteristics of iSCSI: @@ -58,7 +61,7 @@
- Use cases for remote iSCSI storage + What are the main use cases for iSCSI storage? The common use cases for iSCSI include: Virtualization: Servers running VMware or Hyper-V store virtual machines on remote iSCSI targets so that if one physical server dies, another can immediately take over the disk over the network. diff --git a/tasks/install-configure-iscsi-initiator.xml b/tasks/install-configure-iscsi-initiator.xml index 8ab00deb7..f76e03ee2 100644 --- a/tasks/install-configure-iscsi-initiator.xml +++ b/tasks/install-configure-iscsi-initiator.xml @@ -29,14 +29,24 @@ An iSCSI Initiator is the client component in a SAN that initiates communication Install the iSCSI Initiator if needed: &prompt.sudo; zypper install install open-iscsi - This step is optional as the Initiator name is set by default. Configure the Initiator name. The name must match the ACL created on the Target. - Open the configuration file: -vi /etc/iscsi/initiatorname.iscsi -Edit the line to match: -InitiatorName=iqn.2026-04.com.example:sles.initiator -Restart the service: -&prompt.sudo; systemctl restart iscsid - + + The following steps are optional as the Initiator name is set by default. + + + Configure the Initiator name. The name must match the ACL created on the Target. + Open the configuration file: + vi /etc/iscsi/initiatorname.iscsi + + + Edit the line to match: + InitiatorName=iqn.2026-04.com.example:sles.initiator + + + Restart the service: + &prompt.sudo; systemctl restart iscsid + + + diff --git a/tasks/troubleshooting-iscsi.xml b/tasks/troubleshooting-iscsi.xml index fe4d7d0b6..3ae313b30 100644 --- a/tasks/troubleshooting-iscsi.xml +++ b/tasks/troubleshooting-iscsi.xml @@ -72,10 +72,8 @@ iscsi_target_mod 491520 7 Using iSCSI volumes with LVM Use the troubleshooting tips in this section when using LVM on iSCSI - targets. - Check if iSCSI targets connect automatically at boot - When configuring the iSCSI initiator, ensure that the iSCSI service and target nodes are set to start automatically at boot. This ensures that iSCSI sessions are established during startup, allowing udev to initialize the block devices so that LVM can detect and activate the volume groups. - Check that the iSCSI service automatically establishes target sessions during boot + targets. When configuring the iSCSI initiator, ensure that the iSCSI service and target nodes are set to start automatically at boot. This ensures that iSCSI sessions are established during startup, allowing udev to initialize the block devices so that LVM can detect and activate the volume groups. + Check that the iSCSI service automatically establishes target sessions during boot Remember that udev provides the default setup for devices. Ensure that all of the applications that create devices are started at boot time so that udev can recognize and diff --git a/tasks/workflow-iscsi.xml b/tasks/workflow-iscsi.xml index 64c52dd90..9698a8078 100644 --- a/tasks/workflow-iscsi.xml +++ b/tasks/workflow-iscsi.xml @@ -31,13 +31,15 @@ Additionally, as an example the iSCSI LIO target server has an IP address You must see 0.0.0.0:3260 or your specific target IP. -Enter the targetcli shell and verify the initiator's IQN is listed under the ACLs for your specific TPG (Target Portal Group): - +Enter the targetcli shell. &prompt.sudo; targetcli targetcli shell version 3.0.1 Copyright 2011-2013 by Datera, Inc and others. - For help on commands, type 'help'. - + For help on commands, type 'help'. + + +Verify the initiator's IQN is listed under the ACLs for your specific TPG (Target Portal Group): + /> ls /iscsi o- iscsi ........................................................[Targets: 1] o- iqn.2026-04.com.example:sles.target ...........................[TPGs: 1]