Creating LUNs and mapping igroups ( 7 Mode & C - mode )

Setting up LUNs and igroups using individual commands -  ( 7 Mode )

Instead of using LUN setup, you can use individual commands to create LUNs, create igroups, and map the LUNs to the appropriate igroups.

Before you begin

The LUN type must be specified.

About this task

After the LUN is created, you cannot modify the LUN host operating system type.

Note: You can grow a LUN to approximately 10 times its original size. For example, if you create a 10 GB LUN, you can grow that LUN to approximately 100 GB. However, you cannot exceed 16 TB, which is the approximate maximum size of a LUN.

Steps

1. Create a space-reserved LUN by entering the following command on the storage system command line:
   lun create -s size -t ostype lun_path

   -s size indicates the size of the LUN to be created, in bytes by default.

   -t ostype indicates the LUN type. The LUN type refers to the operating system type, which determines the geometry used to store data on the LUN.

   lun_path is the LUN’s path name that includes the volume and qtree.

   
   

   Example

   The following example command creates a 5-GB LUN called /vol/vol2/qtree1/lun3 that is accessible by a Windows host. Space reservation is enabled for the LUN.

   lun create -s 5g -t windows_2008 /vol/vol2/qtree1/lun3
   
2. Create an igroup by entering the following command on the storage system command line:
   igroup create {-i | -f} -t ostype initiator_group [node ...]

   -i specifies that the igroup contains iSCSI node names.

   -f specifies that the igroup contains FCP WWPNs.

   -t ostype indicates the operating system type of the initiator. The values are solaris, Solaris_efi, windows, windows_gpt, windows_2008, hpux, aix, linux, netware, vmware, xen, and hyper_v.

   initiator_group is the name you specify as the name of the igroup.

   node is a list of iSCSI node names or FCP WWPNs, separated by spaces.

   
   

   Example

   iSCSI example:

   igroup create -i -t windows_2008 win_host5_group2 iqn.1991-05.com.microsoft:host5.domain.com

   
   

   FCP example:

   igroup create -f -t aix aix-igroup3 10:00:00:00:0c:2b:cc:92
   
   
3. Map the LUN to an igroup by entering the following command on the storage system command line:
   lun map lun_path initiator_group [lun_id]

   lun_path is the path name of the LUN you created.

   initiator_group is the name of the igroup you created.

   lun_id is the identification number that the initiator uses when the LUN is mapped to it. If you do not enter a number, Data ONTAP generates the next available LUN ID number.

   
   

   Example

   The following command maps /vol/vol1/qtree1/lun3 to the igroup win_host5_group2 at LUN ID 0:

   lun map /vol/vol2/qtree1/lun3 win_host5_group2 0

 

Creating LUNs and mapping igroups ( C - mode )

As part of configuring your SAN environment, you must create LUNs, create your initiator groups (igroups), and map your LUNs to your igroups.

Before you begin

• You must have created your aggregates, volumes, and Storage Virtual Machines (SVMs).
• You must have enabled block access with FC.
• You must have created SAN LIFs on the LUN owning node and the owning node's HA partner.

About this task

When you create a LUN, you must specify the LUN OS type. The actual size of the LUN might vary slightly based on the OS type of the LUN. The LUN OS type cannot be modified after the LUN is created.

The metadata for each LUN requires approximately 64 KB of space in the containing aggregate. When you create a LUN, you must ensure that the containing aggregate has enough space for the LUN's metadata. If the aggregate does not contain enough space for the LUN's metadata, some hosts might not be able to access the LUN. If necessary, you can grow your LUN up to 10 times its original size. For example, if you create a 100-GB LUN, you can grow that LUN to 1,000 GB. You cannot exceed 16 TB, which is the maximum LUN size limit.

ALUA is always enabled during LUN creation. You cannot change the ALUA setting.

Steps

1. Create your LUNs: lun create -vserver vserver_name -volume volume_name -lun lun_name -size lun_size -ostype lun_ostype -space-reserve enabled|disabled
   If your host operating system is Windows 2012, you must use the windows_2008 ostype. Space-reserve is enabled by default. If you want a non-space-reserved LUN, you must set the space-reserve option to disabled.
2. Create your igroups: igroup create -vserver vserver_name -igroup igroup_name -protocol fcp|iscsi -ostype lun_ostype -initiator initiator_name
   If your host operating system is Windows 2012, you must use the windows_2008 ostype.
3. Map your LUNs to igroups: lun mapping create -vserver vserver_name -volume volume_name -lun lun_name -igroup igroup_name
4. Verify that your LUNs are configured correctly: lun show -vserver vserver_name