Editing ISCSI (section)

==Implementations==
===Operating systems===
The dates in the following table denote the first appearance of a native driver in each operating system. Third-party drivers for Windows and Linux were available as early as 2001, specifically for attaching IBM's IP Storage 200i appliance.<ref>{{cite web|url=http://www.research.ibm.com/haifa/projects/storage/iSCSI/history.html|title=IBM IP storage 200i general availability|publisher=IBM|access-date=13 September 2013}}</ref>

{| class="wikitable sortable"
|- 
! OS
! First release date 
! Version
! Features
|-
! [[IBM i]]
| 2006-10
| V5R4M0 (as i5/OS)
| Target, Multipath
|-
! [[VMware ESX]]
| 2006-06
| ESX 3.0, ESX 4.0, ESXi 5.x, ESXi 6.x
| Initiator, Multipath
|-
! [[IBM AIX|AIX]]
| 2002-10
| AIX 5.3 TL10, AIX 6.1 TL3
| Initiator, Target
|-
! [[Microsoft Windows|Windows]]
| 2003-06
| 2000, XP Pro, 2003, Vista, 2008, 2008 R2, 7, 8, Server 2012, 8.1, Server 2012 R2, 10, Server 2016, 11, Server 2019
| Initiator, Target,{{Efn|Target available only as part of [[Windows Storage Server|Windows Unified Data Storage Server]]. Target available in Storage Server 2008 (excepted Basic edition).<ref>{{cite web|url=http://www.microsoft.com/windowsserver2008/en/us/WSS08/iSCSI.aspx |title=Windows Storage Server &#124; NAS &#124; File Management |publisher=Microsoft |access-date=2012-09-18}}</ref>
Target available for Windows Server 2008 R2 as a separate download. Windows Server 2012, 2012 R2 and 2016 have built-in Microsoft iSCSI target version 3.3.}} Multipath
|-
! [[Novell NetWare|NetWare]]
| 2003-08
| NetWare 5.1, 6.5, & OES
| Initiator, Target
|-
! [[HP-UX]]
| 2003-10
| HP 11i v1, HP 11i v2, HP 11i v3
| Initiator
|-
! [[Solaris (operating system)|Solaris]]
| 2002-05
| Solaris 10, OpenSolaris
| Initiator, Target, Multipath, [[ISCSI Extensions for RDMA|iSER]]
|-
! [[Linux]]
| 2005-06
| 2.6.12, 3.1
| Initiator (2.6.12), [[LIO Target|Target]] (3.1), Multipath, [[ISCSI Extensions for RDMA|iSER]], VAAI{{Efn|name="vstorage"|vStorage APIs Array Integration}}
|-
! [[OpenBSD]]
| 2009-10
| 4.9
| Initiator
|-
! [[NetBSD]]
| 2002-06
| 4.0, 5.0
| Initiator (5.0), Target (4.0)
|-
! [[FreeBSD]]
| 2008-02
| 7.0
| Initiator (7.0), Target (10.0), Multipath, [[ISCSI Extensions for RDMA|iSER]], VAAI{{Efn|name="vstorage"}}
|-
! [[OpenVMS]]
| 2002-08
| 8.3-1H1
| Initiator, Multipath
|-
! [[macOS]]
| 2008-07
| 10.4—
| N/A{{Efn|macOS has neither initiator nor target coming from vendor directly. {{citation needed|date=November 2013}}}}
|}

===Targets===
Most iSCSI targets involve disk, though iSCSI tape and medium-changer targets are popular as well. So far, physical devices have not featured native iSCSI interfaces on a component level. Instead, devices with [[Parallel SCSI]] or [[Fibre Channel]] interfaces are bridged by using iSCSI target software, external bridges, or controllers internal to the device enclosure.

Alternatively, it is possible to virtualize disk and tape targets. Rather than representing an actual physical device, an emulated virtual device is presented. The underlying implementation can deviate drastically from the presented target as is done with [[virtual tape library]] (VTL) products. VTLs use disk storage for storing data written to virtual tapes. As with actual physical devices, virtual targets are presented by using iSCSI target software, external bridges, or controllers internal to the device enclosure.

In the security products industry, some manufacturers use an iSCSI RAID as a target, with the initiator being either an IP-enabled encoder or camera.

===Converters and bridges===
Multiple systems exist that allow Fibre Channel, SCSI and SAS devices to be attached to an IP network for use via iSCSI. They can be used to allow migration from older storage technologies, access to SANs from remote servers and the linking of SANs over IP networks. An iSCSI gateway bridges IP servers to Fibre Channel SANs. The TCP connection is terminated at the gateway, which is implemented on a Fibre Channel switch or as a standalone appliance.