The lun setup program prompts you for information needed for creating a LUN and an initiator group, and for mapping the LUN to the initiator group. When a default is provided, you can press Enter to accept the default.
If you did not create volumes and qtrees to store LUNs in prior to running the lun setup program, you must terminate the program and create volumes and qtrees, if you want to use them.
If you did not create initiator groups, you can create them during the lun setup program.
To run the lun setup program, complete the following steps. The answers given are an example of creating LUNs using FCP in a Solaris environment.
| 1 | On the filer command line, enter the following command. If you press Enter, to select y, the lun setup program provides instructions and prompts you to enter your values, as shown in the remaining steps. If you press n, the program terminates. lun setup ResultThe lun setup program displays the following instructions: 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 (default/solaris/windows) [default]: Examplesolaris If you press Enter to select default, the contents of the LUN are not specified. Typing solaris indicates that the LUN will store a Solaris raw disk in a single-slice partition. Typing windows indicates that the LUN will store a raw disk device in a single-partition Windows disk. |
| 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: ExampleIf you previously created /vol/vol1/, you would enter /vol/vol1/lun0. Caution Resultlun0 is created in the root of /vol/vol1 if the configuration information is accepted later in this program. |
| 4 | Specify whether you want the LUN created with space reservations enabled. A LUN can be created with or without space reservations being enabled. Do you want the LUN to be space reserved? [y]: ExamplePress Enter to accept the default. |
| 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: Example5g ResultA LUN with 5 GB of raw disk space is created if the configuration information is accepted 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: Example5 GB Solaris LUN for finance records If you do not want to provide a comment at this time, press Enter. You can add a comment later with the lun comment command or a description by using FilerView. |
| 7 |
Create an initiator group 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[]: |
Example 1:Result 1If you did not create any initiator groups yet, the following message is displayed: No existing initiator groups Name of initiator group[]: Result 2If you already created one or more initiator groups, they are displayed. If you created two initiator groups, solaris-igroup1 and solaris-igroup2, they appear as follows: Name of initiator group[]: ? Existing initiator groups: solaris-igroup1 solaris-igroup2 Name of initiator group[solaris-igroup1]: Press Enter to accept the default for the last initiator group used; otherwise, enter the name of the initiator group that contains the initiator you want to allow access to the LUN you are creating. When you enter the name of an existing initiator group, it is displayed, along with the WWPNs it contains, as shown in the following message: solaris-igroup1 10:00:00:00:c9:2c:43:a0 10:00:00:00:c9:2c:46:60 The LUN will be accessible to all initiators in the initiator group. Enter `?' to display the LUNs already in use by one or more initiators in group "solaris-igroup1". |
|
Example 2ResultThe initiator group solaris-igroup3 is created. Note |
|
| 8 | Specify which protocol will be used by the host in the initiator group by responding to the next prompt. Press Enter to accept the default. Type of initiator group solaris-igroup3 (FCP/iSCSI)[FCP]: ResultThe initiator unique identifiers (FCP WWPNs) in this initiator group use the FCP protocol. |
| 9 | Add the unique identifiers (iSCSI node names or FCP WWPNs) of the hosts that will be in the initiator group by responding to the next prompt: A Fibre Channel Protocol (FCP) initiator group is a collection of initiator port names. Each port name (WWPN) is 16 hexadecimal digits, separated (only) by optional colon (:) characters. You can separate port names by commas. Enter `?' to display a list of connected initiators. Hit ENTER when you are done adding port names to this group. |
Example 1ResultThe following output is a sample of what is displayed. Initiators connected on adapter 4a Portname Group 10:00:00:00:c9:2b:cc:51 10:00:00:00:c9:2b:dd:62 10:00:00:00:c9:2b:ee:5d Adapter 4b is running on behalf of the partner. Initiators connected on adapter 5a: None connected. Enter comma separated portnames: |
|
Example 210:00:00:c9:2b:cc:51 ResultThe initiator identified by this WWPN is added to the initiator group that was specified in Step 8. You are prompted for more portnames until you press Enter. Note |
|
| 10 |
Specify the operating system type that will be accessing the LUN by responding to the next prompt: OS type of initiator group "solaris-igroup3" (default/solaris/windows) [default]: |
| 11 | Specify the LUN ID that the host will map to the LUN by responding to the next prompt. Press Enter to accept the default. 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 "solaris-igroup3". LUN ID at which initiator group "solaris-igroup3" sees "/vol/vol1/lun0" [0]: ResultIf 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. See the HBA installation and setup guide for your host for information about valid LUN ID numbers. Note After you press Enter, the lun setup program displays the information you entered: LUN Path : /vol/vol1/q0/lun0 OS Type : default Size : 5g (5368709120) Comment : 5 GB Solaris LUN for finance records Initiator Group : solaris-igroup3 Initiator Group Type : FCP Initiator Group Members : 10:00:00:00:c9:2b:cc:51 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] ResultIf you type y, the LUNs are mapped to the specified initiator group. 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. See Chapter 3, Managing LUNs. |
| 13 | Either continue creating LUNs, or terminate the program by responding to the next prompt. Press Enter to terminate or type y to continue: Do you want to create another LUN? [n] |
Copyright © 1994-2003, Network Appliance, Inc. All rights
reserved.
Part No. 210-00338
File: c2reqs5.htm
Last updated: 01/17/03 17:40:29