Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Creating LUNs with the lun setup program

What the lun setup program does  Top

The lun setup program prompts you for information needed for creating a LUN and an igroup, and for mapping the LUN to the igroup. When a default is provided in brackets in the prompt, you can press Enter to accept it.

Prerequisites for running the lun setup program  Top

If you did not create volumes to store LUNs in prior to running the lun setup program, you must terminate the program and create volumes. If you want to use qtrees, you must also create them before running the lun setup program.

Running the lun setup program  Top

To run the lun setup program, complete the following steps. The answers given are an example of creating LUNs using iSCSI in a Windows environment.

Step

Action

1

On the filer command line, enter the following command.

lun setup

Result

The lun setup program displays the following instructions. Press Enter to continue or n to terminate the program.

  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

Specify the operating system that will be accessing the LUN by responding to the next prompt:

OS type of LUN (image/solaris/windows/hpux/aix/linux) [image]:

Example

windows

For information about specifying the ostype of the LUN, see The host operating system type.

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

f 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.

5

Specify the size of the LUN by responding to the next 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

5g

Result

A LUN with 5 GB of raw disk space is created if you accept the configuration information later in this program. The amount of usable disk space by the host varies, depending on the operating system type and the application using the LUN.

6

Create 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:

Example

5 GB Windows LUN for finance records

If you choose not to provide a comment at this time, you can add a comment later with the lun comment command or a description by using FilerView.

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. For information about naming an igroup, see The name of the igroup.

8

Specify which protocol will be used by the initiator in the igroup by responding to the next prompt:

Type of initiator group windows-igroup2 (FCP/iSCSI)[FCP]: iscsi

Result

The initiators in this igroup use the iSCSI protocol.

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.{reserved domain
    name}:{any string}.
    Eg. iqn.2001-04.com.acme:storage.tape.sys1.xyz or eui.02004567A25678D
    You can separate node names by commas. Enter `?' to display a list of
    connected initiators. Hit ENTER when you are done adding port names to this
    group. 
Enter comma separated nodenames:

Result

If you want to list the iSCSI node names, enter ? to list them. When you enter a node name, it is added to the igroup you specified in Step 7.

Note
To determine which node name is associated with a host, use the vendor-supplied commands or methods you downloaded from the iSCSI host initiator support kit on NetApp's NOW web site, or from the CD-ROM in the iSCSI Host Attach Kit for Windows.

10

Specify the operating system type initiators in the igroup use to access LUNs by responding to the next prompt:

The initiator group has an associated OS type. The following are
currently supported: solaris, windows, hpux, aix, linux, or default
OS type of initiator group "windows-igroup1" [windows]:

If the default is the correct os type, press Enter; otherwise, type the appropriate os type. In this example, it is windows.

For information about specifying the ostype of an igroup, see About igroups.

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. For information about valid LUN IDs for your host initiator, see the documentation provided with your iSCSI host Initiator Support Kit or with your SAN Host Attach Kit for iSCSI Protocol on your host.

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.

13

Either continue creating LUNs or terminate the program by responding to the next prompt:

Do you want to create another LUN? [n]

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments