Instead of using LUN setup, you can use individual commands to create LUNs, create igroups, and map the LUNs to the appropriate igroups.
-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.
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.
-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.
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.
The following command maps /vol/vol1/qtree1/lun3 to the igroup win_host5_group2 at LUN ID 0: