iSCSI

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by I already forgot (talk | contribs) at 22:28, 20 March 2007 (→‎iSCSI to Fibre Channel, SAS/SATA or SCSI: wiki link). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

You must add a |reason= parameter to this Cleanup template – replace it with {{Cleanup|December 2006|reason=<Fill reason here>}}, or remove the Cleanup template.
 Internet SCSI (iSCSI) is a network protocol standard, officially ratified on 2003-02-11 by the Internet Engineering Task Force, that allows the use of the SCSI protocol over TCP/IP networks. iSCSI is a transport layer protocol in the SCSI-3 specifications framework. Other protocols in the transport layer include SCSI Parallel Interface and Fibre Channel.

Acceptance of iSCSI in corporate production environments has accelerated now that Gigabit Ethernet is becoming more common. Building iSCSI-based Storage Area Networks (SAN) has become a less costly but worthy alternative to creating Fibre Channel-based SANs.

Functionality

The iSCSI (IPA pronunciation: [aɪskʌzi]) protocol uses TCP/IP for its data transfer. Unlike other network storage protocols, such as Fibre Channel (which is the foundation of most SANs), it requires only the simple and ubiquitous Ethernet interface (or any other TCP/IP-capable network) to operate. This enables low-cost centralization of storage without all of the usual expense and incompatibility normally associated with Fibre Channel storage area networks.

Critics of iSCSI expect worse performance than Fibre Channel due to the overhead added by the TCP/IP protocol to the communication between client and storage. However new techniques like TCP Offload Engine (TOE) help in reducing this overhead. Tests have shown excellent performance of iSCSI SANs, whether TOEs or plain Gigabit Ethernet NICs were used. In fact, in modern high-performance servers, a plain NIC with efficient network driver code can outperform a TOE card because fewer interrupts and DMA memory transfers are required. Initial iSCSI solutions are based on a software stack. The iSCSI market is growing steadily, and should improve in performance and usability as more organizations deploy Gigabit and 10 Gigabit networks, and manufacturers integrate iSCSI support into their operating systems, SAN products and storage subsystems. iSCSI becomes even more interesting since Ethernet is starting to support higher speeds than Fibre Channel.

Storage Devices

In the context of computer storage, iSCSI allows a machine to use an iSCSI initiator to connect to remote targets such as disks and tape drives on an IP network for block level I/O. From the point of view of the class drivers and application software, the devices appear as locally attached SCSI devices. More complex environments consisting of multiple hosts and/or devices are called Storage Area Networks (SAN).

iSCSI devices should not be confused with Network-Attached Storage (NAS) devices which include server software to handle the arbitration of simultaneous access requests from different hosts. Allowing multiple hosts to have simultaneous access to a single device is a difficult task common to all SCSI devices. Without host-to-host communication, each host is unaware of the state and intentions of the other hosts. This condition leads to data corruption and race conditions. In the realm of disk storage, cluster software solves this issue.

iSCSI terminology and how iSCSI can be used by an OS

An iSCSI initiator, in client/server terminology, is akin to a client device that connects to some service offered by the server (in this case an iSCSI target). An iSCSI target is akin to a server, in that it provides block level access to its storage media (usually a hard drive, but can be other types of SCSI devices if the iSCSI target software supports them.) The primary difference between a regular client/server system and an iSCSI initiator/target system is that while many clients can simultaneously access the same files served by a single server, iSCSI requires complex coordination between initiators to synchronize accesses to the same files.

iSCSI can be used to give an OS block-level access to a remote device (one attached to another computer likely on the same LAN). Depending on the types of devices supported by the iSCSI target, this block-level access can be used to build RAID volumes using remote disks, or to connect and use remote DVD/CD-writers and scanners, or to simply access additional storage space. iSCSI (like all SCSI protocols) does not mandate how devices are shared amongst multiple computers at the same time; instead the OS in control of the iSCSI device is responsible for controlling remote access to the device. The initiator and the OS that it is running on will determine how the iSCSI device appears, and whether it is a /dev entry or gets a drive letter or something else.

Industry support

Initiators

OS Support Overview

OS First release date Version
AIX 2002-10 AIX 5.2
Windows 2003-06 2003, Vista, Server CodeName "Longhorn"
NetWare 2003-08 NetWare 5.1, 6.5, & OES
HP-UX 2003-10 HP 11i v1, HP 11i v2
Solaris 2005-02 Solaris 10
Linux kernel 2005-06 2.6.12
Mac OS X Spring 2007 10.5 (Leopard)

Initiator Implementations

Software Initiators
  • Cisco iSCSI Driver - one of the earliest software iSCSI initiator implementations. Drivers were available for HP-UX, AIX, Linux, Solaris, and Windows NT4/2000. Its use is now discouraged in favor of other newer initiators. External Link
  • IBM iSCSI Software Initiator for AIX - Available since version 5.2 (2002-10)
  • FreeBSD support is under development.
  • HP HP-UX iSCSI Software Initiator - External Link
  • Linux Initiators
    • Core-iSCSI - Based on GPLed portions of the commercial PyX initiator. This is a project revived for Linux Kernel 2.6 to bridge the gap left when maintenance of Linux-iSCSI stopped in favor of developing Open-iSCSI. External Link
    • Intel-iSCSI (Intel) - The earliest open source release of iSCSI (March 2001). The distribution includes initiator and target code for Linux 2.4 and 2.6 and support for Object-based Storage Devices (OSD). External Link
    • Linux-iSCSI - based on the Cisco Linux iSCSI driver. As of April 2005, the Linux-iSCSI and Open-iSCSI developers have combined their efforts for working on Open-iSCSI. External Link
      • 3.xx series supports Linux Kernel 2.4
      • 4.xx series supports Linux Kernel 2.6 up to 2.6.9
    • Open-iSCSI - Newest initiator implementation for Kernel 2.6.11 and up. Development of Linux-iSCSI has been halted in favor of this project. External Link
    • UNH-iSCSI - Initiator and target implementation from the University of New Hampshire. External Link
  • NetBSD has support in its latest development version.
  • Windows Initiators:
  • Novell iSCSI Initiator for NetWare - Available for Netware 6.5. (ver 5.0 and 6.0 supported via download)
  • Sun Solaris iSCSI Initiator - Available as of the Solaris 10 1/06 update.
  • Ardis Technologies iSCSI initiator for Mac OS X - External Link
  • ATTO Xtend SAN iSCSI Initiator for Mac OS X - External Link
  • Studio Network Solutions globalSAN iSCSI Initiator for Mac OS X (free download) - External Link
iSCSI to Fibre Channel, SAS/SATA or SCSI

Many companies have made a large investment in Fibre Channel and SCSI storage. With the advent of SAS and SATA storage there is now an abundance of both storage technologies.

Conversion of these technologies to iSCSI is possible using a bridging appliance. Bridging appliances take one technology and convert it to another to easily adapt to a SAN, WAN or LAN.

For instance, the iPBridge 2700 from ATTO Technology, Inc allows customers to attach Fibre Channel devices and then connect them to an IP network using iSCSI. There are also conversions available from SCSI to iSCSI as well as SAS/SATA to iSCSI.

This bridging technology allows customers to use their storage in heterogeneous environments while extending existing investments in storage infrastructures.

iSCSI Host Bus Adapters

iSCSI host bus adapters (HBAs) are network interface controllers that incorporate a TCP Offload Engine with onboard iSCSI processing. iSCSI HBAs are usually abstracted purely as SCSI controllers by the operating system driver system. In this case, the HBA is not a part of the system network stack. Recently there has been considerable effort in providing standard vendor-independent iSCSI management facilities via operating system driver interfaces. These standard interfaces also work with software initiators.

Since iSCSI HBAs offload considerable processing in the iSCSI stack, interrupt generation is less than comparable software initiator setups. Applications leaving few spare CPU cycles should benefit from the use of a dedicated HBA.

iSCSI HBAs have the advantage of including PCI option ROMS to allow booting from iSCSI targets. Alternative iSCSI boot methods with software initiators would require substantial work.

The following vendors have developed iSCSI HBAs:

Targets

Most industry focus has been placed on creating iSCSI disk targets 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 SCSI Parallel Interface or Fibre Channel interfaces are bridged by using iSCSI target software, external bridges, or controllers internal to the device enclosure.

Alternatively, disk and tape targets can be virtualizations. 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) solutions. 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.

Software-based iSCSI Targets

  • Linux/Netware/Solaris/NetBSD/FreeBSD
  • Microsoft Windows
    • DataCore Software's SANsymphony [4] storage virtualization software for Windows 2000/XP/2003
    • String Bean Software's WinTarget [5] - acquired by Microsoft and renamed to Microsoft iSCSI Target, now offered as an option pack from OEM's for Windows Storage Server 2003 R2 [6]
    • Rocket Division Software StarWind iSCSI Target for Windows 2000/XP/2003
    • FalconStor - iSCSI Storage Server [7] for Windows 2003 and Windows 2003 Storage Server
    • DataCore SANmelody [8] & SANmelody Lite [9] iSCSI target and disk server software for Windows 2000/XP/2003
    • Nimbus Data Systems - MySAN iSCSI Server [10] Free iSCSI target for Windows 2003 Server
    • Virtual Infrastructure Foundation kit iSCSI target and thin provisioning software for Windows systems
  • Other
    • Open-E iSCSI-R3 - iSCSI storage software is pre-installed on a USB-DOM
    • Open-E DSS - data storage software (NAS + iSCSI ) on pre-installed USB-DOM
    • Software target implementations are also available or included on storage devices from vendors such as EMC, Equallogic, Reldata, LeftHand Networks, Network Appliance, Stonefly and StorageConnections.Net.
    • Wasabi Systems Storage Builder for IP-SAN comes pre-installed on a bootable Compact Flash IDE disk and runs on standard hardware platforms.

Native iSCSI Targets

Addressing and Name formats

iSCSI provides three name formats for different types of naming authorities:

  • iSCSI Qualified Name (IQN), Format: iqn.yyyy-mm.{reversed domain name} (e.g. iqn.2001-04.com.acme:storage.tape.sys1.xyz)
  • Extended Unique Identifier (EUI), Format: eui.{EUI-64 bit address} (e.g. eui.02004567A425678D)
  • T11 Network Address Authority (NAA), Format: naa.{NAA 64 or 128 bit identifier} (e.g. naa.52004567BA64678D)

In the case of IQN the address is qualified by a date (yyyy-mm) since a domain name can expire or be acquired by another entity. EUI is provided by the IEEE Registration authority in accordance with EUI-64 standard. NAA is part OUI which is provided by the IEEE Registration Authority.

NAA name formats were added to iSCSI in RFC 3980, to provide compatibility with naming conventions used in Fibre Channel and SAS storage technologies.

Each target is defined by three or four fields:

HostNameOrAddress PortNumber iSCSIName CHAPSecret (optional)

Example:

iscsi.fake.com 3260 iqn.2003-01.com.ibm:00.fcd0ab21.shark128 "123ismysecretpassword"

Trivia

See also

External links

RFCs

  • RFC 3720 - Internet Small Computer Systems Interface (iSCSI)
  • RFC 3783 - Small Computer Systems Interface (SCSI) Command Ordering Considerations with iSCSI

Other Links

Retrieved from "https://en.wikipedia.org/w/index.php?title=ISCSI&oldid=116639336"