Vous êtes sur la page 1sur 72

iSCSI Host Attach Kit 2.

0 for Windows®
Installation and Setup Guide

Network Appliance, Inc.


495 East Java Drive
Sunnyvale, CA 94089 USA
Telephone: +1 (408) 822-6000
Fax: +1 (408) 822-4501
Support telephone: +1 (888) 4-NETAPP
Documentation comments: doccomments@netapp.com
Information Web: http://www.netapp.com

Part number 210-00626


February 2004
Copyright and trademark information

Copyright Copyright © 1994–2004 Network Appliance, Inc. All rights reserved. Printed in the U.S.A.
information Portions © 1998–2001 The OpenSSL Project. All rights reserved.

No part of this book 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 system—without prior written permission of the copyright owner.

Portions of this product are derived from the Berkeley Net2 release and the 4.4-Lite-2 release, which
are copyrighted and publicly distributed by The Regents of the University of California.

Copyright © 1980–1995 The Regents of the University of California. All rights reserved.

Portions of this product are derived from NetBSD, which is copyrighted by Carnegie Mellon
University.

Copyright © 1994, 1995 Carnegie Mellon University. All rights reserved. Author Chris G.
Demetriou.

Permission to use, copy, modify, and distribute this software and its documentation is hereby granted,
provided that both the copyright notice and its permission notice appear in all copies of the software,
derivative works or modified versions, and any portions thereof, and that both notices appear in
supporting documentation.

CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS “AS IS” CONDITION.
CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES
WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.

Software derived from copyrighted material of The Regents of the University of California and
Carnegie Mellon University is subject to the following license and disclaimer:

Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notices, this list of conditions,
and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notices, this list of
conditions, and the following disclaimer in the documentation and/or other materials provided
with the distribution.

3. All advertising materials mentioning features or use of this software must display the following
acknowledgment:
This product includes software developed by the University of California, Berkeley and its
contributors.

4. Neither the name of the University nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

ii Copyright and trademark information


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.

Portions of the software were created by Netscape Communications Corp.

The contents of those portions are subject to the Netscape Public License Version 1.0 (the “License”);
you may not use those portions except in compliance with the License. You may obtain a copy of the
License at http://www.mozilla.org/NPL/.

Software distributed under the License is distributed on an “AS IS” basis, WITHOUT WARRANTY
OF ANY KIND, either express or implied. See the License for the specific language governing rights
and limitations under the License.

The Original Code is Mozilla Communicator client code, released March 31, 1998.

The Initial Developer of the Original Code is Netscape Communications Corp. Portions created by
Netscape are Copyright © 1998 Netscape Communications Corp. All rights reserved.

This software contains materials from third parties licensed to Network Appliance Inc. which is
sublicensed, and not sold, and title to such material is not passed to the end user. All rights reserved
by the licensors. You shall not sublicense or permit timesharing, rental, facility management or
service bureau usage of the Software.

Portions developed by the Apache Software Foundation (http://www.apache.org/). Copyright © 1999


The Apache Software Foundation.

Portions Copyright © 1995–1998, Jean-loup Gailly and Mark Adler

Portions Copyright © 2001, Sitraka Inc.

Portions Copyright © 2001, iAnywhere Solutions

Portions Copyright © 2001, i-net software GmbH

Portions of this product are derived from version 2.4.11 of the libxml2 library, which is copyrighted
by the World Wide Web Consortium.

Network Appliance modified the libxml2 software on December 6, 2001, to enable it to compile
cleanly on Windows, Solaris, and Linux. The changes have been sent to the maintainers of libxml2.
The unmodified libxml2 software can be downloaded from http://www.xmlsoft.org/.

Copyright © 1994–2002 World Wide Web Consortium, (Massachusetts Institute of Technology,


Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights
Reserved. http://www.w3.org/Consortium/Legal/

Software derived from copyrighted material of the World Wide Web Consortium is subject to the
following license and disclaimer:

Permission to use, copy, modify, and distribute this software and its documentation, with or without
modification, for any purpose and without fee or royalty is hereby granted, provided that you include
the following on ALL copies of the software and documentation or portions thereof, including
modifications, that you make:

1. The full text of this NOTICE in a location viewable to users of the redistributed or derivative
work.

2. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none
exist, a short notice of the following form (hypertext is preferred, text is permitted) should be
used within the body of any redistributed or derivative code: "Copyright © [$date-of-software]

Copyright and trademark information iii


World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de
Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.
http://www.w3.org/Consortium/Legal/"

3. Notice of any changes or modifications to the W3C files, including the date changes were made.
(We recommend you provide URLs to the location from which the code is derived.)

THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT


HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR
DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
TRADEMARKS OR OTHER RIGHTS.

COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
DOCUMENTATION.

The name and trademarks of copyright holders may NOT be used in advertising or publicity
pertaining to the software without specific, written prior permission. Title to copyright in this
software and any associated documentation will at all times remain with copyright holders.

Software derived from copyrighted material of Network Appliance, Inc. is subject to the following
license and disclaimer:

Network Appliance reserves the right to change any products described herein at any time, and
without notice. Network Appliance assumes no responsibility or liability arising from the use of
products described herein, except as expressly agreed to in writing by Network Appliance. The use
and purchase of this product do not convey a license under any patent rights, trademark rights, or any
other intellectual property rights of Network Appliance.

The product described in this manual may be protected by one or more U.S. 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).

Trademark NetApp, the Network Appliance design, NetApp–the Network Appliance Company, FAServer,
information NearStore, NetCache, and WAFL are registered trademarks of Network Appliance, Inc. in the United
States and other countries. Network Appliance is a registered trademark of Network Appliance, Inc.
in Monaco and a trademark of Network Appliance, Inc. in the United States and Canada. SnapCopy is
a registered trademark of Network Appliance, Inc. in the European Union and a trademark of
Network Appliance, Inc. in the United States. DataFabric, FilerView, SecureShare, SnapManager,
SnapMirror, and SnapRestore are registered trademarks of Network Appliance, Inc. in the United
States. Data ONTAP and Snapshot are trademarks of Network Appliance, Inc. in the United States
and other countries. ApplianceWatch, BareMetal, Center-to-Edge, ContentDirector, gFiler,
MultiStore, SecureAdmin, Serving Data by Design, Smart SAN, SnapCache, SnapDrive, SnapMover,
SnapVault, vFiler, and Web Filer are trademarks of Network Appliance, Inc. in the United States.

Apple is a registered trademark and QuickTime is a trademark of Apple Computer, Inc. in the United
States and/or other countries.

Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in


the United States and/or other countries.

iv Copyright and trademark information


RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, and RealVideo are registered
trademarks and RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the
United States and/or other countries.

All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.

Network Appliance is a licensee of the CompactFlash and CF Logo trademarks.

Network Appliance NetCache is certified RealSystem compatible.

Copyright and trademark information v


vi Copyright and trademark information
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix

Chapter 1 Overview of the iSCSI Host. . . . . . . . . . . . . . . . . . . . . . . . . . . 1


Understanding how NetApp implements an iSCSI network . . . . . . . . . . . 2

Chapter 2 Configuring the Filer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7


Starting the iSCSI service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configuring iSNS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Configuring CHAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3 Installing the HBA in the Host . . . . . . . . . . . . . . . . . . . . . . . . 13


Preparing to install the HBA . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installing the HBA in the host . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4 Installing and Configuring the Host Software. . . . . . . . . . . . . . . . 19


Obtaining the HBA driver software . . . . . . . . . . . . . . . . . . . . . . 20
Upgrading the HBA firmware and software . . . . . . . . . . . . . . . . . . 23
Installing the iSCSI Host Attach Kit 2.0 software for the first time . . . . . . 30
Configuring the HBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5 Creating and Managing LUNs . . . . . . . . . . . . . . . . . . . . . . . . 39


Creating LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Making new LUNs visible as disks on the host . . . . . . . . . . . . . . . . 50
Managing LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

vii
viii Table of Contents
Preface

About this guide This guide describes how to install and configure a NetApp®-supplied iSCSI
host bus adapter (HBA) on a Microsoft® Windows® host. The host accesses data
on Network Appliance™ storage appliances (filers or NearStore) that run
NetApp Data ONTAP™ software with the iSCSI protocol licensed.

Audience This guide is for system installers and administrators who are familiar with the
Windows operating system. It assumes that you are familiar with how to
configure and administer a filer and use the filer-licensed iSCSI protocol to store
and retrieve data on a filer.

Terminology This guide uses the following terms:


◆ LUN (Logical Unit Number) refers to a logical unit of storage identified by a
number.
◆ LUN ID refers to the numerical identifier for a LUN.
◆ Filer refers to a NetApp storage appliance that is licensed for the iSCSI
protocol.
◆ Type refers to pressing one or more keys on the keyboard.
◆ Enter refers to pressing one or more keys and then pressing the Enter key.

Command You can enter filer commands on either the system console or from any host
conventions system that can access the filer through a Telnet session.

Keyboard When describing key combinations, this guide uses the hyphen (-) to separate
conventions individual keys. For example, “Ctrl-D” means pressing the “Control” and “D”
keys simultaneously. Also, this guide uses the term “Enter” to refer to the key
that generates a carriage return, although the key is named “Return” on some
keyboards.

Preface ix
Typographic The following table describes typographic conventions used in this guide.
conventions
Convention Type of information

Italic type Words or characters that require special attention.


Placeholders for information you must supply. For
example, if the guide says to enter the arp -d
hostname command, you enter the characters
“arp -d” followed by the actual name of the host.
Book titles in cross-references.

Monospaced font Command and daemon names.


Information displayed on the system console or
other computer monitors.
The contents of files.

Bold monospaced Words or characters you type. What you type is


font always shown in lowercase letters, unless you
must type it in uppercase letters.

Special messages This guide contains special messages that are described as follows:

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

Caution
A caution contains instructions that you must follow to avoid damage to the
equipment, a system crash, or loss of data.

WARNING
A warning contains instructions that you must follow to avoid personal
injury.

x Preface
Overview of the iSCSI Host 1
About this chapter This chapter provides an overview of the iSCSI network and describes how a
Windows host communicates with a NetApp filer.

Chapter 1: Overview of the iSCSI Host 1


Understanding how NetApp implements an iSCSI network

What the iSCSI The iSCSI protocol is a licensed service on the filer that enables you to transfer
protocol is block data to hosts using the SCSI protocol over TCP/IP.

How NetApp In an iSCSI network, filers are targets that have storage target devices, which are
implements the referred to as LUNs (Logical Unit Numbers). A host with an iSCSI Host Bus
iSCSI network Adapter (HBA) and driver uses the iSCSI protocol to access LUNs on a filer
running Data ONTAP™ software. Filers and hosts can be connected directly to
each other, or they can be connected to TCP/IP switches with Ethernet cable and
use a TCP/IP network for all connectivity.

The filer does not use a hardware iSCSI HBA to implement the iSCSI service.
The iSCSI protocol on the filer is implemented using a software driver that is
integrated into Data ONTAP as a virtual adapter called the iSCSI Software Target
(iswt). This virtual adapter is preinstalled on the filer. It provides two logical iswt
adapters: iswta and iswtb. The iswta adapter controls all iSCSI traffic for the filer.
If the filer is in a cluster, the iswtb adapter is dedicated to iSCSI traffic for the
partner filer. If a failover occurs and the filer is operating in takeover mode, the
iswtb adapter becomes active.

On the filer, you can select which interface is used for iSCSI traffic. For example,
you can specify that iSCSI traffic runs exclusively over GbE interfaces and not
the integrated 10/100 interface. Or you can specify that iSCSI traffic runs
exclusively on an interface connected to a specific dedicated iSCSI network. You
use the iswt interface command to control which network interface is
used for iSCSI connectivity.

Note
If you want to use the internal 10/100 connection on the filer for iSCSI traffic,
NetApp strongly recommends that you set the Ethernet NIC, the host HBA, and
the switch (if one is being used) to full duplex.

Understanding Each iSCSI entity on a network has a unique iSCSI node name. This is a logical
iSCSI node names name that is not linked to an IP address. Only initiators (hosts) and targets (filers)
are iSCSI entities. Switches and routers are TCP/IP devices only and do not have
iSCSI node names.

2 Understanding how NetApp implements an iSCSI network


Format for iSCSI node names: An iSCSI node name has the following
format:

iqn.yyyy-mm.backward_naming_authority:unique_device_name
yyyy-mm is the month and year in which the naming authority acquired the
domain name.
backward_naming_authority is the reverse domain name of the entity
responsible for naming this device. An example reverse domain name is
com.netapp.
unique_device_name is a free-format unique name for this device assigned
by the naming authority.

The following example shows the iSCSI node name for an HBA in an initiator
that is an application server:

iqn.1987-06.com.initvendor1:sn2345

Default node name for the filer: The filer’s default node name is based on
the NetApp reverse domain name and the filer’s system ID. The following
example shows the default node name for a filer with the system ID 123456789:

iqn.1992-08.com.netapp:sn.123456789

On the filer, you use the iscsi nodename command to display the filer’s
node name. You can use the filer’s iscsi nodename command to change the
filer’s node name. If you change the node name, the new node name must be
unique. For detailed information about managing filer node names, see the Data
ONTAP Block Access Administration Guide for iSCSI.

How node names iSCSI node names are used for the following purposes.
are used
Creating initiator igroups: The host’s node name is used to create initiator
groups (igroups). An igroup is a collection of node names of initiators in an
iSCSI network that you specify when you create the igroup. When you map a
LUN on a filer to the igroup, you grant all the initiators in that group access to
that LUN. If a host’s node name is not in an igroup that is mapped to a LUN, that
host does not have access to the LUN. This masks access to the LUN.

Uniquely identifying a filer’s iswt target ports: The node name of the
filer is used to uniquely identify each iswt target port on a filer.

Chapter 1: Overview of the iSCSI Host 3


Understanding The Challenge Handshake Authentication Protocol (CHAP) enables
CHAP authenticated communication between iSCSI initiators and targets. When you
authentication use CHAP authentication, you define CHAP user names and passwords on both
the initiator and the filer.

During the initial stage of an iSCSI session, the initiator sends a login request to
the filer to begin the session. The login request includes the initiator’s CHAP
user name and algorithm. The filer responds with a CHAP challenge. The
initiator provides a CHAP response. The filer verifies the response and
authenticates the initiator. The CHAP password is used to compute the response.

On the filer, you use the iscsi security command to define which initiators
can access the filer. You also define whether a permitted initiator requires a
CHAP authentication to access the filer and the filer’s CHAP user names and
passwords.

On the host, you use the Intel PROSet for IP Storage tool to configure the
initiator’s CHAP user name and password.

Understanding The Internet Storage Name Service (iSNS) is a protocol that enables automated
iSNS discovery and management of iSCSI devices on an IP storage network. An iSNS
server maintains information about active iSCSI devices on the network,
including their IP addresses, iSCSI node names, and portal groups.

If you have an iSNS server on your network, you use the iscsi isns
command configure the filer to register with the iSNS server. The filer
automatically registers its IP address, node name, and portal groups with the
iSNS server when the iSCSI service is started. The initiator can query the iSNS
server to discover the filer as a target device.
On the host, you use the Intel PROSet for IP Storage tool to configure the
initiator to discover iSCSI targets by querying an iSNS server.

If you do not have an iSNS server on your network, you must manually configure
each target to be visible to the host.

Where to go for The following table describes documents on NetApp’s NOW Web site with the
more information most current information about initiator and filer system requirements and
additional documentation.

4 Understanding how NetApp implements an iSCSI network


If you want... Go to...

The most current system FCP/iSCSI Configuration Guide online version at


requirements for the host http://now.netapp.com/NOW/knowledge/docs/docs.shtml

The supported filer models for FCP/iSCSI Configuration Guide online version at
Data ONTAP licensed with http://now.netapp.com/NOW/knowledge/docs/docs.shtml
iSCSI
System Configuration Guide for your version of Data ONTAP online
version at http://now.netapp.com

Information about how to The following documents in the Data ONTAP Information Library at
configure and manage the iSCSI http://now.netapp.com/NOW/knowledge/docs/ontap/
service on the filer ontap_index.shtml
Data ONTAP Block Access Administration Guide
Data ONTAP Release Notes

Information about managing the Intel®-provided HBA and driver documentation. You can find this
iSCSI initiator documentation on your Host Attach Kit CD-ROM.

Chapter 1: Overview of the iSCSI Host 5


6 Understanding how NetApp implements an iSCSI network
Configuring the Filer 2
About this chapter This chapter describes the tasks you must complete to configure the filer and
prepare it to be accessed by an iSCSI initiator:
◆ Ensure that the iSCSI service is licensed and started.
◆ If you have an iSNS server and want the initiator to discover the filer as a
target device, register the filer with the iSNS server.
◆ If you want to use CHAP authentication, configure a CHAP user name and
password.

Topics in this This chapter discusses the following topics:


chapter ◆ “Starting the iSCSI service” on page 8
◆ “Configuring iSNS” on page 9
◆ “Configuring CHAP” on page 10

Chapter 2: Configuring the Filer 7


Starting the iSCSI service

Licensing and To license and start the iSCSI service, complete the following steps.
starting the iSCSI
service Step Action

1 On the filer console, enter the following command:


license

Result: The filer console displays the codes for licensed protocols.

2 If... Then...

The console displays a Proceed to Step 3.


license code for the iSCSI
service

The console does not 1. Enter the following command to


display a license code for license the iSCSI service:
the iSCSI service license add code
code is the iSCSI license code
provided to you by Network
Appliance.

2. Proceed to Step 3.

3 Enter the following command to start the iSCSI service:


iscsi start

Example:
filer_hq > iscsi start
iSCSI service started
Tue Sep 17 16:25:51 EDT [iscsi.adapter.online:notice]:
ISCSI: iswta, Adapter brought online.

Result: The iSCSI service is started and is persistent across reboots.

8 Starting the iSCSI service


Configuring iSNS

When to configure You configure iSNS only when you have an iSNS server on your network and
iSNS you want the initiator to query the iSNS server to discover the filer as an iSCSI
target.

Configuring the filer To configure the filer to register with the iSNS server, complete the following
to register with an steps.
iSNS server
Step Action

1 On the filer console, enter the following command to identify the


iSNS server that the filer registers with:
iscsi isns config -i ip_addr
ip_addr is the IP address of the iSNS server.

2 Enter the following command:


iscsi isns start

Result: The iSNS service is started and the filer registers with the
iSNS server.

Note
iSNS registration is persistent across reboots if the iSCSI service is
running and iSNS is started.

Reregistering the You must reregister the filer with the iSNS server when you change the filer’s
filer with the iSNS iSCSI configuration information, such as its node name or portal information.
server
To reregister the filer, complete the following step.

Step Action

1 On the filer console, enter the following command:


iscsi isns update

Chapter 2: Configuring the Filer 9


Configuring CHAP

When to configure You configure CHAP only if you want to implement CHAP authentication
CHAP between the initiator and the filer.

Types of CHAP user You define two types of CHAP user names and passwords on the filer:
names and ◆ Inbound—The filer authenticates the initiator. Inbound settings are required
passwords if you are using CHAP authentication.
The filer’s inbound user name and password must be the same as the host’s
Username and Secret. You define these host CHAP properties using the Intel
PROSet for IP Storage HBA configuration tool.
◆ Outbound—You use outbound settings to enable mutual authentication. In
mutual authentication, the filer first authenticates the initiator, then the
initiator authenticates the filer.
The filer’s outbound password must be the same as the host’s CHAP shared
secret. The CHAP shared secret is a global initiator property. You define it in
the initiator’s CHAP Properties > Set CHAP Shared Secret window.

10 Configuring CHAP
Configuring CHAP To configure CHAP on the filer, complete the following step.
on the filer
Step Action

1 Enter the following command:


iscsi security add -i initiator -s CHAP -p inpassword
-n inname [-o outpassword -m outname]
initiator is the initiator name in the iSCSI node name format. Use the
initiator node name you recorded in Step 9 of “Configuring the
HBA” on page 32.
inpassword is the inbound password the filer uses to authenticate the
initiator.
inname is the inbound user name the filer uses to authenticate the
initiator.
outpassword is the outbound password the initiator uses to
authenticate the filer for mutual authentication.
outname is the outbound user name for mutual authentication. You
can enter any value for outname. The initiator ignores the outbound
user name and does not require a value for this setting.

2 Record the inbound and outbound CHAP user names and passwords.
The filer user names and passwords are required when you configure
initiator CHAP properties.

Chapter 2: Configuring the Filer 11


12 Configuring CHAP
Installing the HBA in the Host 3
About this chapter This chapter describes the system requirements, host system backup procedures,
and procedures for installing the HBA in the host.

Topics in this This chapter discusses the following topics:


chapter ◆ “Preparing to install the HBA” on page 14
◆ “Installing the HBA in the host” on page 16

Chapter 3: Installing the HBA in the Host 13


Preparing to install the HBA

Tasks for Prepare to install the HBA by performing the following tasks:
preparation ◆ Verify your system meets minimum requirements
◆ Download and install the Microsoft iSCSI service
◆ Back up the host system

Verifying system The online FCP/iSCSI Configuration Guide lists the most current and complete
requirements system requirements, including required driver and firmware versions and
supported versions of Data ONTAP.

Before you install the HBA, verify that your system meets minimum
requirements by checking the FCP/iSCSI Configuration Guide at
http://now.netapp.com/NOW/knowledge/docs/docs.shtml.

14 Preparing to install the HBA


Downloading and The iSCSI Windows Host Attach Kit 2.0 requires that the Microsoft iSCSI
installing the Service is installed on the host.
Microsoft iSCSI
Service For information about obtaining the Microsoft iSCSI Service, go to
http://support.intel.com and search for “Microsoft iSCSI initiator service”.

Backing up the host To back up your system, complete the following step.
system
Step Action

1 Using the appropriate tools, back up the following:


◆ Data on the local drives attached to your host
◆ The boot and system drives on your host
◆ The system registry on your host

Chapter 3: Installing the HBA in the Host 15


Installing the HBA in the host

Installing the HBA To install an HBA in the host, complete the following steps, using the illustration
for reference.

Step Action

1 Use the appropriate commands to shut down the host and its
peripherals.

2 Turn off the host and its peripherals.

16 Installing the HBA in the host


Step Action

3 Put on the antistatic wrist strap and attach the grounding leash to the
host chassis.

Caution
The host and HBA use electronic components that are sensitive to
static electricity. Static discharge from your clothing or other fixtures
around you can damage these components. Wear an antistatic wrist
strap and attach the grounding leash so that you are appropriately
grounded before touching any electronic components.

4 Remove the computer cover from the host.

5 Identify the appropriate 32-bit or 64-bit PCI bus slot in which you
can install one HBA for a direct-attached or single-path host
connection.

6 Remove the blank faceplate from the empty 32-bit or 64-bit PCI bus
slot.

7 Take the HBA out of the antistatic bag.

8 Holding the HBA by its top edge, with the faceplate near the back of
the host, lower the HBA into the slot until its connector edge meets
the grooves in the expansion slot.
The faceplate of the HBA should be in position against the back
panel, and should cover the endplate slot on the back panel.

9 Press carefully on the top edge of the HBA until the edge connector
is seated in the expansion slot.

10 Replace the faceplate screw to secure the HBA to the back panel.

11 Replace the computer cover and tighten the case screws.

Caution
Do not turn on the host, or, if applicable, its peripherals, until you
complete the cabling for the system.

Chapter 3: Installing the HBA in the Host 17


Step Action

12 Connect cables according to your network requirements:


◆ 1000BASE-T or 100BASE-TX—Use a Category 5, twisted-pair
cable (four twisted-pair wiring).
◆ 10BASE-T—Use Category 3, 4, or 5 cable (twisted-pair wiring).

13 Proceed to Chapter 4, “Installing and Configuring the Host


Software,” on page 19.

18 Installing the HBA in the host


Installing and Configuring the Host Software 4
About this chapter This chapter describes the procedures for installing the HBA driver software
package on the host.

Topics in this This chapter discusses the following topics:


chapter ◆ “Obtaining the HBA driver software” on page 20
◆ “Upgrading the HBA firmware and software” on page 23
◆ “Installing the iSCSI Host Attach Kit 2.0 software for the first time” on
page 30
◆ “Configuring the HBA” on page 32

Chapter 4: Installing and Configuring the Host Software 19


Obtaining the HBA driver software

Contents of The software package is a self-extracting archive that contains the following
software package HBA kit components:
◆ Intel® PRO/1000 T IP Storage Adapter—HBA driver
◆ HBA firmware
◆ Intel PROSet for IP Storage—HBA driver management tool

Locating the To locate the software package, complete the following step.
software package
Step Action

1 If you obtain the software


from... Then...

The NetApp NOW site Go to “Obtaining the software


from NOW” on page 20.

CD-ROM in the media package Go to “Uncompressing and


for your NetApp Host Attach extracting the files” on page 21.
Kit for iSCSI on Windows

Obtaining the To download the software package from the NOW site, complete the following
software from NOW steps.

Step Action

1 Use a Web browser to log in to the NOW site at


http://now.netapp.com.
◆ Type your user name and password.
◆ From the Select Start Page list box, click Service and Support.
◆ Click the Login button.

2 Click Download Software.

20 Obtaining the HBA driver software


Step Action

3 In the iSCSI Host Attach Kit product row of the Software Download
table, select Windows in the Select Platform list box.

4 Click Go!

5 Follow the prompts to reach the Software Download page.

6 Download the netapp_windows_iscsi_2_0.exe software file and save


it to disk, for example, the c:\temp directory.

7 Go to “Uncompressing and extracting the files” on page 21.

Uncompressing and To uncompress the file and extract the software, complete the following steps.
extracting the files
Step Action

1 If you are
uncompressing... Then...

Software obtained from 1. Change to the directory (or browse


the NOW site to the location) where you
downloaded the
netapp_windows_iscsi_2_0.exe
file.
For example, change to the c:\temp
directory.

2. Double-click
netapp_windows_iscsi_2_0.exe.

Software from the CD- 1. Insert the CD-ROM into the


ROM CD-ROM drive.

2. Double-click
netapp_windows_iscsi_2_0.exe.

2 In the WinZip Self-Extractor window, choose the default temporary


directory (folder) to unzip the file, or browse to a different temporary
directory.

Chapter 4: Installing and Configuring the Host Software 21


Step Action

3 Click the Unzip button to extract the files to the designated


temporary directory.

Result: The extracted software (package contents) are placed in the


designated temporary directory.

4 If... Then...

You are upgrading from Proceed to “Upgrading the HBA


a previous host attach firmware and software” on page 23
kit.

You are installing the Proceed to “Upgrading the HBA


software for the first firmware and software” on page 23.
time.

22 Obtaining the HBA driver software


Upgrading the HBA firmware and software

Before performing Before you upgrade HBA firmware and software, record your current
the upgrade configuration information in the following table. After the upgrade, you might
have to reenter these values the PROSet configuration software because your
configuration information might not be saved during the upgrade.

Configuration information Your values

HBA IP address

HBA subnet mask

Gateway

Target IP address

Target node name

Overview of The upgrade procedure you follow depends on the version of the iSCSI Host
upgrade Attach Kit for Windows that is currently installed on your host.
procedures
Versions 1.0 and 1.0R1: The firmware versions included in the 1.0 and 1.0R1
attach kits do not support firmware upgrade using a flash utility. You must
upgrade to an interim attach kit release (1.1) to obtain the flash utility and the
firmware and drivers that support it. The following steps provide an overview of
the upgrade:
◆ Obtain the iSCSI Host Attach Kit 1.1 for Windows from the NetApp on the
Web (NOW) site.
◆ Install the iSCSI Host Attach Kit 1.1 for Windows.
◆ Upgrade the HBA firmware using the Intel firmware upgrade utility.
◆ Upgrade from version 1.1 of the attach kit to version 2.0.

For detailed procedures, see “Upgrading from versions 1.0 or 1.0R1” on page 24.

Version 1.1: Version 1.1 of the attach kit includes the firmware and drivers that
support upgrade using the flash utility. You can upgrade directly from version 1.1
to version 2.0. The following steps are an overview of the upgrade procedure:
◆ Use the Intel firmware upgrade utility to upgrade the firmware.

Chapter 4: Installing and Configuring the Host Software 23


◆ Update the driver software.
◆ Update the Intel PROSet for IP Storage Configuration software.

Upgrading from To upgrade from versions 1.0 or 1.0R1 of the attach kit, complete the following
versions 1.0 or tasks.
1.0R1
Obtaining the iSCSI Host Attach Kit 1.1 for Windows: To obtain the
iSCSI Host Attach Kit 1.1 for Windows, complete the following steps.

Step Action

1 Use a Web browser to log in to the NOW site at


http://now.netapp.com.

a. Under the Service and Support heading, click Software


Downloads.

b. Enter your user name and password.

2 Scroll down to the last row of the Software Download table, labeled
To Access a Specific Version.

a. Select iSCSI Host Attach Kit - Windows in the Select


Software list box.

b. Enter 1.1 in the version box.

c. Click Go!

3 At the bottom of the iSCSI Host Attach Kit 1.1 for Windows
Description Page, click Continue.

4 Read and accept the NetApp Customer Software License and the
Intel Software License Agreement.

5 On the iSCSI Host Attach Kit 1.1 for Windows Download Page,
click the installation package link to download the
netapp_windows_iscsi_1_1.exe file and save it to disk, for example,
in the c:\temp directory.

6 Change to the directory (or browse to the location) where you


downloaded the netapp_windows_iscsi_1_1.exe file.
For example, change to the c:\temp directory.

24 Upgrading the HBA firmware and software


Step Action

7 Double-click netapp_windows_iscsi_1_1.exe.

8 In the WinZip Self-Extractor window, choose the default temporary


directory (folder) for the file, or browse to a different temporary
directory.

9 Click the Unzip button to extract the files to the designated


temporary directory.

Result: The extracted package contents are placed in the designated


directory.

Installing the iSCSI Host Attach Kit 1.1 for Windows: To install the
iSCSI Host Attach Kit 1.1 for Windows, complete the following steps.

Step Action

1 Follow the procedure described in Chapter 3, “Installing and


Configuring the HBA Software,” in the Host Bus Adapter
Installation and Setup Guide 1.0 for iSCSI Protocol on Windows.
This document is available from the iSCSI Host Attach Kit 1.1 for
Windows Download Page.

2 After software installation is complete, reboot the host.

Upgrading the HBA firmware: To upgrade the HBA firmware, complete the
following steps.

Step Action

1 Navigate to the directory to which you extracted the host attach kit
software.

2 In the \Firmware\Update\Windows directory, start the flash-3.5.65.x


utility.

Result: The Intel PRO/1000 T IP Flash Update window is


displayed.

Chapter 4: Installing and Configuring the Host Software 25


Step Action

3 Select the HBA you want to update and click Update.

Result: The Flash Update utility updates the firmware on the HBA.

4 Reboot the host.

Result: The firmware is upgraded to version 3.5.65.2.

5 Proceed to “Upgrading from version 1.1” below.

Upgrading from To upgrade from version 1.1 of the attach kit, complete the following steps.
version 1.1
Step Action

1 Navigate to the directory to which you downloaded the iSCSI Host


Attach Kit 2.0 software.

2 In the \Firmware\WindowsFlashUpdate directory, start the


FlashUpdateFrom3.5.6x.exe utility.

3 In the Intel PRO/1000 T IP Flash Update window, click Choose


Firmware Image and select the flash image file from the Firmware
directory.

4 Select the HBA you want to upgrade and click Update.

5 Close the Intel PRO/1000 T IP Flash Update window.

6 Proceed to one of the following sections:


◆ “Windows Server 2003: Upgrading the HBA drivers” on
page 26
◆ “Windows 2000: Upgrading the HBA drivers” on page 27

Windows Server To upgrade the HBA drivers for Windows Server 2003, complete the following
2003: Upgrading the steps.
HBA drivers
Step Action

26 Upgrading the HBA firmware and software


1 Reboot the host.

2 In the Found New Hardware Wizard that appears after the reboot,
select Install from a List or Specific Location and click Next.

3 In the next window of the Found New Hardware wizard, select Don’t
Search, I Will Choose the Driver to Install and click Next.

4 From the next window, click the Have Disk button and locate the
10002k.inf file, in the directory to which you extracted the attach kit
2.0 software from NOW.

5 In the next window of the Found New Hardware wizard, select Intel
PRO/1000 T IP Storage Adapter and click Next.

6 Click Finish when prompted.

7 Install the Intel PROSet for IP Storage Configuration software by


completing the following steps:

a. Navigate to the directory to which you downloaded and


extracted the software.

b. Click autorun.exe.

c. Click Install/Update Configuration Software.

Windows 2000: To upgrade the HBA drivers for Windows 2000, complete the following steps.
Upgrading the HBA
drivers Step Action

1 Reboot the host.

Result: The Found New Hardware Wizard is displayed.

Chapter 4: Installing and Configuring the Host Software 27


Step Action

2 Before continuing configuration with the Found New Hardware


Wizard, search your computer for “oem*.inf” files in the WINNT
directory that contain the text string “is10002K” and delete those
files.

Note
If the .inf files are hidden, you must set them to show so that they
appear when you search for them. To show hidden files, complete the
following steps:

a. Select Folder Options from the Tools menu in Windows


Explorer.

b. Click the View tab.

c. Under Advanced Settings, select the Show hidden files and


folders button.

3 Return to the Found New Hardware Wizard and choose Search for a
Suitable Driver for My Device, then click Next.

4 Specify the location of the is10002K.inf file in the directory to which


you extracted the attach kit 2.0 software, then click Next.

5 Click Next when the wizard locates the driver.

6 When the installation is complete, click Finish.

7 Reboot the host.

8 Install the Intel PROSet for IP Storage Configuration software by


completing the following steps:

a. Navigate to the directory to which you downloaded and


extracted the software.

b. Click autorun.exe.

c. Click Install/Update Configuration Software.

28 Upgrading the HBA firmware and software


Important note When you upgrade to version 2.0 of the Host Attach Kit from a previous release,
about how initiator the driver software assigns a new default node name to the initiator.
node names change
after an upgrade In previous releases of the Host Attach Kit, each initiator (HBA or software) had
a unique initiator node name. For example, if you had a software initiator and the
HBA installed in the same host, each initiator had a different node name.

For version 2.0 of the host attach kit, a host has a single initiator node name. All
the initiators installed in the host use this node name. The node name uses the
following format:

iqn.1991-05.com.microsoft:hostname.domain_name

To prevent the host from losing access to filer LUNs, you must modify the
igroups on the filer to include the new node name. You use the igroup set
command to add or modify initiators in an igroup.

Caution
If you do not update the filer igroups with the new initiator node name, you
cannot access your LUNs after the upgrade.

Chapter 4: Installing and Configuring the Host Software 29


Installing the iSCSI Host Attach Kit 2.0 software for the first time

Installing for To install the HBA software for Windows Server 2003, complete the following
Windows Server steps.
2003
Step Action

1 Reboot the host.

2 In the Found New Hardware Wizard, choose Install from a List or


Specific Location (Advanced) and click Next.

3 In the Found New Hardware Wizard, specify the following and click
Next:
◆ Choose Search for the Best Driver in These Locations.
◆ Check Include This Location in the Search.
◆ In <type your path here>, specify the location of the
is10002k.inf file in the directory to which you extracted the host
attach kit software.

4 When the Found New Hardware Wizard window appears after the
software is installed, click Finish.

5 Install the Intel PROSet for IP Storage Configuration software by


completing the following steps:

a. Navigate to the directory to which you downloaded and


extracted the software.

b. Click autorun.exe.

c. Click Install/Update Configuration Software.

Installing for To install the HBA software for Windows 2000, complete the following steps.
Windows 2000
Note
In this procedure, you use the Found New Hardware wizard to install the
is10002K.inf and nodev.inf files separately.

30 Installing the iSCSI Host Attach Kit 2.0 software for the first time
Step Action

1 Reboot the host.

2 In the Found New Hardware Wizard that is displayed, click Next.

3 In the Found New Hardware Wizard, choose Search for a Suitable


Driver for My Device and click Next.

4 Specify the location of the is10002K.inf file in the directory to which


you extracted the attach kit 2.0 software, then click Next.

5 Click Next after the wizard locates the driver.

Result: The wizard installs the driver and prompts you to click
Finish to complete the installation.

6 Click Finish.

Result: The Found New Hardware Wizard is displayed again.

7 In the Found New Hardware Wizard, choose Search for a Suitable


Driver for My Device and click Next.

8 Specify the location of the nodev.inf file in the directory to which you
extracted the attach kit 2.0 software, then click Next.

9 Click Next after the wizard locates the driver.

Result: The wizard installs the driver and prompts you to click
Finish to complete the installation.

10 Click Finish

11 Reboot the host

12 Install the Intel PROSet for IP Storage Configuration software by


completing the following steps:

a. Navigate to the directory to which you downloaded and


extracted the software.

b. Click autorun.exe.

c. Click Install/Update Configuration Software.

Chapter 4: Installing and Configuring the Host Software 31


Configuring the HBA

Settings you can You use the Intel PROSet for IP Storage tool to configure the following HBA
configure settings:
◆ IP address, network mask, and gateway
◆ Targets the host will access
◆ User names and passwords if you are using CHAP authentication
◆ Link settings

Configuring the To configure the HBA, complete the following steps.


HBA
Step Action

1 From the Windows Start menu, choose Settings > Control Panel >
Intel PROSet for IP Storage.

2 In the Configure Adapter window, click Configure.

3 In the IP Address tab of the Modify Network Settings windows, enter


the following host values:
◆ IP Address
◆ Subnet Mask
◆ Gateway

32 Configuring the HBA


Step Action

4 If... Then...

You are using DHCP Enable DHCP

Note
Ensure that the DHCP server is
configured to issue infinite leases. If
you have a finite lease and the DHCP
server renews your lease with a
different IP address, the HBA becomes
unusable until you reboot or use
PROSet to disable DHCP and then re-
enable it.

You are not using DHCP Disable DHCP.

5 In the Advanced tab of the Modify Network Settings tab, configure


the following link settings:
◆ Frame size—Normal or jumbo.
If you use jumbo frames, you must also enable jumbo frames
when you configure the filer. You use the filer ifconfig
command to set the Maximum Transfer Unit (MTU) size to
9000. The following example sets the MTU size to 9000:
ifconfig interface mtusize 9000
◆ Auto negotiation—Enable or disable.
◆ Duplex—Full or half

Note
If you plan to use the filer’s 10/100 Ethernet interface for iSCSI,
you must disable autonegotiation and set Duplex to full. To
ensure proper connectivity between the host and the filer, you
must use the same link settings for the filer’s Ethernet interfaces.
For switched configuration, you must also use the same link
settings on the switch.

6 In the Modify Network Settings window, click OK.

7 In the Configure Adapter window, click OK.

Chapter 4: Installing and Configuring the Host Software 33


Step Action

8 In the left pane of the PROSet for IP Storage window, click the
Initiator icon.

Result: The Properties tab in the right pane displays the initiator’s
node name. This is the node name used by all hardware and software
initiators installed in the host. The node name uses the following
format:

iqn.1991-05.com.microsoft:hostname.domain_name

Note
NetApp recommends that you use the default name. If you define a
new node name, you must use the iSCSI node name format described
in “Understanding iSCSI node names” on page 2. You must also
modify any existing igroups on the filer to include the new node
name.

9 Record the initiator node name. This node name is required when you
configure igroups on the filer.

Adding targets You must add targets after you configure basic initiator settings. To add targets,
complete the following steps.

Step Action

1 In the left pane of the PROSet for IP Storage window, click the
Initiator icon.

2 In the Properties tab, click Add a Target.

Result: The Add Target window is displayed. If you upgraded from


a previous release and connected to targets, the Add Target window
displays these targets.

34 Configuring the HBA


Step Action

3 If... Then...

The Add Target window does 1. In the Add Target window,


not display a list of targets click Add.

2. Proceed to Step 4.

The Add Target window 1. Select a target and click Next.


displays a list of targets
2. Proceed to Step 5.

Chapter 4: Installing and Configuring the Host Software 35


Step Action

4 If you choose... Then in the Discover iSCSI


targets window...

Discover iSCSI targets by 1. Enter the IP address of the


querying an iSNS server iSNS server.

Note 2. Choose the HBA used to


The filer must be registered connect to the iSNS server.
with the iSNS server
3. Click Next.
according to the procedure
described in “Configuring 4. In the Add Target window,
iSNS” on page 9. Otherwise, select a target and click Next.
the filer is not discovered as
an iSCSI target. 5. If you want to use CHAP,
proceed to Step 5.
If you do not want to use
CHAP, proceed to Chapter 5,
“Creating and Managing
LUNs,” on page 39.

Discover iSCSI targets by 1. Enter the IP address of the


querying a specific target target.

2. If you want to use CHAP,


proceed to Step 5.
If you do not want to use
CHAP, proceed to Chapter 5,
“Creating and Managing
LUNs,” on page 39.

Manually enter the 1. Enter the node name and IP


information for an iSCSI address of the target.
target
2. In the Add Target window,
select the target you just added
and click Next.

3. If you want to use CHAP,


proceed to Step 5. If you do not
want to use CHAP, proceed to
Chapter 5, “Creating and
Managing LUNs,” on page 39.

36 Configuring the HBA


Step Action

5 If you want to use CHAP authentication, configure the following


properties in the Add Target window and then click Next:
◆ Select Check Authenticate the initiator to the target.
◆ In the Username field, enter the filer’s inbound user name, which
you defined using the iscsi security command in
“Configuring CHAP on the filer” on page 11.
◆ In the Secret field, enter the filer’s inbound password, which you
defined using the iscsi security command in
“Configuring CHAP on the filer” on page 11.
◆ If you want to configure mutual authentication, check “Also
require the target to authenticate to the initiator using the
Initiator’s Secret (Mutual CHAP)”.

6 If you configured mutual authentication in Step 5, you must define


the initiator’s password as follows:

a. In the left pane of the PROSet tool, click the initiator icon.

b. Click Set CHAP Properties

c. Enter the initiator’s secret. You must use the outbound


password you defined using the iscsi security
command in “Configuring CHAP on the filer” on page 11.

Chapter 4: Installing and Configuring the Host Software 37


38 Configuring the HBA
Creating and Managing LUNs 5
About this chapter This chapter describes how to create LUNs for iSCSI access on the filer and
manage the LUNs from the host using Windows disk management tools.

This chapter provides quick procedures for creating LUNs and lists some brief
guidelines about snapshots and space reservations. For detailed information
about snapshots and space reservations, and how they affect available space for
LUNs, see Chapter 2, “Creating LUNs and Initiator Groups,” in the Data ONTAP
Block Access Management Guide for iSCSI.

Topics in this This chapter discusses the following topics:


chapter ◆ “Creating LUNs” on page 40
◆ “Making new LUNs visible as disks on the host” on page 50
◆ “Managing LUNs” on page 52

Chapter 5: Creating and Managing LUNs 39


Creating LUNs

Guidelines for The following rules apply to creating LUNs for a Windows host:
creating LUNs ◆ You must create a LUN with an ID of 0. If a LUN with an ID of 0 is not
present, the host does not discover LUNs with IDs higher than seven.
◆ Ensure that LUNs are created at the root of a filer volume or at the root of a
qtree within a volume.
◆ Do not put LUNs in /vol/vol0 (the root volume). This volume contains files
that Data ONTAP uses to administer the filer.
◆ Distribute LUNs across the filer cluster.

Enabling space NetApp strongly recommends that you enable space reservations when creating
reservations LUNs. Data ONTAP enables you to manage space reservations at the qtree, file,
or LUN level. When you enable space reservations, Data ONTAP reserves
enough space on the volume so that writes to the LUN do not fail. For detailed
information about space reservations, see Chapter 2, “Creating LUNs, igroups,
and LUN maps,” in the Data ONTAP Block Access Management Guide for
iSCSI.

Changing snapshot When you create LUNs, NetApp recommends that you change default snapshot
defaults settings as follows:
◆ Set the percentage of snap reserve to 0% for the volume containing the
LUNs.
◆ Turn off the automatic snap schedule.

For detailed information about snapshot defaults and how they affect available
space for LUNs, see Chapter 2, “Creating LUNs, igroups, and LUN maps,” in the
Data ONTAP Block Access Management Guide for iSCSI.

40 Creating LUNs
Methods for You can use the following methods to create LUNs and map them to initiator
creating LUNs groups:
◆ Filer command line—You use the lun setup command to create a LUN
and map it to an initiator group.

Note
You can also use the lun create and lun map commands to create a
LUN and map it to an initiator group. For detailed information about these
commands, see the Data ONTAP 6.4 Block Access Management Guide.

◆ FilerView® Web-based interface—You use the LUN Wizard to create a


LUN and map it to an initiator group.

Prerequisites for You must create volumes or qtrees prior to creating LUNs.
creating LUNs

For detailed For detailed information about creating LUNs, see the following topics:
information ◆ “Creating LUNs with the lun setup command” on page 42
◆ “Creating LUNs with FilerView” on page 48

Chapter 5: Creating and Managing LUNs 41


Creating LUNs
Creating LUNs with the lun setup command

Command for The lun setup command prompts you for information required for creating a
creating LUNs LUN and an initiator group and mapping the LUN to an igroup. When a default
in brackets [ ] is provided, you can press Enter to accept the default.

You can create an initiator group and add the iSCSI node name to it when
prompted. If you already created an initiator group, you can use an existing
initiator group and add the node name to the group.

You can interrupt the lun setup process at any time by pressing Ctrl-C. Any
information that you entered is discarded.

Creating LUNs To create LUNs on the filer using the lun setup command, complete the
following steps.

Step Action

1 On the filer’s command line, enter the following command to create


a LUN:
lun setup

Result: The lun setup command displays the following


instructions. Press Enter to continue or n to terminate the setup:

This setup will take you through the steps needed to


create LUNs and to make them accessible by initiators.
You can type ^C (Control-C) at any time to abort the
setup and no unconfirmed changes will be made to the
system.
Do you want to create a LUN? [y]

2 Enter windows in response to the following prompt:

OS type of LUN (default/solaris/windows) [default]:


windows

42 Creating LUNs
Step Action

3 Specify where the LUN will be located by responding to the next


prompt:
A LUN path must be absolute. A LUN can only reside in a
volume or qtree root. For example, to create a LUN with
the name “lun0” in the qtree root /vol/vol/q0, specify
the path as “/vol/vol1/q0/lun0”.
Enter LUN path:

Example: If you previously created /vol/vol1/ and want to create a


LUN called lun0, you would enter, /vol/vol1/lun0.

Caution
Do not create LUNs in /vol/vol0. This is the root volume used for
filer administration.

Result: lun0 is created in the root of /vol/vol1 if you accept the


configuration information later in this program.

4 Specify whether you want the LUN created with space reservations
enabled by responding to the prompt:

A LUN can be created with or without space reservations


being enabled. Space reservation guarantees that data
writes to that LUN will never fail.
Do you want the LUN to be space reserved? [y]:

Example: Enter

Caution
If you choose n, space reservation is disabled. This might cause
writes to the filer to fail, which can cause data corruption. NetApp
strongly recommends that you enable space reservations.

Chapter 5: Creating and Managing LUNs 43


Step Action

5 Enter the LUN size in response to the following prompt:

Size for a LUN is specified in bytes. You can use single-


character multiplier suffixes: b(sectors), k(KB), m(MB),
g(GB) or t(TB).
Enter LUN size:

Example: An example is 5g, meaning 5 GB of raw disk.

Result: A LUN with the specified size of raw disk is created if the
configuration information is accepted later in this program. The
quantity of usable disk space by the host varies depending on the
host’s operating system and the application using the LUN.

6 Enter a comment or a brief description about the LUN by responding


to the next prompt:

You can add a comment string to describe the contents of


the LUN.
Please type a string (without quotes), or hit ENTER if
you don’t want to supply a comment.
Enter comment string:________

Note
If you press Enter and do not add a comment, you can add a
comment later with the lun comment command. For more
information, see the lun comment man page on the filer.

7 Create or use an existing igroup by responding to the next prompt:

The LUN will be accessible to an initiator group. You can


use an existing group name, or supply a new name to
create a new initiator group. Enter ‘?’ to see existing
initiator group names.
Name of initiator group[]:

Result: If you have already created one or more igroups, you can
enter ? to list them. The last igroup you used appears as the default.
If you press Enter, that igroup will be used.

If you have not created any igroups, enter a name of the igroup you
want to create now.

44 Creating LUNs
Step Action

8 Enter iSCSI at the next prompt to specify the type of initiator


group:
Type of initiator group igroup_name (FCP/iSCSI) [FCP]:
iSCSI

9 Add the iSCSI node names of the hosts that will be in the igroup by
responding to the next prompt:

An iSCSI initiator group is a collection of initiator


node names. Each node name can begin with either ’eui.’
or ’iqn.’ and should be in the following formats:
eui.{EUI-64 address} or iqn.yyyy-mm.{reversed domain
name}:{any string} Eg: iqn.2001-
04.com.acme:storage.tape.sys1.xyz or eui.02004567A425678D
You can separate node names by commas. Enter ’?’ to
display a list of connected initiators. Hit ENTER when
you are done adding node names to this group.
Enter comma separated nodenames: iqn.1989-
03.com.isinit:app1

Note
You can enter ? to view a list of node names or use the node name
that you recorded in Step 9 of “Configuring the HBA” on page 32.

10 Enter windows in response to the next prompt:

OS type of initiator group "igroup_name"


(default/solaris/windows):

Chapter 5: Creating and Managing LUNs 45


Step Action

11 Specify the LUN ID that the host will map to the LUN by responding
to the next prompt:

The LUN will be accessible to all the initiators in the


initiator group. Enter ‘?’ to display LUNs already in use
by one or more initiators in group “windows-igroup1”.

LUN ID at which initiator group “windows-igroup1” sees


“/vol/vol1/lun0” [0]:

Result: If you press Enter to accept the default, Data ONTAP issues
the lowest valid unallocated LUN ID to map it to the initiator,
starting with zero. Alternatively, you can enter any valid number.

Note
Network Appliance recommends that you accept the default value
for the LUN ID.

After you press Enter, the lun setup program displays the information
you entered:
LUN Path : /vol/vol1/q0/lun0
OS Type : windows
Size : 5g (5368709120)
Comment : 5 GB Windows LUN for finance
records
Initiator Group : windows-igroup1
Initiator Group Type : ISCSI
Initiator Group Members : iqn.1991-
05.com.microsoft:lab1.hq.XYZcompany.com
Mapped to LUN-ID : 0

12 Commit the configuration information you entered by responding to


the next prompt:
Do you want to accept this configuration? [y]

Result: If you press Enter to accept the default, the LUNs are
mapped to the specified igroup. All changes are committed to the
system and Ctrl-C cannot undo these changes. The LUN is created
and mapped. If you want to modify the LUN, its mapping, or any of
its attributes, you need to use individual commands or FilerView.

46 Creating LUNs
Step Action

13 Finish or continue creating LUNs by responding to the final prompt.


Enter y to create additional LUNs or enter n to finish and exit the
lun setup script.

Do you want to create another LUN? [n]:

14 Proceed to “Making new LUNs visible as disks on the host” on


page 50.

Chapter 5: Creating and Managing LUNs 47


Creating LUNs
Creating LUNs with FilerView

Creating LUNs with To create LUNs with FilerView, complete the following steps.
the FilerView LUN
Wizard Step Action

1 Open a browser on your host.

2 Enter the DNS-resolvable name or IP address of the filer followed by


/na_admin/ as the location for the URL.

Example: If you have a filer named filerX, enter the following


address in the browser:

http://filerX/na_admin

Result: The Network Appliance Online administrative window is


displayed.

3 Click FilerView.

Result: The user name and password window is displayed.

4 Enter your user name and password, then click the OK button.

Result: The Network Appliance FilerView window is displayed.

5 Click LUNs in the left panel of the FilerView screen.

Result: The management tasks you can perform on LUNs are


displayed.

6 Click Wizard.

Result: The LUN Wizard window appears and explains how to use
it.

7 Click the Next button to continue.

Result: The first window of fields in the LUN Wizard appears.

48 Creating LUNs
Step Action

8 Follow the instructions in the LUN Wizard and enter information in


the appropriate fields.

9 At the LUN Wizard Commit Changes window, review your input. If


everything is correct, click Commit.

Result: The LUN Wizard: Success! window appears and the LUN
you created is mapped to the igroups you specified.

Chapter 5: Creating and Managing LUNs 49


Making new LUNs visible as disks on the host

Making the LUN After you create LUNs you must make them visible to the host. To make the new
visible to the host LUN visible to the host, complete the following steps.

Step Action

1 Right-click My Computer on your desktop and select Manage.

Result: The Computer Management window is displayed.

2 Expand Storage and double-click the Disk Management folder.

Result: The disk information on the host system is displayed.

3 From the Action menu, select Rescan Disks.

Result: All disks on the host are rescanned.

4 From the Action menu, select Refresh.

Result: The screen is refreshed with the latest data.

Note
If you are using Microsoft Terminal Services and the LUN does not appear after you rescan, log
off, reconnect, log on, and return to the Computer Management window to see the new LUNs.

50 Making new LUNs visible as disks on the host


Step Action

5 On the Computer Management window with Storage expanded and the Disk Management folder
open, verify in the lower right pane that the newly created LUN is visible as a disk on the host.
In the following example, Disk 2 represents a newly created LUN.

6 If... Then...

You want to configure the Proceed to “Managing LUNs” on page 52.


LUNs as disks for filesystem
access

You want to manage the Do not partition or format the disk.


LUNs as raw disks
You can manage the LUNs from the DOS command line. Each
new LUN that appears as a disk in the Computer Management
window is managed as a PhysicalDrive on the DOS command
line. For example, Disk 2 is managed as PhysicalDrive2.

Chapter 5: Creating and Managing LUNs 51


Managing LUNs

Options for The new LUNs appear as disks in the Windows disk management utilities on the
managing LUNs host. You can use Windows disk management utilities to do the following:
◆ Create a partition on a basic disk and map it to a drive to organize your data.
◆ Locate a LUN ID for a particular disk.

Partitioning the To view partition the disks, complete the following steps.
disks
Note
Before partitioning a disk, make sure that you rescanned for newly created
LUNs, as described in “Making new LUNs visible as disks on the host” on
page 50.

Step Action

1 Ensure that you are logged in with administrative privileges.

2 Right-click My Computer on your desktop and select Manage.

Result: The Computer Management window is displayed.

3 Expand Storage and double-click the Disk Management folder.

Result: The disk information on the host system is displayed.

52 Managing LUNs
Step Action

4 Locate the disk that corresponds to the LUN you created on the filer. In the following example,
Disk 2 represents a newly created LUN.

Chapter 5: Creating and Managing LUNs 53


Step Action

5 To write a signature on the disk, right-click the Disk information text box (the white box next to
the disk information graphic) and select Write Signature from the menu.

Note
The signature helps the Disk Administrator identify the disk.

Example: In this example, the user right-clicked the Disk 2 information text box and selected
Write Signature from the menu.

Result: The Write Signature window is displayed.

54 Managing LUNs
Step Action

6 In the Write Signature window, select the check box beside each disk on which you want to
write a signature, and then click OK.

Example: In the following example, a signature is written to disks 2 through 8.

Result: The signatures are written and the disks become basic disks, as shown in the Disk
information graphics.

7 To create a partition on a disk, right-click a Disk information box and select Create Partition
from the menu.

Result: The Create Partition Wizard is displayed.

8 In the Create Partition Wizard window, click the Next button to continue.

Result: The Select Partition Type window is displayed.

Chapter 5: Creating and Managing LUNs 55


Step Action

9 In the Select Partition Type window, specify the type of partition to create, and then click the
Next button.

Example:

Result: The Specify Partition Size window is displayed.

10 In the Specify Partition Size window, choose a partition size in the Amount Of Disk Space To
Use check box that is less than or equal to the Maximum disk space, and then click the Next
button.

Result: The Assign Drive Letter or Path window is displayed.

11 In the Assign Drive Letter or Path window, choose whether to assign a drive letter or drive path
to a partition, and then click the Next button.

Result: The Format Partition window is displayed.

56 Managing LUNs
Step Action

12 In the Format Partition window, specify whether and how to format the partition, then click the
Next button.

Example: In the following example, the disk is formatted with the NTFS file system.

Result: The Completing the Create Partition Wizard window is displayed.

Chapter 5: Creating and Managing LUNs 57


Step Action

13 In the Completing the Create Partition Wizard window, verify that the settings you specified are
listed in the list box, then click the Finish button to close the Creation Partition Wizard.

Result: The Disk information graphic is displayed with the new settings.

Example: In the following example, Disk 2 is a basic disk with a primary partition of 298 MB
of disk space. The name of the volume is “New Volume” and it is assigned to drive letter G. The
partition is formatted with the NTFS file system using the default allocation unit size.

Locating a LUN ID To locate a LUN ID for a particular disk, complete the following steps.

Step Action

1 Ensure that you are logged in with administrative privileges.

2 Right-click My Computer on your desktop and select Manage.

Result: The Computer Management window is displayed.

58 Managing LUNs
Step Action

3 In the Computer Management window, expand the Storage view and


select Disk Management.

Result: In the top of the right pane, a list of partitions is displayed.


In the bottom of the right pane, a list of disks is displayed.

4 Locate the disk that you want, right-click the Disk information
graphic (gray rectangular box), and select Properties from the menu.

Result: The Disk Properties window is displayed.

5 In the Disk Properties window on the General tab, locate the Device
Type label.

Result: The LUN ID is listed at the end of the Device Type


description.

Example: In the following example, the LUN ID is 1.

Chapter 5: Creating and Managing LUNs 59


60 Managing LUNs
Index

D iSCSI node names, how used 3


iswt target port, identifying 3
disks
locating a LUN 58
partitioning 52 L
LUN
F creating with FilerView 48
FilerView creating with the lun setup command 42
locating on a disk 58
launching 48
making visible to host 50
managing 52
H rules for creating 40
HBA LUN ID 58
configuring 32 lun setup 42
installing driver software 32 LUNs
host and space reservations 40
backing up 15
P
I partioning disks 52
initiator group, defined 3
installation S
HBA 16
obtaining the software package 20 space reservations
uncompressing the software package 20, 21 recommendations for LUNs 40
iqn node names,creating igroups with 3

Index 61
62 Index