diff --git a/DC-SLES-ISCSI b/DC-SLES-ISCSI
new file mode 100644
index 000000000..d78b776d8
--- /dev/null
+++ b/DC-SLES-ISCSI
@@ -0,0 +1,19 @@
+# This file originates from the project https://github.com/openSUSE/doc-kit
+# This file can be edited downstream.
+
+## Basics
+MAIN="iscsi.asm.xml"
+SRC_DIR="articles"
+IMG_SRC_DIR="images"
+
+## Profiling
+PROFOS="sles"
+PROFCONDITION="16.0"
+#STRUCTID="sles-iscsi"
+#PROFARCH="x86_64;zseries;power;aarch64"
+
+DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat"
+
+## stylesheet location
+STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns"
+FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2021-ns"
\ No newline at end of file
diff --git a/articles/iscsi.asm.xml b/articles/iscsi.asm.xml
new file mode 100644
index 000000000..6ea0f29d8
--- /dev/null
+++ b/articles/iscsi.asm.xml
@@ -0,0 +1,146 @@
+
+
+
+ %entities;
+]>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Understanding iSCSI
+
+ 2026-02-11
+
+
+ Initial version
+
+
+
+
+
+
+
+
+
+ Smart Docs
+
+
+
+ Administration
+ Configuration
+ Security
+
+
+
+
+
+ https://bugzilla.suse.com/enter_bug.cgi
+ Documentation
+ SUSE Linux Enterprise Server 16.0
+ amrita.sakthivel@suse.com
+
+ yes
+
+
+
+
+ &x86-64;
+ &power;
+ &zseries;
+ &aarch64;
+
+
+
+
+ &productname;
+
+
+
+ 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
+
+
+ Use iSCSI to manage your storage
+
+
+
+
+ WHAT?
+
+
+ iSCSI is a networking standard that allows a system to treat a remote storage device over an Ethernet network as if it were a physically plugged-in local hard drive.
+
+
+
+
+ WHY?
+
+
+ Learn how to use iSCSI is used to provide a cost-effective way to consolidate storage into a central location while allowing remote servers to access that data with the high performance and formatting flexibility of a locally attached hard drive.
+
+
+
+
+ EFFORT
+
+
+The average reading time of this article is approximately 40 minutes.
+
+
+
+
+ REQUIREMENTS
+
+
+
+
+Linux fundamentals: Understanding basic Linux commands, file permissions, directory structures
+and use of the command line.
+
+
+
+
+Networking fundamentals: Understanding how IP addresses and subnets work, as iSCSI relies on your local network to find the storage. It also helps to know that iSCSI uses TCP Port 3260 to communicate.
+
+
+
+
+Storage fundamentals: Understanding the difference between file level storage (like a folder on Google Drive) and block level storage (like a raw, unformatted hard drive), as iSCSI is strictly block-level.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/concepts/install-iscsi.xml b/concepts/install-iscsi.xml
new file mode 100644
index 000000000..82310659a
--- /dev/null
+++ b/concepts/install-iscsi.xml
@@ -0,0 +1,30 @@
+
+
+ %entities;
+]>
+
+
+
+
+
+
+ Installing the iSCSI LIO target server and iSCSI initiator
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/concepts/intro-iscsi.xml b/concepts/intro-iscsi.xml
new file mode 100644
index 000000000..32243e48f
--- /dev/null
+++ b/concepts/intro-iscsi.xml
@@ -0,0 +1,72 @@
+
+
+ %entities;
+]>
+
+
+
+
+
+
+ About iSCSI
+
+
+
+ iSCSI (Internet Small Computer Systems Interface) is a networking protocol that enables the transmission of SCSI commands over IP networks, allowing a system to access remote storage as if it were a locally attached hard drive.
+
+
+
+
+ By wrapping storage-level data blocks into standard TCP/IP packets, it bridges the gap between local storage performance and network flexibility, using existing Ethernet infrastructure like switches and cables rather than expensive, specialized hardware. In an iSCSI setup, the initiator connects to a target to claim a portion of disk space known as a LUN (Logical Unit Number), which the client can then format and manage with its own native file system.
+ Linux iSCSI provides iSCSI initiator and iSCSI LIO target software for connecting Linux servers to central storage systems.
+
+ In a physical iSCSI environment, the initiator is the server’s hardware 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.
+
+ HBA (Host Bus Adapter): While you can use a standard network card, a physical iSCSI HBA is a dedicated expansion card installed in the server's PCIe slot. It contains its own processor to handle storage traffic and prevents the server’s main CPU from becoming overwhelmed.
+ Physical Ports: These are the dedicated connection points on the server used exclusively for storage traffic to ensure low latency and high throughput.
+
+
+ The iSCSI LIO Target:The target is the physical hardware device that houses the data. LIO (Linux-IO) is the standard, open-source storage enterprise-grade target for the Linux kernel.
+
+ Chassis and Controllers: The physical box contains one or more controllers (specialized systems) that manage the data flow.
+ Drive Backplane: This is the physical internal wiring that connects the storage controllers to the actual rows of hard drives or SSDs.
+ Network Ports: The physical Ethernet ports (RJ45 for copper or SFP+ for fiber) that plug into the storage network switch.
+
+
+ The LUN: While a LUN is a logical identifier, it directly corresponds to the physical disk resources allocated to a server.
+
+ Physical Disk Groups: A LUN is often a physical collection of disks bound together in a RAID configuration.
+ The Drive to the OS: From the server's perspective, the LUN is treated as a physical local hard drive. You can format, partition and install files on it just like a drive plugged directly into the motherboard.
+ Physical Capacity: The size of the LUN is limited by the number of physical disks installed in the target array.
+
+
+
+
+ Key characteristics of remote iSCSI storage
+ Following are some the common characteristics of iSCSI:
+
+ Block-Level Access: Unlike a network share where you see files, with iSCSI, your system sees raw sectors. This allows you to format the remote drive with any file system such as NTFS, ReFS, or ext4.
+ Distance and Flexibility: The storage can be in a server rack across the room or in a data center across the city. As long as there is a network connection, the system treats it as local storage.
+ Low Latency Requirement: Because the OS thinks the drive is local, it expects fast responses. This is why remote iSCSI usually requires a high-speed network ( preferably 10Gbps or higher).
+
+
+
+ Use cases for remote 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.
+ Database Hosting: High-performance databases like SQL Server or Oracle require block-level access to manage data placement and logging. Since iSCSI presents itself as a local physical disk rather than a shared folder, it satisfies the strict technical requirements of database software while keeping the data on a secure and centralized server.
+ Consolidated Backup and Disaster Recovery: iSCSI allows organizations to centralize backups from various machines onto one large and manageable storage array. It also supports diskless booting, where a server with no internal hard drive can load its entire operating system directly from a remote iSCSI target, making hardware replacement much faster.
+
+
+
\ No newline at end of file
diff --git a/glues/info-iscsi.xml b/glues/info-iscsi.xml
new file mode 100644
index 000000000..3b0a1eead
--- /dev/null
+++ b/glues/info-iscsi.xml
@@ -0,0 +1,24 @@
+
+
+ %entities;
+]>
+
+
+ For more information
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/tasks/configure-iscsi-initiator.xml b/tasks/configure-iscsi-initiator.xml
new file mode 100644
index 000000000..49f27c159
--- /dev/null
+++ b/tasks/configure-iscsi-initiator.xml
@@ -0,0 +1,30 @@
+
+
+ %entities;
+]>
+
+
+
+
+
+
+ Configuring an iSCSI initiator
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/tasks/configure-iscsi-target.xml b/tasks/configure-iscsi-target.xml
new file mode 100644
index 000000000..052018479
--- /dev/null
+++ b/tasks/configure-iscsi-target.xml
@@ -0,0 +1,30 @@
+
+
+ %entities;
+]>
+
+
+
+
+
+
+ Configuring an iSCSI target
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/tasks/troubleshooting-iscsi.xml b/tasks/troubleshooting-iscsi.xml
new file mode 100644
index 000000000..51f9821c3
--- /dev/null
+++ b/tasks/troubleshooting-iscsi.xml
@@ -0,0 +1,30 @@
+
+
+ %entities;
+]>
+
+
+
+
+
+
+ Troubleshooting iSCSI
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file