Microsoft iSCSI Software Target 3.

3 Getting Started Guide

Microsoft Corporation Published: March 2011

Abstract
This guide provides technical help for end users who want to configure Microsoft iSCSI Software Target on their storage appliance. iSCSI Software Target creates iSCSI targets and virtual disks that you can manage through the Microsoft iSCSI Software Target console.

Copyright information
This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. 2010-2011 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, Hyper-V, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.

Contents
Microsoft iSCSI Software Target 3.3 Getting Started Guide............................................................1 Abstract.................................................................................................................................... 1 Copyright information...................................................................................................................... 2 Contents.......................................................................................................................................... 3 Microsoft iSCSI Software Target 3.3 Getting Started Guide............................................................4 iSCSI overview............................................................................................................................ 4 iSCSI network components...................................................................................................... 4 iSCSI Software Target components.......................................................................................... 5 In this guide................................................................................................................................. 5 Configuring Windows Firewall......................................................................................................... 6 Installing the Microsoft iSCSI Software Target................................................................................6 Installing the Microsoft iSCSI Software Target Providers................................................................7 About Virtual Disks and Snapshots...............................................................................................10 Virtual disks............................................................................................................................... 10 Snapshots.................................................................................................................................. 11 Using hardware providers.......................................................................................................... 12 Command line tools for VDS Hardware Provider...................................................................12 Command line tools for VSS Hardware Provider ...................................................................12 Multipath I/O Support.................................................................................................................... 13 Failover Clustering Support (Enterprise Edition Only)...................................................................13 Supported failover cluster configurations...............................................................................14 Requirements for iSCSI storage failover clustering................................................................14 Creating a failover cluster....................................................................................................... 15 Interoperability with Non-Microsoft iSCSI Initiators.......................................................................15 Version and platform supportability............................................................................................15 Support...................................................................................................................................... 16

Microsoft iSCSI Software Target 3.3 Getting Started Guide

Internet Small Computer Systems Interface (iSCSI) is a protocol that supports access to storage devices over a TCP/IP network, which facilitates storage consolidation and sharing of storage resources across an organization. You can use Microsoft iSCSI Software Target 3.3 to create iSCSI targets and iSCSI virtual disks. You can then use the Microsoft iSCSI Software Target console to manage all iSCSI targets and virtual disks that were created. Additional functionality provided in iSCSI Software Target includes support for taking snapshots of virtual disks. It also includes wizards for setting up and maintaining iSCSI Software Target. This guide provides basic conceptual and installation information about iSCSI Software Target 3.3. It supplements the detailed procedural information that is available from the iSCSI Target Microsoft Management Console (MMC) snap-in. Microsoft iSCSI Software Target is an optional package for Windows Server 2008 R2 and Windows Storage Server 2008 R2. If it is not installed or provided with your storage appliance, contact your storage appliance manufacturer for information about acquiring iSCSI Software Target. iSCSI Software Target 3.3 is supported on the following operating systems: Windows Server 2008 R2 Standard Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Windows Storage Server 2008 R2 Workgroup Windows Storage Server 2008 R2 Standard Windows Storage Server 2008 R2 Enterprise

iSCSI overview
Several protocols, such as Serial Attached SCSI (SAS) and Serial ATA (SATA or Serial Advanced Technology Attachment), are available so that a disk controller can communicate with the disk drives. These protocols are predefined standards that determine how commands, such as read and write requests, are packaged and sent between the controller and disk drive. The iSCSI protocol extends the SCSI standards by encapsulating SCSI commands in TCP/IP packets. These commands are sent over a TCP/IP network, so that servers can access storage on a storage area network (SAN). This facilitates implementing and centrally managing the consolidated storage, including centralized backup and remote system recovery.

iSCSI network components

In an iSCSI network, there are three components: iSCSI target 4

The iSCSI target provides storage, similar to the hard disk drives of locally attached storage, but this storage is accessed over a network instead of locally. This functionality is provided in Windows Server 2008 R2 and Windows Storage Server 2008 R2 by iSCSI Software Target. iSCSI initiator The iSCSI initiator is sometimes referred to as the client. The iSCSI target provides the storage to the iSCSI initiator, which acts as a disk controller for the disks that are hosted by the target. All versions of Windows Server include the iSCSI initiator so that the client computer can connect to an iSCSI target. The iSCSI Initiator is also included in the Windows Vista and Windows 7 operating systems. Storage fabric This is an IP-based network that connects the iSCSI target to the iSCSI initiator. The storage fabric is typically a gigabit local area network (LAN).

iSCSI Software Target components

The iSCSI Software Target package includes the following components: Microsoft iSCSI Software Target Lets you create and manage virtual disks, create and manage iSCSI targets, and provide backup and recovery of iSCSI targets through snapshots. Volume Shadow Copy Service (VSS) hardware provider Installs on the initiator computer and works with the VSS to provide consistent snapshots of iSCSI virtual disks on the computer that runs iSCSI Software Target. Virtual Disk Service (VDS) hardware provider Installs on an initiator computer and lets VDS-aware applications manage virtual disks on a storage appliance that is running iSCSI Software Target. High Performance Computing (HPC) provider On 64-bit Windows Server platforms, enables provisioning of iSCSI startup disks for Microsoft High Performance Computing (HPC) servers. Windows PowerShell cmdlets Assist you with task automation.For more information, see iSCSI Cmdlets (http://go.microsoft.com/fwlink/?LinkId=195399) on Microsoft TechNet. To access in-product Windows PowerShell Help, type PowerShell Command Prompt window.
get-help

from a Windows

In this guide
Configuring Windows Firewall Installing the Microsoft iSCSI Software Target Installing the Microsoft iSCSI Software Target Providers About Virtual Disks and Snapshots Multipath I/O Support Failover Clustering Support (Enterprise Edition Only) Interoperability with Non-Microsoft iSCSI Initiators

To add an inbound filter rule for an application

Configuring Windows Firewall

The following table lists the Windows Firewall exception that should be made on the computer that is running iSCSI initiator so that iSCSI will properly function. Specifically, an inbound filter rule must be added and configured in Windows Firewall for the application listed.
Application exception Description

%windir%\System32\Wtvds.exe

iSCSI Software Target VDS hardware provider

1. In Server Manager, expand Configuration, expand Windows Firewall with Advanced Security, and then click Inbound Rules. 2. In the Actions pane, click New Rule. 3. Under What type of rule would you like to create, click Program, and then click Next. 4. Click Browse, browse to the %windir%\System32 folder, and then click Wintarget.exe. Click Open, and then click Next. 5. Click Allow the connection, and then click Next. 6. Select the network locations that should be bound to this rule (the default is Domain, Private, and Public). Click Next. 7. Under Name, type a descriptive name for the rule. For example, type Microsoft iSCSI Software Target Service for the program rule for Wintarget.exe. Click Finish.

Installing the Microsoft iSCSI Software Target

Microsoft iSCSI Software Target is distributed as the Windows Installer file, iscsitarget.msi. To install the Microsoft iSCSI Software Target files interactively, double-click the .msi file. Alternatively, you can use the following command lines to perform the installation. To install Microsoft iSCSI Software Target: msiexec /i iscsitarget.msi <options> ALLUSERS=1 [PROPERTY=PropertyValue] To uninstall Microsoft iSCSI Software Target: msiexec /x iscsitarget.msi <options> The following options are available:

Option

Description

/quiet /passive /q[n|b|r|f]

Quiet mode, no user interface is displayed during installation. Unattended mode, only a progress bar is displayed. Sets user interface level: n No UI b Basic UI r Reduced UI f Full UI (default)

/L*v <logfile> The following property is available:

Property

Logs all actions to the specified log file.

Description

TARGETDIR

Specifies the root destination directory.

Installing the Microsoft iSCSI Software Target Providers

A provider is software that supports management of iSCSI virtual disks and snapshots from the iSCSI initiator. The following providers are included in the Microsoft iSCSI Software Target 3.3 package, and they are installed on initiator computers that will connect to a storage appliance running the Microsoft iSCSI Software Target: Microsoft iSCSI Software Target Virtual Disk Service Hardware Provider Windows Server 2003 introduced Virtual Disk Service (VDS), which is a set of application programming interfaces (APIs) that provides a single interface for managing disks. VDS provides an end-to-end solution for managing storage hardware and disks, and for creating volumes on those disks. The Microsoft iSCSI Software Target VDS Hardware Provider is required to use non-Microsoft VDS or VSS aware applications to manage virtual disks in a storage system. You install the Microsoft iSCSI Software Target VDS Hardware Provider on each iSCSI initiator computer that is running a storage management application (such as Storage Manager for SANs) that uses the hardware provider to manage storage, as described in this guide. You should also install the Microsoft iSCSI Software Target VDS Hardware Provider on 7

Note any computer from which you will use VDS-aware management applications to manage the storage appliance. Microsoft iSCSI Software Target Volume Shadow Copy Service Hardware Provider A Microsoft iSCSI Software Target VSS Hardware Provider is required to create transportable snapshots of iSCSI virtual disks and create application consistent snapshots from iSCSI initiators. iSCSI snapshots are created by using the Volume Shadow Copy Service in conjunction with a disk storage array. You install this hardware provider on the same iSCSI initiator server that you use to perform backups. The backup software you use must support transporting snapshots. Microsoft iSCSI Software Target High Performance Computing (HPC) Provider A Microsoft iSCSI Software Target HPC Provider enables provisioning of iSCSI startup disks for Microsoft High Performance Computing (HPC) servers. The iSCSI target creates snapshots to backup and restore virtual disks that are file system consistent, and which support restoration at the file system level. For a virtual disk to be restored in a way that is application consistent, so that the server application recovers completely, the snapshots should be made from the iSCSI initiator. This functionality in the iSCSI initiator requires the use of the iSCSI initiator VSS Hardware Provider on the iSCSI initiator server. Except as noted, the Microsoft iSCSI Software Target Providers can be installed on the following operating systems: Windows Server 2003 SP2 x86 Windows Server 2003 SP2 x64 Windows Server 2008 (SP1) x86 Windows Server 2008 (SP1) x64 Windows Server 2008 (SP2) x86 Windows Server 2008 (SP2) x64 Windows Server 2008 x64 Windows Server 2008 R2 x64

The Microsoft iSCSI Target High Performance Computing (HPC) provider is only supported on 64-bit Windows platforms. The Microsoft iSCSI Software Target Providers require that the computer on which they are installed is in a Windows domain, and that the computer is in the same domain as the Microsoft iSCSI Software target that they are connecting to. Install the Microsoft iSCSI Software Target Providers The Microsoft iSCSI Software Target Providers are distributed as Windows Installer files. Open the Index.htm file to access the installation links, or double click the applicable iscsitargetClient.msi file. Alternatively, you can also enter the following commands from a Windows command prompt to perform the installation.

Note iSCSI Target Client Setup will prompt you to enter user account credentials that have local administrative permissions on the iSCSI target computer when installing the VDS or VSS hardware provider. This is not required if installing the HPC provider only. To install the Microsoft iSCSI Software Target Providers From a command prompt, type the following: msiexec /i iscsitargetClient.msi <options> ALLUSERS=1 [PROPERTY=PropertyValue] To uninstall the Microsoft iSCSI Software Target Hardware Providers From a command prompt, type the following: msiexec /x iscsitargetClient.msi <options> The following options are available:
Option Description

/quiet /passive /q[n|b|r|f]

Quiet mode, no user interface is displayed during installation. Unattended mode, only a progress bar is displayed. Sets user interface level: n No UI b Basic UI r Reduced UI f Full UI (default)

/L*v <logfile>

Logs all actions to the specified log file.

The following properties are available:

Property Description

ADDLOCAL

Specifies which features to install. Available features include: ALL: Install all features (default) VSSProvFeature: Install the VSS Hardware Provider VDSProvFeature: Install the VDS Hardware Provider HPCiSCSIProvFeature: Install the HPC Provider

TARGETDIR

Specifies the root destination directory. 9

To upgrade to Microsoft iSCSI Software Target 3.3 Providers

Property Description

SERVICEUSERNAME SERVICEPASSWORD

The VSS and VDS service account user name. The VSS and VDS service account password.

1. Uninstall previous versions of the applicable providers. 2. Right-click the iscsitargetClient.msi file for iSCSI initiator 3.32 and select Run as Administrator. 3. Follow the steps in the wizard.

About Virtual Disks and Snapshots

Microsoft iSCSI Software Target creates storage devices as iSCSI virtual disks. These iSCSI virtual disks offer flexible and effective storage. Virtual disks can be extended to provide extra capacity on demand, enable efficient storage utilization, minimize the time that is required to create disks, and minimize the down time that is typically required to install new disks.

Virtual disks
iSCSI virtual disks are files in the virtual hard disk (VHD) format. iSCSI virtual disks are assigned to specific iSCSI targets, and only the iSCSI virtual disks assigned to an iSCSI target are available to an iSCSI initiator. After the iSCSI initiator logs on to the iSCSI target, these virtual disks appear as locally-attached hard disks. These disks can be locally mounted to support backup and recovery operations. With Microsoft iSCSI Software Target, you can provide effective and efficient backup and recovery for virtual disks on the iSCSI target without stopping applications or closing files. You can then transport data to a central server for LAN-free and server-free backup. This eliminates the backup window that is needed for traditional backup solutions, and it allows application servers to continue running without disruption to clients. The primary functionality that is provided in iSCSI Software Target to support data backup and recovery includes the following: Snapshots A snapshot is a point-in-time, read-only copy of an iSCSI virtual disk that can be used for fast system recovery in the event of data corruption from a virus attack, system security compromise, or an inadvertent user deletion. These are especially useful for interim backups of data that has changed since the previous regular backup because they are differential copies. Local disk access

10

Local access to data on virtual disks can be set up by mounting a read-only snapshot of an iSCSI virtual disk or mounting a virtual disk as a read-write disk on the local computer. This makes it possible to use other backup software to perform regular backups. Rollback The rollback functionality in iSCSI Software Target makes it possible to roll back a virtual disk to a snapshot. Using backup software requires appropriate coordination of actions between the backup software and iSCSI Software Target; for example, setting up appropriate schedules and configurations for creating and mounting snapshots, and including the locally mounted snapshots in routine backups.

Snapshots
Snapshots are useful for backup and recovery operations and for data mining. You can create a snapshot manually or set up automatic snapshots to be taken at specific times. Snapshots offer the following advantages: Can be scheduled to be created automatically. Offer space-efficiency because they are differential copies.

Provide fast system recovery of files and volumes if data is accidentally deleted by a user, overwritten, or corrupted by a malicious program. Can be mounted locally or exported to facilitate backup and recovery operations. Do not require that you close files or stop programs when you create them, so application servers can continue servicing clients without disruption. iSCSI snapshots are created by using the Volume Shadow Copy Service and a storage array with a hardware provider that is designed for use with the Volume Shadow Copy Service. Snapshots that are created on the iSCSI target server are crash consistent. This means that if the iSCSI initiator computer stops responding, the state of the snapshot will be the same as the state of the virtual disk. Most modern file systems can recover from this state. To enable crash consistent snapshots, the Microsoft iSCSI Software Target VSS Hardware Provider, which is available as an option in iSCSI Software Target, must be installed on the iSCSI initiator computer. The hardware provider coordinates with the local Volume Shadow Copy Service to create a consistent image of the volume that can be transported to a central backup server. With Microsoft iSCSI Software Target, you can make a snapshot available on remote computers by using the Export Snapshot Wizard. You can use the wizard to export the snapshot to one or more iSCSI targets. After you export a snapshot, it appears on the iSCSI initiator as a local disk with read-only access, and it can be mounted by using a drive letter. This is useful for making files available to users for a short period of time, such as might be required for search and recovery of a specific file. With Microsoft iSCSI Software Target, you can roll back an iSCSI virtual disk to a previous snapshot. A rollback of the disk requires the use of a temporary directory (such as C:\WINDOWS\Temp). This directory must contain sufficient space to store the differential data. If there is insufficient space, the rollback will stop, and the virtual disk content will not change. 11

Using hardware providers

To manage iSCSI virtual disks and snapshots, you use the appropriate iSCSI Software Target Hardware Providers. These hardware providers, which are provided in the iSCSI Software Target package, include: Microsoft iSCSI Software Target Virtual Disk Service Hardware Provider Virtual Disk Service (VDS) is a set of application programming interfaces (APIs) that provides a single interface for managing disks. VDS provides an end-to-end solution for managing storage hardware and disks, and for creating volumes on those disks. The Microsoft iSCSI Software Target VDS Hardware Provider is required to manage virtual disks on a storage subsystem. You install the Microsoft iSCSI Software Target VDS Hardware Provider on each iSCSI initiator computer that is running a storage management application (such as Storage Manager for SANs) that uses the hardware provider to manage storage, as described later in this guide. Microsoft iSCSI Software Target Volume Shadow Copy Service Hardware Provider iSCSI snapshots are created by using Volume Shadow Copy Service (VSS) and a storage array with a hardware provider that is designed for use with VSS. A Microsoft iSCSI Software Target VSS Hardware Provider is required to create transportable snapshots of iSCSI virtual disks and to create application consistent snapshots from iSCSI initiators. You install this hardware provider on the iSCSI initiator server that you use to perform backups. You can perform many of the administrative tasks for the Microsoft iSCSI Software Target from the command prompt by using standard Windows Server 2008 R2 utilities. Following are some commands that you might find useful.

Command line tools for VDS Hardware Provider

The following commands can be used to work with disks and volumes from the command prompt: MountVol.exe: MountVol is used to create, delete, or display volume mount points. DiskRaid.exe: DiskRaid is used to create, delete, and optimize physical and logical redundant arrays of independent disks (RAIDs).

Command line tools for VSS Hardware Provider

The following tools can be used to work with VSS from the command prompt: VSSAdmin.exe: VSSAdmin is used to manage the Volume Shadow Copy Service, including creating, resizing, and deleting VSS allocations on volumes. DiskShadow.exe: DiskShadow is a tool for working with VSS, similar to VSSAdmin, but it also lets you work with snapshots. For more information on using command line tools, see Command-line reference, A-Z List (http://technet.microsoft.com/en-us/library/cc772390(WS.10).aspx) on Microsoft TechNet.

12

Note

To install MPIO

Multipath I/O Support

Microsoft Multipath I/O (MPIO) enables hardware vendors to create interoperable multipathing solutions that increase reliability, interoperability, and high-speed data access. Multipathing is the ability of a system to use more than one read/write path to a storage device, and it is a highavailability solution that provides fault tolerance against a single point of failure in hardware components. Multipathing can also provide load balancing for I/O traffic. Microsoft iSCSI Software Target 3.3 supports MPIO for block storage on Windows Server 2008 R2 and Windows Storage Server 2008 R2. It also includes a device specific module (DSM), which works with SPC-3 compliant targets. When used with Microsoft iSCSI Software Target, MPIO is not supported for iSCSI initiators when the initiators are members of a failover cluster.

The following procedure explains how to install MPIO as an additional feature through Server Manager. 1. To open Server Manager, click Start, and then click Server Manager. 2. Click Features, and then click Add Features. 3. Under Features, select Multipath I/O, and then click Next. 4. Click Install.

Failover Clustering Support (Enterprise Edition Only)

The Microsoft iSCSI Software Target 3.3 is a cluster-aware application, and it can be used to provide file and block storage services on failover clusters that run the Windows Server 2008 R2 Enterprise and Windows Storage Server 2008 R2 Enterprise operating systems. This failover cluster support provides redundancy for shared block storage or storage area networks (SANs). This enhances the availability of applications that can be scaled across the cluster nodes. You implement failover clustering by configuring highly available instances (also known as resource groups) on storage appliances that are part of a failover cluster. Each highly available instance is a collection of resources that run together on a cluster node and fail over as a single unit. You can create new highly available instances, or if you have previously configured any highly available instances, you can use those resource groups. You can use the same resource group to provide high availability for both file sharing and block sharing. For more information about the use of resource groups, see Failover Cluster Management Help. 13

In an iSCSI-based cluster environment, the iSCSI virtual disk must reside on a shared cluster disk, and an existing iSCSI virtual disk can only be added to an iSCSI target that belongs to the same resource group. Microsoft iSCSI Software Target must be installed on every node in the cluster to provide failover support for iSCSI resources.

Supported failover cluster configurations

Windows Server 2008 R2 and Windows Storage Server 2008 R2 support failover clustering in various configurations. These configurations support increasing levels of redundancy to ensure data availability. Storage appliances running Windows Storage Server 2008 R2 Enterprise can be used in the following failover cluster configurations: Highly available target, single path: A single initiator computer uses an iSCSI initiator to connect to a failover cluster that contains two or more nodes. The storage appliances are connected to external storage, such as Fibre Channel or iSCSI, to provide a quorum disk and cluster storage. Highly available target, multipath: A single iSCSI initiator server uses Microsoft Multipath I/O (MPIO) to connect to a failover cluster that contains two or more nodes. The nodes are connected to external storage, such as Fibre Channel or iSCSI, to provide a quorum disk and cluster storage. Highly available initiators and targets: The initiators are in a highly available failover cluster, which is connected to a failover cluster that contains two or more nodes. A single subnet connects the initiator cluster to the storage appliance cluster. The storage appliances are connected to external storage, such as Fibre Channel or iSCSI, to provide a quorum disk and cluster storage.

Requirements for iSCSI storage failover clustering

You can configure failover clustering to provide high availability for the iSCSI storage provided by Windows Server 2008 R2 or Windows Storage Server 2008 R2. Configuring failover clustering for Windows Server 2008 R2 or Windows Storage Server 2008 R2 is slightly different from configuring failover clustering in Windows Server 2008. These differences are in the requirements that are needed to support the Microsoft iSCSI Software Target 3.3. Microsoft iSCSI Software Target 3.3 is installed on each node in the failover cluster. There are no iSCSI targets before the failover cluster is created.

Each node that will participate in the failover cluster passes all cluster validation tests in the Failover Cluster Management console. The Failover Cluster feature is installed on each node and is configured to use a shared storage back-end such as iSCSI, Fibre Channel, or SAS interconnect. There is at least one cluster disk listed in Available Storage in the Failover Cluster Management console. The network adapters are configured to support separate subnets for storage and client access.

14

Creating a failover cluster

Creating a failover cluster that uses Microsoft iSCSI Software Target requires a modified procedure from typical failover cluster creation. When you create a failover, use the following steps as a guide: Connect to iSCSI storage: Use Microsoft iSCSI Software Initiator to connect each node in the failover cluster to the iSCSI storage. A failover cluster requires that each node have access to storage for cluster functions and for data storage to provide as a high available resource. . Create the failover cluster: Use the Failover Cluster Management console to create a new failover cluster. Install Microsoft iSCSI Software Target: Install Microsoft iSCSI Software Target on each node in the cluster if your failover cluster will provide highly available block storage. Configure a resource group: Use the Configure a Service or Application Wizard in the Failover Cluster Management console to create a resource group. Resource group names must be unique on a failover cluster. Create an iSCSI target: Use the Microsoft iSCSI Software Target console to create a new iSCSI target. Create virtual disks: Use Microsoft iSCSI Software Target to create virtual disks for each target. Assign an iSCSI initiator: Assign an initiator for each iSCSI target that you create. This link between an initiator and the target prevents other computers from accessing the target.

Interoperability with Non-Microsoft iSCSI Initiators

This topic provides information about interoperability and support for using Microsoft iSCSI Software Target versions 3.1, 3.2, and 3.3 with non-Microsoft iSCSI initiators. Microsoft iSCSI Software Target is supplied only through an OEM. End-users must seek support from their OEM vendor or reseller. If necessary, the OEM can initiate a support request with Microsoft.

Version and platform supportability

Following are version and platform supportability details for Microsoft iSCSI Software Target: Microsoft iSCSI Software Target 3.1 is installed by default on Windows Unified Data Storage Server 2003, and it is available as an optional add-on to Windows Storage Server 2003 R2. Microsoft iSCSI Software Target 3.2 can be preinstalled by the OEM on Windows Storage Server 2008. It is also available as an optional add-on to Windows Storage Server 2008 R2. Microsoft iSCSI Software Target 3.3 can be downloaded from the Microsoft Download Center to run on Windows Server 2008 R2.

15

Note Microsoft iSCSI Software Target versions 3.1, 3.2, and 3.3 are interoperable with iSCSI initiators that comply with the standard iSCSI protocol. (For details of known issues, see Microsoft iSCSI Software Target 3.3 Implementation Notes. At the request of certain OEMs, Microsoft has tested discovery, log-on and log-off, and I/O of the following non-Microsoft iSCSI initiators to determine interoperability with Microsoft iSCSI Software Target: SUSE Linux Enterprise Server 10 Red Hat Enterprise Linux 5 QLogic QLE4062C-SP, firmware 3.00.01.24 Microsoft conducted these interoperability tests at the request of certain OEMs. Microsoft has not approved any of the iSCSI initiators listed through a formal Microsoft logo or certification program. This testing should not be construed to represent promotion or support by Microsoft of the iSCSI initiators listed.

Support
The OEM is the customers primary contact for the resolution of all iSCSI initiator and iSCSI target interoperability issues. Microsoft is committed to working with OEMs to resolve interoperability issues that involve Microsoft iSCSI Software Target, but Microsoft is not responsible for resolving any issues that are caused by non-Microsoft iSCSI initiators. The following policy governs how Microsoft will work to reproduce and resolve issues that involve Microsoft iSCSI Software Target: Interoperability issues that involve the non-Microsoft iSCSI initiators that are previously listed Microsoft will work with the OEM to reproduce interoperability issues that involve the nonMicrosoft initiators previously listed, and to resolve only those issues directly caused by Microsoft iSCSI Software Target. Microsoft will not resolve interoperability issues caused by non-Microsoft iSCSI initiators. Interoperability issues that involve non-Microsoft iSCSI initiators that are not previously listed Microsoft is committed to working with OEMs to resolve interoperability issues that involve non-Microsoft iSCSI initiators that are not previously listed. However, each OEM is solely responsible for reproducing interoperability issues on its premises and allowing Microsoft to perform remote analysis. Moreover, Microsoft will resolve only interoperability issues that are directly caused by Microsoft iSCSI Software Target.

16