Win Hu 5.3 Install

8/6/2019 Win Hu 5.3 Install

1/118

Windows Host Utilities 5.3

Installation and Setup Guide

NetApp, Inc.

495 East Java DriveSunnyvale, CA 94089 U.S.A.Telephone: +1 (408) 822-6000

Fax: +1 (408) 822-4501Support telephone: +1 (888) 4-NETAPP

Documentation comments: [email protected]

Information Web: http://www.netapp.com

Part number 215-05164_A0

February 2010


2/118


3/118

Contents

Copyright information ................................................................................. 9Trademark information ............................................................................. 11

About this guide .......................................................................................... 13

Audience .................................................................................................................... 13

Terminology .............................................................................................................. 13

Where to enter commands ......................................................................................... 14

Keyboard and formatting conventions ...................................................................... 15

Special messages ....................................................................................................... 16

How to send your comments ..................................................................................... 16

New features in this Host Utilities release ................................................ 17

Introduction to Host Utilities ..................................................................... 19

What the Host Utilities are ........................................................................................ 19

Tasks required for installing and configuring the Host Utilities ............................... 20

What the Host Utilities Contain ................................................................................. 20

Windows configurations supported by the Host Utilities .......................................... 21

Windows configurations that support ALUA ............................................................ 22

Protocols supported by the Host Utilities .................................................................. 22

Data ONTAP and Fibre Channel ................................................................... 23

Data ONTAP and Fibre Channel over Ethernet ............................................ 24

Data ONTAP and iSCSI ................................................................................ 25

Dynamic disk support ................................................................................................ 26

Multipathing options supported by the Host Utilities ............................................... 26

What is Hyper-V ........................................................................................................ 27

Methods for using storage with Hyper-V ...................................................... 28

Methods for clustering Windows hosts with Hyper-V .................................. 28

Recommended LUN layout with Hyper-V .................................................... 29Virtual Server 2005 overview .................................................................................... 29

About using virtual hard disks ....................................................................... 30

Virtual machines and iSCSI initiators ........................................................... 30

About SAN booting ................................................................................................... 30

Support for non-English operating system versions .................................................. 31

Where to find more information ................................................................................ 31

Table of Contents | 3


4/118

Installing and Configuring Host Utilities ................................................. 33

Installing and configuring the Host Utilities (high level) .......................................... 33

Verifying your host and storage system configuration .............................................. 34

Confirming your storage system configuration ......................................................... 35

Configuring FC HBAs and switches ......................................................................... 35

Checking the media type of FC ports ........................................................................ 36

Configuring iSCSI initiators and HBAs .................................................................... 37

iSCSI software initiator options .................................................................... 37

Downloading the iSCSI software initiator ..................................................... 38

Installing the iSCSI Initiator software ........................................................... 39

Installing the iSCSI HBA .............................................................................. 39

Options for iSCSI sessions and error recovery levels ................................... 41

Options for using CHAP with iSCSI Initiators ............................................. 41Using RADIUS for iSCSI authentication ...................................................... 42

Installing multipath I/O software ............................................................................... 44

How to have a DSM multipath solution ........................................................ 44

Disabling ALUA for Data ONTAP DSM 3.3.1 and earlier .......................... 45

Enabling ALUA for FC with msdsm ............................................................. 45

Configuring Hyper-V systems ................................................................................... 46

Adding virtual machines to a failover cluster ................................................ 46

Configuring SUSE Linux guests for Hyper-V .............................................. 47

Hyper-V VHD requires alignment for best performance .............................. 48

Installing Veritas Storage Foundation ....................................................................... 52

Using Veritas Storage Foundation 5.1 for Windows ..................................... 52

Using Veritas Storage Foundation 5.1 SP1 for Windows ............................. 52

Installation process overview .................................................................................... 53

Installing the Host Utilities interactively ....................................................... 53

Installing the Host Utilities from a command line ........................................ 54

About SnapDrive for Windows ................................................................................. 55

Repairing and removing Windows Host Utilities ...................................................... 55

Repairing or removing Windows Host Utilities interactively ....................... 56

Repairing or removing Windows Host Utilities from a command line ......... 56

Removing Windows Host Utilities affects DSM .......................................... 56

Host configuration settings ........................................................................ 59

What are FC and iSCSI identifiers ............................................................................ 59

Recording the WWPN ................................................................................... 59

4 | Windows Host Utilities 5.3 Installation and Setup Guide


5/118

Recording the iSCSI initiator node name ...................................................... 62

Overview of settings used by the Host Utilities ........................................................ 62

Summary of registry values set by Windows Host Utilities .......................... 63

Summary of FC HBA values set by Windows Host Utilities ........................ 66

ManageDisksOnSystemBuses setting used by the Host Utilities .................. 67

ClusSvcHangTimeout setting ........................................................................ 67

TimeOutValue setting used by the Host Utilities .......................................... 67

PathVerifyEnabled setting used by the Host Utilities ................................... 68

PDORemovePeriod setting used by the Host Utilities .................................. 68

RetryCount setting used by the Host Utilities ............................................... 69

RetryInterval setting used by the Host Utilities ............................................. 69

DsmMaximumStateTransitionTime and

DsmMaximumRetryTimeDuringStateTransition settings used by theHost Utilities ............................................................................................ 70

MPIOSupportedDeviceList setting used by the Host Utilities ...................... 70

DsmSupportedDeviceList setting used by Host Utilities .............................. 70

IPSecConfigTimeout setting used by the Host Utilities ................................ 71

LinkDownTime setting used by the Host Utilities ........................................ 71

MaxRequestHoldTime setting used by the Host Utilities ............................. 71

FC HBA parameters set by the Host Utilities ................................................ 72

Setting up LUNs .......................................................................................... 73

LUN overview ........................................................................................................... 73

LUN types to use for hosts and guest operating systems .............................. 73

Overview ofcreating LUNs .......................................................................... 74

Initiator group overview ............................................................................................ 75

Mapping LUNs to igroups ............................................................................. 76

About mapping LUNs for Windows clusters ................................................ 76

About FC targets ........................................................................................................ 76

About proxy paths in FC configurations ....................................................... 76

Adding iSCSI targets ................................................................................................. 79

About dependent services on the Native Stack and iSCSI ............................ 80

About dependent services on Veritas and iSCSI ........................................... 80

Accessing LUNs on hosts that use Veritas Storage Foundation ............................... 80

Accessing LUNs on hosts that use the native OS stack ............................................ 81

Overview of initializing and partitioning the disk ..................................................... 82

Troubleshooting .......................................................................................... 83



6/118

Areas to check for possible problems ........................................................................ 83

Displaying Host Utilities and HBA version information .......................................... 84

Updating the HBA software driver ............................................................................ 85

Understanding the Host Utilities changes to FC HBA driver settings ...................... 86

Verifying the Emulex HBA driver settings on FC systems ........................... 86

Verifying the QLogic HBA driver settings on FC systems ........................... 87

Enabling logging on the Emulex HBA ...................................................................... 88

Enabling logging on the QLogic HBA ...................................................................... 88

FCoE troubleshooting overview ................................................................................ 88

Troubleshooting the FCoE initiator to switch connection ............................. 89

Troubleshooting the FCoE switch ................................................................. 90

Troubleshooting the FCoE switch to target connection ................................ 90

Troubleshooting FCoE failover problems ..................................................... 91About the diagnostic programs .................................................................................. 91

Installing the nSANity data collection program ............................................ 92

Collecting diagnostic data using nSANity ..................................................... 92

About collecting information on Veritas Storage Foundation ................................... 93

SAN Booting ................................................................................................ 95

What SAN booting is ................................................................................................. 95

How SnapDrive supports SAN booting ......................................................... 96

General requirements for SAN booting ......................................................... 96

About queue depths used with FC SAN booting ........................................... 96

Configuring FC SAN booting .................................................................................... 97

About BootBIOS and SAN booting .............................................................. 98

Enabling Emulex BootBIOS using HBAnyware ........................................... 98

Enabling Emulex BootBIOS using LP6DUTIL ............................................ 99

Enabling QLogic BootBIOS .......................................................................... 99

WWPN for the HBA required ..................................................................... 100

Configuring a single path between the host and storage system ................. 101

Creating the boot LUN ............................................................................................ 103

Configuring Emulex BootBIOS .............................................................................. 103

Configuring QLogic BootBIOS ............................................................................... 104

About configuring BIOS to allow booting from a LUN ......................................... 105

Configuring a Dell BIOS Revision A10 ...................................................... 106

Configuring an IBM BIOS .......................................................................... 106

Configuring a Phoenix BIOS 4 Release 6 ................................................... 106



7/118

Configuring QLogic iSCSI HBA boot BIOS settings ............................................. 107

Configuration process requires limited paths to HBA ................................. 107

Setting iSCSI HBA parameters in boot BIOS ............................................. 107

Getting the correct driver for the boot LUN ............................................................ 108

Installing Windows on the boot LUN .......................................................... 108

Configuring a VCS or MSCS cluster with Veritas in a SAN booted environment . 110

Index ........................................................................................................... 111



8/118


9/118

Copyright information

Copyright 19942010 NetApp, Inc. All rights reserved. Printed in the U.S.A.

No part of this document covered by copyright may be reproduced in any form or by any means

graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an

electronic retrieval systemwithout prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license and

disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR

IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,

WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE

GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF

ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.

NetApp assumes no responsibility or liability arising from the use of products described herein,

except as expressly agreed to in writing by NetApp. The use or purchase of this product does notconvey a license under any patent rights, trademark rights, or any other intellectual property rights of

NetApp.

The product described in this manual may be protected by one or more U.S.A. patents, foreign

patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to

restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer

Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Copyright information | 9


10/118


11/118

Trademark information

NetApp; the NetApp logo; the Network Appliance logo; Cryptainer; Cryptoshred; DataFabric; DataONTAP; Decru; Decru DataFort; FAServer; FilerView; FlexCache; FlexClone; FlexShare; FlexVol;

FPolicy; gFiler; Go further, faster; Manage ONTAP; MultiStore; NearStore; NetCache; NOW

(NetApp on the Web); ONTAPI; RAID-DP; SANscreen; SecureShare; Simulate ONTAP;

SnapCopy; SnapDrive; SnapLock; SnapManager; SnapMirror; SnapMover; SnapRestore;

SnapValidator; SnapVault; Spinnaker Networks; Spinnaker Networks logo; SpinAccess;

SpinCluster; SpinFlex; SpinFS; SpinHA; SpinMove; SpinServer; SpinStor; StoreVault; SyncMirror;

Topio; vFiler; VFM; and WAFL are registered trademarks of NetApp, Inc. in the U.S.A. and/or other

countries. Network Appliance, Snapshot, and The evolution of storage are trademarks of NetApp,

Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. The

StoreVault logo, ApplianceWatch, ApplianceWatch PRO, ASUP, AutoSupport, ComplianceClock,DataFort, Data Motion, FlexScale, FlexSuite, Lifetime Key Management, LockVault, NOW,

MetroCluster, OpenKey, ReplicatorX, SecureAdmin, Shadow Tape, SnapDirector, SnapFilter,

SnapMigrator, SnapSuite, Tech OnTap, Virtual File Manager, VPolicy, and Web Filer are

trademarks of NetApp, Inc. in the U.S.A. and other countries. Get Successful and Select are service

marks of NetApp, Inc. in the U.S.A.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business

Machines Corporation in the United States, other countries, or both. A complete and current list of

other IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or

other countries. Microsoft is a registered trademark and Windows Media is a trademark of MicrosoftCorporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,

RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and

SureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.

All other brands or products are trademarks or registered trademarks of their respective holders and

should be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

Trademark information | 11


12/118


13/118

About this guide

You can use your product more effectively when you understand this document's intended audienceand the conventions that this document uses to present information.

Next topics

Audienceon page 13

Terminologyon page 13

Where to enter commandson page 14

Keyboard and formatting conventionson page 15

Special messageson page 16

How to send your commentson page 16

AudienceThis document is written with certain assumptions about your technical knowledge and experience.

This guide is for administrators of Windows host computers and NetApp storage systems who are

configuring storage using Windows Host Utilities software.

You should be familiar with the specifics of your configuration, including the following items.

The iSCSI or Fibre Channel (FC) protocols.

Windows multipathing software.

FC host bus adapters (HBAs), FCoE converged network adapters (CNAs) and iSCSI initiators

(software or HBA).

TerminologyTo understand the concepts in this document, you might need to know how certain terms are used.

Storage terms

LUN (logical

unit number)

Refers to a logical unit of storage identified by a number.

storage

controller

Refers to the component of a storage system that runs the Data ONTAP

operating system and controls its disk subsystem. Storage controllers are also

sometimes called controllers, storage appliances, appliances, storage engines,

heads, CPU modules, or controller modules.

About this guide | 13


14/118

storage system Refers to the hardware device running Data ONTAP that receives data from and

sends data to native disk shelves, third-party storage, or both. Storage systems

that run Data ONTAP are sometimes referred to as filers, appliances, storage

appliances, V-Series systems, or systems.

Cluster and high-availability terms

active/active

configuration

In the Data ONTAP 7.2 and 7.3 release families, refers to a pair of storage

systems (sometimes called nodes) configured to serve data for each other if one

of the two systems stops functioning. Also sometimes referred to as active/active

pairs. In the Data ONTAP 7.1 release family and earlier releases, this

functionality is referred to as a cluster.

cluster In the Data ONTAP 7.1 release family and earlier releases, refers to a pair of

storage systems (sometimes called nodes) configured to serve data for each other

if one of the two systems stops functioning. In the Data ONTAP 7.3 and 7.2release families, this functionality is referred to as an active/active configuration.

Where to enter commandsYou can use your product more effectively when you understand how this document uses command

conventions to present information.

You can perform common administrator tasks in one or more of the following ways:

You can enter commands either at the system console or from any client computer that can obtainaccess to the storage system using a Telnet or Secure Shell (SSH) session.

In examples that illustrate command execution, the command syntax and output shown might

differ from what you enter or see displayed, depending on your version of the operating system.

You can use the graphical user interface.

You can enter Windows, ESX, HP-UX, AIX, Linux, and Solaris commands at the applicable

client console.



You can use the client graphical user interface.

Your product documentation provides details about how to use the graphical user interface.

You can enter commands either at the switch console or from any client that can obtain access to

the switch using a Telnet session.





15/118

Keyboard and formatting conventionsYou can use your product more effectively when you understand how this document uses keyboard

and formatting conventions to present information.

Keyboard conventions

Convention What it means

The NOW site Refers to NetApp On the Web athttp://now.netapp.com/.

Enter, enter Used to refer to the key that generates a carriage return; the key is named

Return on some keyboards.

Used to mean pressing one or more keys on the keyboard and then pressing theEnter key, or clicking in a field in a graphical interface and then typing

information into the field.

hyphen (-) Used to separate individual keys. For example, Ctrl-D means holding down the

Ctrl key while pressing the D key.

type Used to mean pressing one or more keys on the keyboard.

Formatting conventions

Convention What it means

Italicfont Words or characters that require special attention.

Placeholders for information that you must supply.

For example, if the guide says to enter the arp -dhostname command,

you enter the characters "arp -d" followed by the actual name of the host.

Book titles in cross-references.

Monospaced font Command names, option names, keywords, and daemon names.

Information displayed on the system console or other computer monitors.

Contents of files.

File, path, and directory names.

Bold monospaced

font

Words or characters you type. What you type is always shown in lowercase

letters, unless your program is case-sensitive and uppercase letters are

necessary for it to work properly.

About this guide | 15
http://now.netapp.com/


16/118

Special messagesThis document might contain the following types of messages to alert you to conditions that you

need to be aware of.

Note: A note contains important information that helps you install or operate the system

efficiently.

Attention: An attention notice contains instructions that you must follow to avoid a system crash,

loss of data, or damage to the equipment.

How to send your commentsYou can help us to improve the quality of our documentation by sending us your feedback.

Your feedback is important in helping us to provide the most accurate and high-quality information.

If you have suggestions for improving this document, send us your comments by e-mail to

[email protected]. To help us direct your comments to the correct division, include in the

subject line the name of your product and the applicable operating system. For example, FAS6070

Data ONTAP 7.3, or Host UtilitiesSolaris, or Operations Manager 3.8Windows.

mailto:[email protected]


17/118

New features in this Host Utilities release

Windows Host Utilities 5.3 includes several new features and support for additional configurations.Host Utilities 5.3 includes the following changes from 5.2:

The diagnostic programs, such as controller_info.exe, are replaced by the nSANity

diagnostic program. The nSANity program is not included with Windows Host Utilities; you

download, install, and run it when requested to do so by technical support.

A new script is provided to set required timeouts for Linux guest operating systems. The script is

provided as a .iso image that you mount in the Hyper-V virtual CD-ROM.

The mbralign.exe program detects and corrects the alignment ofblock boundaries in VHD

files to ensure best read/write performance with NetApp storage systems.

If the Host Utilities installation program detects the Data ONTAP DSM for Windows MPIOsoftware on the host, it skips most Windows registry and HBA settings. It relies instead on the

values set by the DSM installation program.

The Emulex and QLogic HBA timeout values are changed for configurations without Data

ONTAP DSM for Windows MPIO software to reduce the time needed to resume I/O after a fault.

RADIUS authentication is supported for iSCSI initiators with Data ONTAP 8.0 targets.

New Microsoft Windows hotfixes are required.

Related concepts

About the diagnostic programson page 91

Hyper-V VHD requires alignment for best performanceon page 48ClusSvcHangTimeout settingon page 67

Using RADIUS for iSCSI authenticationon page 42

Related tasks

Configuring SUSE Linux guests for Hyper-Von page 47

Related references

Summary of FC HBA values set by Windows Host Utilitieson page 66

New features in this Host Utilities release | 17


18/118


19/118

Introduction to Host Utilities

This section introduces the Host Utilities and what they contain.

Next topics

What the Host Utilities areon page 19

Tasks required for installing and configuring the Host Utilitieson page 20

What the Host Utilities Containon page 20

Windows configurations supported by the Host Utilitieson page 21

Windows configurations that support ALUA on page 22

Protocols supported by the Host Utilitieson page 22

Dynamic disk supporton page 26

Multipathing options supported by the Host Utilitieson page 26

What is Hyper-Von page 27

Virtual Server 2005 overviewon page 29

About SAN bootingon page 30

Support for non-English operating system versionson page 31

Where to find more informationon page 31

What the Host Utilities areThe Host Utilities are a set of software programs and documentation that enable you to connect host

computers to NetApp storage systems.

The Host Utilities include the following components:

An installation program that sets required parameters on the host computer and on certain host

bus adapters (HBAs).

A program (san_version.exe) that reports the Host Utilities version and displays driver

version information for Emulex and QLogic HBAs in the host.

A program (mbralign.exe) to detect and correct VHD alignment problems for Hyper-V virtual

machines. An ISO file (LinuxGuestConfig.iso) you can mount in Hyper-V virtual machines running

Linux that contains a script (linux_gos_timeout-install.sh) for setting disk timeouts for

best read/write performance with NetApp storage.

This documentation, which describes how to install the Host Utilities and troubleshoot common

problems.

Introduction to Host Utilities | 19


20/118

Tasks required for installing and configuring the HostUtilities

Installing and configuring the Host Utilities involves performing a number of tasks on the host and

the storage system.

The required tasks are as follows.

1. Install the Host Utilities and other required and optional software.

2. Record the FC and iSCSI initiator identifiers.

3. Create LUNs and make them available as disks on the host computer.

The following tasks are optional, depending on your configuration.

Change the Fibre Channel cfmode setting of the storage system to single_image.

Configure SAN booting of the host.

Related concepts

Host configuration settingson page 59

Setting up LUNson page 73

SAN Bootingon page 95

Related tasks

Installingand ConfiguringHost Utilitieson page 33

Related information

Changing the Cluster cfmode Setting in Fibre Channel SAN Configurations - http://

now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/QuickRef/SSICFMODE_1205.pdf

What the Host Utilities ContainThe Host Utilities include an installation program. When you install the Host Utilities software, the

installer sets required Windows registry and HBA parameters.

The following programs and files are installed on the Windows host computer. The default directory

is C:\Program Files\NetApp\Windows Host Utilities.

Program Purpose

emulexhba.reg Used by the installation program to set Emulex Fibre

Channel host bus adapter (HBA) parameters.

http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/QuickRef/SSICFMODE_1205.pdfhttp://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/QuickRef/SSICFMODE_1205.pdf


21/118

Program Purpose

fcconfig.exe Used by the installation program to set HBA

parameters. Not installed if Data ONTAP DSM for

Windows MPIO is detected on the host.

fcconfig.ini Used by the installation program to set HBA

parameters. Not installed if Data ONTAP DSM for

Windows MPIO is detected on the host.

LinuxGuestConfig.iso Sets disk timeouts for Hyper-V virtual machines

running Linux. Must be run from the Linux guest.

mbralign.exe Detects and corrects VHD alignment problems for

Hyper-V virtual machines.

Notices.pdf Contains legal notices for the Host Utilities programs.

QLSDM.DLL Used by the installation program to set QLogic Fibre

Channel HBA parameters.

san_version.exe Displays the version of the Host Utilities and Fibre

Channel HBAs.

Related tasks


Windows configurations supported by the Host UtilitiesThe Host Utilities support a number of Windows host configurations.

Depending on your specific environment, the Host Utilities support the following:

iSCSI paths to the storage system

Fibre Channel paths to the storage system

Multiple paths to the storage system when a multipathing solution is installed

Virtual machines using Hyper-V (Windows Server 2008, Windows Server 2008 R2) or Virtual

Server 2005 (Windows Server 2003), both parent and guest

Veritas Storage Foundation

SAN booting

Use the Interoperability Matrix to find a supported combination of host and storage system

components and software and firmware versions.

Related information

NetApp Interoperability Matrix - http://now.netapp.com/NOW/products/interoperability/

http://now.netapp.com/NOW/products/interoperability/


22/118

Windows configurations that support ALUAWindows hosts support ALUA with certain combinations of Windows, Data ONTAP, Host Utilities,

and MPIO software.

The following table lists configurations that support ALUA (asymmetric logical unit access). Use the

Interoperability Matrix to determine a supported combination of Windows, Data ONTAP, Host

Utilities, and MPIO software. Then enable or disable ALUA based on the information in the table.

Windows version MPIO software Minimum Data ONTAP Supported ?

Server 2008

Server 2008 R2

Microsoft DSM (msdsm) 7.3.0 Yes

Server 2008

Server 2008 R2

Data ONTAP DSM 3.3.1 and

earlier

none No

Server 2008

Server 2008 R2

Veritas DSM from Storage

Foundation for Windows 5.1

and earlier

none No

Server 2003 Data ONTAP DSM none No

Server 2003 Veritas DSM from Storage

Foundation for Windows 5.1

and earlier

none No

Note: For MPIO software not listed in this table, see the documentation for that software for

updated ALUA support and requirements.

ALUA is required when using the Microsoft DSM (msdsm).

Protocols supported by the Host UtilitiesThe Host Utilities provide support for Fibre Channel, Fibre Channel over Ethernet, iSCSI, and NFS

connections to the storage system.

Next topics

Data ONTAP and Fibre Channelon page 23

Data ONTAP and Fibre Channel over Etherneton page 24

Data ONTAP and iSCSIon page 25



23/118

Data ONTAP and Fibre ChannelThe Fibre Channel (FC) protocol for SCSI is one method for enabling the host to access data on

storage systems that run supported versions of Data ONTAP software.

Fibre Channel connections require one or more supported host bus adapters (HBAs) in the host.

The storage system is an FC target device. The Fibre Channel service must be licensed and running

on the storage system.

Each HBA port is an initiator that uses FC to access logical units of storage (LUNs) on a storage

system to store and retrieve data.

On the host, a worldwide port name (WWPN) identifies each port on an HBA. The host WWPNs are

used as identifiers when creating initiator groups on a storage system. An initiator group permits host

access to specific LUNs on a storage system.

Supported FC configurations

The Host Utilities support fabric-attached SAN network configurations and direct-attached

configurations.

The following configurations are supported:

Fabric-attached storage area network (SAN). Two variations of fabric-attached SANs are

supported:

A single-host FC connection from the HBA to the storage system through a single switch. A

host is cabled to a single FC switch that is connected by cable to redundant FC ports on an

active/active storage system configuration. A fabric-attached single-path host has one HBA. Two (or more) FC connections from the HBA to the storage system through dual switches or

a zoned switch. In this configuration, the host has at least one dual-port HBA or two single-

port HBAs. The redundant configuration avoids the single point of failure of a single-switch

configuration. This variation requires a supported multipathing solution and device-specific

module (DSM), such as the Data ONTAP DSM for Windows MPIO or the Veritas DMP

DSM.

Direct-attached. A single host with a direct FC connection from the HBA to stand-alone or active/

active storage systems.

ALUA (asymmetric logical unit access) must be enabled on igroups when using the Microsoft DSM

(msdsm), and must be disabled when using the Data ONTAP DSM 3.3.1 for Windows MPIO and

earlier or the Veritas DMP DSM from Storage Foundation for Windows 5.1 and earlier. ALUA

requires a supported version of Data ONTAP software; see the Windows Host Utilities Release

Notesfor the latest ALUA requirements.

Note: Use redundant configurations with two FC switches for high availability in production

environments. However, direct FC connections and switched configurations using a single zoned

switch might be appropriate for less critical business applications.



24/118

For more detailed information about the supported Fibre Channel topologies, including diagrams, see

the Fibre Channel and iSCSI Configuration Guidefor your version of Data ONTAP.

For more information about using Fibre Channel on your storage system, see the Data ONTAP Block

Access Management Guide for iSCSI and FCfor your version of Data ONTAP.

Related information

Fibre Channel and iSCSI Configuration Guide - http://now.netapp.com/NOW/knowledge/docs/

san/fcp_iscsi_config/

Data ONTAP and Fibre Channel over EthernetThe Fibre Channel over Ethernet (FCoE) protocol for SCSI is one method for enabling the host to

access data on storage systems that run supported versions of Data ONTAP software.

Fibre Channel over Ethernet (FCoE) is a new model for connecting hosts to storage systems. FCoE is

very similar to traditional Fibre Channel (FC), as it maintains existing FC management and controls,

but the hardware transport is a lossless 10-gigabit Ethernet network.

Setting up an FCoE connection requires one or more supported converged network adapters (CNAs)

in the host, connected to a supported data center bridging (DCB) Ethernet switch. The CNA is a

consolidation point and effectively serves as both an HBA and an Ethernet adapter.

As an HBA, the presentation to the host is FC targets and all FC traffic is sent out as FC frames

mapped into Ethernet packets (FC over Ethernet). The 10 gigabit Ethernet adapter is used for IP

traffic, such as iSCSI, NFS, and HTTP. Both FCoE and IP communications through the CNA run

over the same 10 gigabit Ethernet port, which connects to the DCB switch.

In general, you configure and use FCoE connections just like traditional FC connections.

Supported FCoE configurations

The Host Utilities support fabric-attached SAN network configurations, but direct-attached

configurations are not supported.

FCoE adapter configuration

The converged network adapters (CNA) must be directly cabled to a supported data center bridging

(DCB) switch. No intermediate Ethernet switches may be connected between the CNA end point and

the DCB switch. The CNA is a consolidation point and effectively serves as both an HBA and an

Ethernet adapter.

Updating the drivers and firmware for a CNA is just like updating them for a traditional FC HBA.

Check the Interoperability Matrix for the supported firmware versions.

The CNA uses the same timeout parameters as a traditional FC HBA. The Windows Host Utilities

installation program detects the FC HBA portion of the CNA and sets the required parameters. If you

install a CNA after installing the Host Utilities, run the Repair option of the installation program to

configure the CNA parameters.

http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/


25/118

FCoE cabling configuration

FCoE cabling information and diagrams are included in the Fibre Channel and iSCSI Configuration

Guidefor your version of Data ONTAP software.

FCoE switch configuration

The DCB switch requires special setup steps for FCoE. See the documentation supplied by the switch

manufacturer. For example, the steps for a Cisco 5020 are included in the Cisco Nexus 5000 Series

Switch Fabric Manager Software Configuration Guide.

You zone the DCB switch for FCoE just like you zone a traditional FC switch.

Related information

NetApp Interoperability Matrix - now.netapp.com/NOW/products/interoperability

Cisco Nexus 5000 Series Switch Fabric Manager Software Configuration Guide - www.cisco.com/

en/US/products/ps9670/tsd_products_support_series_home.html

Data ONTAP and iSCSIThe iSCSI protocol is one method for enabling the host to access data on storage systems that run

supported versions of Data ONTAP software.

iSCSI connections can use a software initiator over the hosts standard Ethernet interfaces, or one or

more supported host bus adapters (HBAs).

The iSCSI protocol is a licensed service on the NetApp storage system that enables you to transfer

block data to hosts using the SCSI protocol over TCP/IP. The iSCSI protocol standard is defined by

RFC 3720 (www.ietf.org).

The storage system is an iSCSI target device. A host running the iSCSI Initiator software or an iSCSI

HBA uses the iSCSI protocol to access LUNs on a storage system.

The connection between the initiator and target uses a standard TCP/IP network. No special network

configuration is needed to support iSCSI traffic. The network can be a dedicated TCP/IP network, or

your regular public network. The storage system listens for iSCSI connections on TCP port 3260. For

more information on using iSCSI on your storage system, see the Data ONTAP Block Access

Management Guide for iSCSI and FCfor your version of Data ONTAP.

About iSCSI on IPv6You can use iSCSI connections over networks running Internet Protocol version 6 (IPv6) if all

components of the network have IPv6 support enabled.

IPv6 uses a longer IP address than the previous IPv4. This enables a larger address space. IPv6

address look likefe80:0000:0000:0000:ad7a:41a0:62d0:dd0b

IPv4 addresses look like192.168.2.3

http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.htmlhttp://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.htmlhttp://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.htmlhttp://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.htmlhttp://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.htmlhttp://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.htmlhttp://now.netapp.com/NOW/products/interoperability


26/118

Windows Host Utilities supports IPv6 starting with version 5.1. A version of Data ONTAP software

that supports IPv6 is required on the storage system.

There are no IPv6-specific tasks for Windows Host Utilities. See the Microsoft Windows

documentation for information about enabling IPv6 on the Windows host. See your Ethernet switch

documentation for information on enabling IPv6 on your switches if needed. See the Data ONTAPNetwork Management Guidefor your version of Data ONTAP for information on enabling IPv6 on

the storage system.

Note: The diagnostic programs included with Windows Host Utilities do not currently support

IPv6 addresses. See the Host Utilities Release Notesfor information about collecting diagnostic

information in an IPv6 configuration and any updates to the diagnostic programs.

Dynamic disk support

Windows dynamic disks are supported with specific configuration requirements.

When using the native Windows storage stack, all LUNs composing the dynamic volume must be

located on the same storage system controller.

When using Veritas Storage Foundation for Windows, the LUNs composing the dynamic volume can

span storage controllers in active/active configurations.

Dynamic disks are not supported by SnapDrive for Windows.

Multipathing options supported by the Host UtilitiesThe Host Utilities support multiple FC (Fibre Channel) paths, multiple iSCSI paths, or a combination

of FC and iSCSI paths.

Configure multiple paths to ensure a highly available connection between the Windows host and

storage system.

Multipath I/O (MPIO) software is required any time a Windows host has more than one path to the

storage system. The MPIO software presents a single disk to the operating system for all paths, and a

device-specific module (DSM) manages path failover. Without MPIO software, the operating system

could see each path as a separate disk, which can lead to data corruption.

On a Windows system, there are two main components to any MPIO configuration: the Windows

MPIO components and a DSM. MPIO is supported for Windows Server 2003, Windows Server

2008, and Windows Server 2008 R2 systems. MPIO is not supported for Windows XP and Windows

Vista running in a Hyper- V virtual machine.

When you select MPIO support during Host Utilities installation, the Host Utilities installer installs

the Microsoft MPIO components on Windows Server 2003 or enables the included MPIO feature of

Windows Server 2008.

See the NetApp Interoperability Matrix for the multipathing software currently supported.



27/118

The Microsoft Windows multipathing software uses a DSM to communicate with storage devices

such as NetApp storage systems. You must use only one DSM for a given storage vendor. More

precisely, you can have only one DSM that claims the LUNs for a given vendor ID, product ID

(VID/PID) pair. If you are using Windows Server 2008 or Windows Server 2008 R2, you must

enable the optional Windows multipathing feature before installing a DSM.

A supported DSM is required for multipathing. The following DSMs are available for Windows

hosts.

Data ONTAP

DSM for

Windows

MPIO

This multipathing software supports active/active and active/passive policies on

Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2. If

installed on Windows Server 2008, the Data ONTAP DSM claims NetApp LUNs

and the Microsoft msdsm is not used. ALUA must be disabled on the storage

system igroup when using Data ONTAP DSM 3.3.1 and earlier.

Veritas DMP

DSM

For MPIO using Veritas DMP, only the Veritas DMP DSM is supported; the

Veritas DMP Array Support Library (ASL) is not supported. See the

Interoperability Matrix for details on supported load balance policies with FC and

iSCSI protocols.

Note: If you are using Veritas Storage Foundation for Windows, configure

either Fibre Channel paths or iSCSI paths depending on how you want to

connect to the storage system. There is no support for both Fibre Channel and

iSCSI protocols on the same host with Veritas Storage Foundation.

Windows

Server 2008

msdsm

This is the native DSM provided with Microsoft Windows Server 2008 and

Windows Server 2008 R2 . It offers active/active and active/passive load balance

policies for both the FC and iSCSI protocols. ALUA must be enabled on the

storage system igroup for FC. See the Interoperability Matrix to be sure you have aversion of Data ONTAP software that is supported with this DSM.

Microsoft

iSCSI DSM

This is the DSM provided with the Microsoft iSCSI initiator. You can use this

DSM for iSCSI paths on Windows Server 2003 systems.

Related information


What is Hyper-VHyper-V is a Windows technology that enables you to create multiple virtual machines on a single

physical x64 computer running Microsoft Windows Server 2008 or Windows Server 2008 R2.

Hyper-V is a role available in Microsoft Windows Server 2008 and Windows Server 2008 R2.

Each virtual machine runs its own operating system and applications. For a list of currently-

supported operating systems on Hyper-V virtual machines, see the Windows Host Utilities Release

Notes.



28/118

Next topics

Methods for using storage with Hyper-Von page 28

Methods for clustering Windows hosts with Hyper-Von page 28

Recommended LUN layout with Hyper-Von page 29

Methods for using storage with Hyper-VHyper-V enables you to provision storage using a virtual hard disk, an unformatted (raw) LUN, or an

iSCSI LUN.

Virtual machines use storage on a storage system in the following ways:

A virtual hard disk (IDE or SCSI) formatted as NTFS. The virtual hard disk is stored on a LUN

mapped to the Hyper-V parent system. The guest OS must boot from an IDE virtual hard disk.

An unformatted (raw) LUN mapped to the Hyper-V parent system and provided to the virtual

machine as a physical disk mapped through either the SCSI or IDE virtual adapter.

Note: Do not enable multipathing in Windows Host Utilities installed on a guest OS if you are

using raw (passthru) disks. The raw disks do not show up in the guest OS.

An iSCSI LUN accessed by an iSCSI initiator running on the guest OS.

For Windows Vista, use the built-in iSCSI initiator; multipathing is not supported.

For Windows XP, use Microsoft iSCSI initiator 2.07; multipathing is not supported.

For Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2, use an

iSCSI initiator and multipathing solution that is supported by NetApp for use on a standard

host platform. The guest OS supports the same iSCSI configurations as if it was not running

on a virtual machine.

For SUSE Linux Enterprise Server, use a supported iSCSI initiator and multipathing solution.The guest OS supports the same iSCSI configurations as if it was not running on a virtual

machine.

The parent Hyper-V system can connect to storage system LUNs just like any other Windows Server

2008 or Windows Server 2008 R2 host.

Methods for clustering Windows hosts with Hyper-VHyper-V provides two ways to let you cluster Windows hosts.

You can cluster the parent Hyper-V system with other parent systems using Windows failover

clustering.

You can cluster guest systems running in virtual machines with other guest systems using the

clustering solution supported on the operating system You must use an iSCSI software initiator

on the guest system to access the quorum and shared disks.



29/118

Recommended LUN layout with Hyper-VYou can put one or more virtual hard disks (VHDs) on a single LUN for use with Hyper-V.

The recommended LUN layout with Hyper-V is to put up to 10 VHDs on a single LUN. If you need

less than ten VHDs, put each VHD on its own LUN. If you need more than ten VHDs for a Windowshost, spread the VHDs evenly across about ten LUNs.

When you create virtual machines, store the virtual machine and the VHD it boots from in the same

LUN.

For Windows failover clusters, the layout is different.

For Windows Server 2008 R2 with cluster shared volumes (CSVs), you can have VHDs for

multiple guests on the same LUN.

For failover clusters without CSV, use a separate LUN for each guest's VHDs.

Virtual Server 2005 overviewVirtual Server 2005 R2 enables you to run Windows and Linux virtual machines on Windows Server

2003.

NetApp storage systems support Microsoft Virtual Server 2005 R2 using iSCSI and FC. Virtual

Server 2005 R2 is supported on any supported Windows 2003 configuration.

The virtual machines can use storage system LUNs in one of two ways:

Connect to LUNs from the underlying Windows Server 2003 system. Then create virtual harddisks (VHDs) on those LUNs for the virtual machines. You can use either iSCSI or FC to connect

to the LUNs.

Connect to LUNs using a software iSCSI initiator running on the virtual machine.

For specific configurations that support Virtual Server 2005 R2, see the Interoperability Matrix.

Next topics

About using virtual hard diskson page 30

Virtual machines and iSCSI initiatorson page 30

Related information




30/118

About using virtual hard disksRun the Windows Host Utilities installer to set required parameters on Virtual Server 2005 virtual

machines.

Install Windows Host Utilities on each virtual machine running a Windows operating system thatuses virtual hard disks (VHDs) based on LUNs. This is in addition to the Windows Host Utilities you

install on the physical system that runs Virtual Server 2005.

No changes are required for Virtual Server 2005 virtual machines running a Linux operating system.

Virtual machines and iSCSI initiatorsTo use an iSCSI initiator on a Virtual Server 2005 virtual machine, you must set the required time-

out values.

Run the Windows Host Utilities installer (Windows) or follow the instructions in the Host Utilities

documentation (Linux) to set required timeout values on the virtual machine. An iSCSI initiator on a

virtual machine is installed and works just like the iSCSI initiator on a physical system.

About SAN bootingSAN booting is the general term for booting a Windows host from a storage system LUN instead of

an internal hard disk. The host might or might not have any hard drives installed.

SAN booting offers many advantages. Because the system (C:\) drive is located on the storage

system, all of the reliability and backup features of the storage system are available to the system

drive. You can also clone system drives to simplify deploying many Windows hosts and to reduce

the total storage needed. SAN booting is especially useful for blade servers.

The downside of SAN booting is that loss of connectivity between the host and storage system can

prevent the host from booting. Be sure to use a reliable connection to the storage system.

There are three options for SAN booting a Windows host:

Fibre Channel

HBA

Requires one or more supported adapters. These same adapters can also be used

for data LUNs. The Windows Host Utilities installer automatically configures

required HBA settings.

iSCSI HBA Requires one or more supported adapters. These same adapters can also be usedfor data LUNs, or you can use an iSCSI software initiator for data. You must

manually configure the HBA settings.

iSCSI software

boot

Requires a supported network interface card (NIC) and a special version of the

Microsoft iSCSI software initiator.

For information on iSCSI software boot, see the vendor (emBoot, Intel, or IBM) documentation for

the iSCSI boot solution you choose. Also, see Technical Report 3644.



31/118

Related information

Technical Report 3644 - http://media.netapp.com/documents/tr-3644.pdf

Support for non-English operating system versionsWindows Host Utilities are supported on all Language Editions of Windows Server 2003, Server

2008, and Server 2008 R2. All product interfaces and messages are displayed in English. However,

all variables accept Unicode characters as input.

Where to find more informationFor additional information about host and storage system requirements, supported configurations,

your operating system, and troubleshooting, see the documents listed in the following table.

If you need more information about... Go to...

Known issues, system requirements, and last minute

updates

The latest Host Utilities Release Notes

The latest supported configurations The Interoperability Matrix.

System Configuration Guide.

Configuring the storage system The Data ONTAP Software Setup Guide

The Data ONTAP Block Access Management

Guide for iSCSI and FC

Supported SAN topologies The FC and iSCSI Configuration Guidefor your

version of Data ONTAP software

Installing and configuring the HBA in your host Your HBA vendor documentation

Installing and configuring MPIO using the Data

ONTAP DSM

The Installation and Administration Guidefor that

version of Data ONTAP DSM for Windows MPIO

Installing and configuring Veritas Storage Foundation

for Windows and the Veritas DMP DSM The Veritas Storage Foundation and High

Availability Solutions Installation and Upgrade

Guide

The Veritas Storage Foundation AdministratorsGuide

Configuring Veritas Cluster Server and Microsoft

Clustering in a Storage Foundation environment The Veritas Cluster Server Administrators Guide

The Veritas Storage Foundation Administrators

Guide

Installing and configuring a supported version of

SnapDrive for Windows software

The Installation and Administration Guidefor that

version of SnapDrive for Windows

http://media.netapp.com/documents/tr-3644.pdf


32/118

If you need more information about... Go to...

Managing SAN storage on the storage system Data ONTAP Commands: Manual Page

Reference, Volume 1and Data ONTAP

Commands: Manual Page Reference, Volume 2

The Data ONTAP Block Access ManagementGuide for iSCSI and FC

The FilerView online Help

Related information


FC and iSCSI Configuration Guide - http://now.netapp.com/NOW/knowledge/docs/san/

fcp_iscsi_config/

http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/products/interoperability/


33/118

Installing and Configuring Host Utilities

This section describes how to install and configure the Host Utilities and how to perform relatedtasks.

1. Installing and configuring the Host Utilities (high level)on page 33

2. Verifying your host and storage system configurationon page 34

3. Confirming your storage system configurationon page 35

4. Configuring FC HBAs and switcheson page 35

5. Checking the media type of FC portson page 36

6. Configuring iSCSI initiators and HBAson page 37

7. Installing multipath I/O softwareon page 44

8. Configuring Hyper-V systemson page 469. Installing Veritas Storage Foundationon page 52

10. Installation process overviewon page 53

11. About SnapDrive for Windowson page 55

12. Repairing and removing Windows Host Utilitieson page 55

Installing and configuring the Host Utilities (high level)The following steps provide a high-level overview of what is involved in installing the Host Utilities

and configuring your system to work with that software.

About this task

This section is for people familiar with this operating system and storage systems. If you need more

information, see the detailed instructions for the steps.

Note: If you are upgrading a host running the Data ONTAP DSM from Windows Server 2008 to

Server 2008 R2, you must upgrade to Data ONTAP DSM 3.3.1 before installing Server 2008 R2.

You must also upgrade to Windows Host Utilities 5.2 before upgrading to Windows Server 2008

R2.

Steps

1. Verify your host and storage system configuration.

2. Confirm your storage system is set up.

3. Configure FC HBAs and switches.

4. Check the media type setting of FC target ports.

Installing and Configuring Host Utilities | 33


34/118

5. Install an iSCSI software initiator or HBA.

6. Configure iSCSI options and security.

7. Configure a multipathing solution.

8. Install Veritas Storage Foundation.

9. Install the Host Utilities.

10. Install SnapDrive for Windows.

After you finish

If you add a Windows 2008 R2 host to a failover cluster after installing the Host Utilities, run the

Repair option of the Host Utilities installation program to set the required ClusSvcHangTimeout

parameter.

Verifying your host and storage system configurationBefore you install the Host Utilities, verify that the Host Utilities version supports your host and

storage system configuration.

About this task

The Interoperability Matrix lists all supported configurations. Individual computer models are not

listed; Windows hosts are qualified based on their CPU chips. The following configuration items

must be verified:

Windows host CPU architecture

Windows operating system version, service pack level, and required hotfixes

Note: If you are upgrading a host running the Data ONTAP DSM from Windows Server 2008

to Server 2008 R2, you must upgrade to Data ONTAP DSM 3.3.1 before installing Server 2008

R2. You must also upgrade to Windows Host Utilities 5.2 before upgrading to Windows Server

2008 R2.

HBA model and firmware version

Fibre Channel switch model and firmware version

iSCSI initiator Multipathing software

Veritas Storage Foundation for Windows software

Data ONTAP version and cfmode setting

Option software such as SnapDrive for Windows

Steps

1. Verify that your entire configuration is listed in the matrix.



35/118

2. Verify guest operating systems on Hyper-V virtual machines are shown as supported in the

Windows Host Utilities Release Notes.

Related information


Confirming your storage system configurationYou must make sure your storage system is properly cabled and the FC and iSCSI services are

licensed and started.

About this task

This topic describes the high-level tasks you must complete to configure your storage system for use

with Fibre Channel and iSCSI hosts. See the Data ONTAP Block Access Management Guide foriSCSI and FCfor your version of Data ONTAP for detailed instructions.

Steps

1. Add the iSCSI or FCP license and start the target service. The Fibre Channel and iSCSI protocols

are licensed features of Data ONTAP software. If you need to purchase a license, contact your

NetApp or sales partner representative.

2. Verify your cabling. See the FC and iSCSI Configuration Guidefor detailed cabling and

configuration information.

Related information

FC and iSCSI Configuration Guide - http://now.netapp.com/NOW/knowledge/docs/san/

fcp_iscsi_config/

Configuring FC HBAs and switchesInstall and configure one or more supported Fibre Channel host bus adapters (HBAs) for Fibre

Channel connections to the storage system.

About this task

The Windows Host Utilities installer sets the required Fibre Channel HBA settings.

Note: Do not change HBA settings manually.

http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/products/interoperability/


36/118

Steps

1. Install one or more supported Fibre Channel host bus adapters (HBAs) according to the

instructions provided by the HBA vendor.

2. Obtain the supported HBA drivers and management utilities and install them according to the


The supported HBA drivers and utilities are available from the following locations:

Emulex HBAs Emulex support page for NetApp.

QLogic HBAs QLogic support page for NetApp.

3. Connect the HBAs to your Fibre Channel switches or directly to the storage system.

4. Create zones on the Fibre Channel switch according to your Fibre Channel switch documentation.

Related informationFC and iSCSI Configuration Guide - http://now.netapp.com/NOW/knowledge/docs/san/

fcp_iscsi_config/

Emulex support page for NetApp - www.emulex.com/downloads/netapp.html

QLogic support page for NetApp - http://support.qlogic.com/support/drivers_software.asp

Checking the media type of FC portsThe media type of the storage system FC target ports must be configured for the type of connection

between the host and storage system.

About this task

The default media type setting of auto is for fabric (switched) connections. If you are connecting

the hosts HBA ports directly to the storage system, you must change the media setting of the target

ports to loop.

Steps

1. To display the current setting of the storage systems target ports, enter the following command at

a storage system command prompt:

fcp show adapter -v

The current media type setting is displayed.

2. To change the setting of a target port to loop for direct connections, enter the following

commands at a storage system command prompt:

fcp config adapter down

fcp config adapter mediatype loop

http://http//SUPPORT.QLOGIC.COM/SUPPORT/DRIVERS_SOFTWARE.ASPhttp://www.emulex.com/downloads/netapp.htmlhttp://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://http//SUPPORT.QLOGIC.COM/SUPPORT/DRIVERS_SOFTWARE.ASPhttp://www.emulex.com/downloads/netapp.htmlhttp://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/


37/118

fcp config adapter up

adapteris the storage system adapter directly connected to the host.

For more information, see the fcp man page or Data ONTAP Commands: Manual Page

Reference, Volume 1for your version of Data ONTAP.

Configuring iSCSI initiators and HBAsFor configurations using iSCSI, you must either download and install an iSCSI software initiator or

install an iSCSI HBA, or both

An iSCSI software initiator uses the Windows host CPU for most processing and Ethernet network

interface cards (NICs) or TCP/IP offload engine (TOE) cards for network connectivity. An iSCSI

HBA offloads most iSCSI processing to the HBA card, which also provides network connectivity.

The iSCSI software initiator typically provides excellent performance. In fact, an iSCSI softwareinitiator provides better performance than an iSCSI HBA in most configurations. The iSCSI initiator

software for Windows is available from Microsoft at no charge. In some cases, you can even SAN

boot a host with an iSCSI software initiator and a supported NIC.

iSCSI HBAs are best used for SAN booting. An iSCSI HBA implements SAN booting just like an

FC HBA. When booting from an iSCSI HBA, it is recommended that you use an iSCSI software

initiator to access your data LUNs.

Next topics

iSCSI software initiator optionson page 37

Downloading the iSCSI software initiatoron page 38

Installing the iSCSI Initiator softwareon page 39

Installing the iSCSI HBA on page 39

Options for iSCSI sessions and error recovery levelson page 41

Options for using CHAP with iSCSI Initiatorson page 41

Using RADIUS for iSCSI authenticationon page 42

iSCSI software initiator optionsSelect the appropriate iSCSI software initiator for your host configuration.

The following is a list of operating systems and their iSCSI software initiator options.

Windows Server

2003

Download and install the iSCSI software initiator

Windows Server

2008

The iSCSI initiator is built into the operating system. The iSCSI Initiator

Properties dialog is available from Administrative Tools.

Windows Server

2008 R2

The iSCSI initiator is built into the operating system. The iSCSI Initiator

Properties dialog is available from Administrative Tools.



38/118

Windows XP guest

systems on Hyper-

V

For guest systems on Hyper-V virtual machines that access storage directly

(not as a virtual hard disk mapped to the parent system), download and

install the iSCSI software initiator. You cannot select the Microsoft MPIO

Multipathing Support for iSCSI option; Microsoft does not support MPIO

with Windows XP. Note that a Windows XP iSCSI connection to NetApp

storage is supported only on Hyper-V virtual machines.

Windows Vista

guest systems on

Hyper-V


(not as a virtual hard disk mapped to the parent system), the iSCSI initiator is

built into the operating system. The iSCSI Initiator Properties dialog is

available from Administrative Tools. Note that a Windows Vista iSCSI

connection to NetApp storage is supported only on Hyper-V virtual

machines.

SUSE Linux

Enterprise Server

guest systems onHyper-V


(not as a virtual hard disk mapped to the parent system), use an iSCSI

initiator solution on a Hyper-V guest that is supported for standalonehardware. A supported version of Linux Host Utilities is required.

Linux guest

systems on Virtual

Server 2005

For guest systems on Virtual Server 2005 virtual machines that access

storage directly (not as a virtual hard disk mapped to the parent system), use

an iSCSI initiator solution on a Virtual Server 2005 guest that is supported

for standalone hardware. A supported version of Linux Host Utilities is

required.

Note: If you want to use an iSCSI HBA on Windows Server 2003 hosts to access the storage

system, you must download and install the iSCSI initiator service.

Related tasks


Downloading the iSCSI software initiatorTo download the iSCSI initiator, complete the following steps.

About this task

If you are using iSCSI software boot, you need a special boot-enabled version of the iSCSI software

initiator.

Steps

1. Go to the Microsoft Web site at http://www.microsoft.com/.

2. ClickDownloads & Trials.

3. ClickDownload Center.

4. Keep the default setting of All Downloads. In the Search box, type



39/118

iSCSI Initiator

and then clickGo.

5. Select the supported Initiator version you want to install.

6. Click the download link for the CPU type in your Windows host. You might also choose to

download the Release Notesand Users Guidefor the iSCSI Initiator from this Web page.

7. ClickSave to save the installation file to a local directory on your Windows host.

Result

The initiator installation program is saved to the Windows host.

Related concepts

About SAN bootingon page 30

Installing the iSCSI Initiator softwareOn the Windows host, complete the following steps to install the iSCSI Initiator.

Before you begin

You must have downloaded the appropriate iSCSI initiator installer to the Windows host.

Steps

1. Open the local directory to which you downloaded the iSCSI Initiator software.

2. Run the installation program by double-clicking the icon.

3. When prompted to select installation options, select Initiator Service and Software Initiator.

4. For all multipathing solutions except Veritas, select the Microsoft MPIO Multipathing Support

for iSCSI check box, regardless of whether you are using MPIO or not. For the Veritas

multipathing, clear this check box.

Multipathing is not available for Windows XP and Windows Vista.

5. Follow the prompts to complete the installation.

Installing the iSCSI HBAIf your configuration uses an iSCSI HBA, you must make sure that the HBA is installed and

configured correctly.

Before you begin

If you use an iSCSI HBA on Windows Server 2003 hosts, you also need to install the Microsoft

iSCSI initiator service. Follow the instructions in Installing an iSCSI software initiator on page 29

to install the software initiator. If you are using only the iSCSI HBA, you can clear the iSCSI



40/118

Initiator check box when installing the initiator package. The initiator service is built into Windows

Server 2008 and Windows Server 2008 R2.

About this task

You can optionally boot your Windows host from a storage system LUN using a supported HBA.

Steps

1. Install one or more supported iSCSI host bus adapters according to the instructions provided by

the HBA vendor.

2. Obtain the supported HBA drivers and management utilities and install them according to the


Drivers for QLogic iSCSI HBA devices can be found here: http://support.qlogic.com/support/

drivers_software.asp

3. Manually set the required QLogic iSCSI HBA settings.

a. Start the SANsurfer program on the Windows host and select the iSCSI HBA. See the

SANsurfer online Help for more information.

b. Specify an IP address for each HBA port.

c. Set the Connection KeepAliveTO value to 180.

d. Enable ARP Redirect.

e. Set the iSCSI node name of all iSCSI HBA ports to the same name as shown in the iSCSI

initiator GUI on the Windows host.

f. Save the HBA settings and reboot the Windows host.

4. Connect the iSCSI HBA to your Ethernet switches or directly to the storage system. Avoid

routing if possible.

5. Using the iSCSI initiator GUI, configure the iSCSI target addresses of your storage system. If you

are using more than one path, explicitly select the initiator and target for each path when you log

on.

After you finish

If you are SAN booting from an iSCSI HBA, you must also manually set the boot BIOS on the HBA.

Related concepts

SAN Bootingon page 95

Related references

Configuring QLogic iSCSI HBA boot BIOS settingson page 107



41/118

Options for iSCSI sessions and error recovery levelsThe defaults allowed by Data ONTAP are one TCP/IP connection per iSCSI session and an error

recovery level of 0.

You can optionally enable multiple connections per session and error recovery level 1 or 2 by settingData ONTAP option values. Regardless of the settings, you can always use error recovery level 0 and

single-connection sessions. For more information, see the chapter about managing the iSCSI network

in the Data ONTAP Block Access Management Guide for iSCSI and FC.

The iSCSI initiator does not automatically create multiple sessions. You must explicitly create each

session using the iSCSI Initiator GUI.

Options for using CHAP with iSCSI InitiatorsYou can use one-way or mutual (bidirectional) authentication with the challenge handshake

authentication protocol (CHAP).

For one-way CHAP, the target only authenticates the initiator. For mutual CHAP, the initiator also

authenticates the target.

The iSCSI Initiator sets strict limits on the length of both the initiators and targets CHAP

passwords. For Windows Server 2003, see the readme file on the host (C:\Windows\iSCSI

\readme.txt) for more information. For Windows Server 2008 or Windows Server 2008 R2, see the

Manage iSCSI Security topic in Help.

There are two types of CHAP user names and passwords. These types indicate the direction of

authentication, relative to the storage system:

Inbound The storage system authenticates the iSCSI Initiator. Inbound settings are required if

you are using CHAP authentication.

Outbound The iSCSI Initiator authenticates the storage system using CHAP. Outbound values are

used only with mutual CHAP.

You specify the iSCSI Initiator CHAP settings using the Microsoft iSCSI Initiator GUI on the host.

ClickAdvanced on the GUI Discovery tab to specify inbound values for each storage system when

you add a target portal. ClickSecret on the General tab to specify the outbound value (mutual

CHAP only).

By default, the iSCSI Initiator uses its iSCSI node name as its CHAP user name.Always use ASCII text passwords; do not use hexadecimal passwords. For mutual (bidirectional)

CHAP, the inbound and outbound passwords cannot be the same.



42/118

Using RADIUS for iSCSI authenticationYou can optionally use a RADIUS (Remote Authentication Dial-in User Service) server to centrally

manage passwords for iSCSI authentication. Using RADIUS simplifies password management,

increases security, and offloads authentication processing from storage systems.Support for RADIUS is available starting with Data ONTAP 8.0 for the iSCSI target and Windows

Server 2008 or Windows Server 2008 R2 for the iSCSI initiator.

You can configure either one-way authentication (the target authenticates the initiator), or mutual

authentication (the initiator also authenticates the target).

There are three parts to enabling RADIUS authentication for iSCSI initiators:

Set up a RADIUS server

Configure the storage system to use RADIUS

Configure iSCSI initiators to use RADIUS

Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 include a RADIUS

server. For information about configuring this RADIUS server, see the Windows online Help.

For information about configuring the storage system to use RADIUS, see the Block Access

Management Guide for iSCSI and FCfor your version of Data ONTAP.

Next topics

Configuring iSCSI initiators for one-way authentication using RADIUSon page 42

Configuring iSCSI initiators for mutual authentication using RADIUSon page 43

Configuring iSCSI initiators for one-way authentication using RADIUS

One-way authentication means the target verifies the identity of the initiator; the initiator does not

verify the identity of the target. To use one-way RADIUS authentication, you must configure the

Windows Server 2008 or Windows Server 2008 R2 iSCSI software initiator to use the RADIUS

server.

Set up the RADIUS server and configure the storage system before configuring the iSCSI initiator to

use RADIUS.

Steps

1. On the Windows Server 2008 or Windows Server 2008 R2 host, clickStart > Administrative

Tools > iSCSI Initiator to open the Windows iSCSI Initiator Properties dialog.

2. On the Targets tab, select an iSCSI target and clickLog on > Advanced.

3. Select the CHAP logon information, Use RADIUS to generate authentication credentials,

and Use RADIUS to authenticate target credentials check boxes.



43/118

Related tasks

Configuring iSCSI initiators for mutual authentication using RADIUSon page 43

Configuring iSCSI initiators for mutual authentication using RADIUS

Mutual authentication means the target verifies the identity of the initiator, and the initiator verifiesthe identity of the target. To use mutual RADIUS authentication, you must configure the Windows

Server 2008 or Windows Server 2008 R2 iSCSI software initiator to use the RADIUS server.

Set up the RADIUS server and configure the storage system before configuring the iSCSI initiator to

use RADIUS.

Steps

1. On the Windows Server 2008 or Windows Server 2008 R2 host, clickStart > Administrative

Tools > iSCSI Initiator to open the Windows iSCSI Initiator Properties dialog.

2. On the RADIUS tab, clickAdd and specify the IP address of the RADIUS server.

You can optionally add additional RADIUS servers.

3. ClickRADIUS and enter the shared secret for the RADIUS server.

The 26-character shared secret should be the same value as is used in the RADIUS client for this

initiator.

4. On the Discovery tab, clickAdd Portal.

5. Enter the IP address of the iSCSI target port on the storage system, and then clickAdvanced.

6. Select the CHAP logon information check box, and then enter the CHAP user name and target

secret.

These values must match the outbound user name and password specified on the storage system.

7. Select the Use RADIUS to generate authentication credentials and Perform mutual

authentication check boxes, then clickOK.

8. On the Targets tab, select the iSCSI target and clickLog on. Optionally select the

Automatically restore this connection when the computer starts and Enable multi-path

check boxes.

9. ClickAdvanced.

10. In the Local adapter field, select Microsoft iSCSI Initiator. Select the desired IP addresses for

Source IP and Target portal.

11. Select the CHAP logon information check box, and then enter the CHAP user name and target

secret.

Use the same values you entered for the Discovery tab.

12. Select the Use RADIUS to generate authentication credentials and Perform mutual

authentication check boxes, then clickOK.



44/118

13. ClickOK twice to close the Windows iSCSI Initiator Properties dialog.

Related tasks

Configuring iSCSI initiators for one-way authentication using RADIUSon page 42

Installing multipath I/O softwareYou must have multipathing set up if your Windows host has more than one path to the storage

system.

The MPIO software presents a single disk to the operating system for all paths, and a device-specific

module (DSM) manages path failover. Without MPIO software, the operating system could see each

path as a separate disk, which can lead to data corruption.

On a Windows system, there are two main components to any MPIO solution: the Windows MPIO

components and a DSM.

MPIO is supported for Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2

systems. MPIO is not supported for Windows XP and Windows Vista running in a Hyper- V virtual

machine.

When you select MPIO support, the Windows Host Utilities installs the Microsoft MPIO components

on Windows Server 2003 or enables the included MPIO feature of Windows Server 2008 and

Windows Server 2008 R2.

You then need to install a supported DSM. Choices include the Data ONTAP DSM for Windows

MPIO, the Veritas DMP DSM, the Microsoft iSCSI DSM (part of th

Date post:	07-Apr-2018
Category:	Documents
Upload:	tim-gudilin
View:	231 times
Download:	0 times

Win Hu 5.3 Install

Documents