The commands in the following table occur in a logical sequence for creating LUNs and igroups for the first time. However, you can use the commands in any order, or you can skip a command if you already have the information that a particular command displays.
For more information about all of the options for these commands, see the online man pages. For information about how to view man pages, see Command-line administration.
|
Display the node names of iSCSI initiators connected to the storage system |
iscsi initiator show Sample resultInitiators connected: TSIH TPGroup Initiator 64 1 iqn.1991-05.com.microsoft:host5.domain.com / 40:01:37:00:06:00 66 1 iqn.1991-05.com.microsoft:host6.domain.com / 40:01:37:00:00:00 |
|
Display the WWPNs of FCP initiators connected to the storage system |
fcp show initiator Sample resultInitiators connected on adapter 7a: Portname Group 10:00:00:00:c9:39:4d:82 50:06:0b:00:00:11:35:62 10:00:00:00:c9:34:05:0c 10:00:00:00:c9:2f:89:41 10:00:00:00:c9:2d:56:5f Initiators connected on adapter 7b: Portname Group 10:00:00:00:c9:2f:89:41 10:00:00:00:c9:2d:56:5f 10:00:00:00:c9:39:4d:82 50:06:0b:00:00:11:35:62 10:00:00:00:c9:34:05:0c |
|
Determine which iSCSI hosts are associated with the initiator node names |
To determine the iSCSI node name associated with a host, use the command or method provided by the initiator software. For example, the Windows software initiator applet lists the node name on the General tab or Initiator Settings tab, depending on version. Linux systems typically store the node name in the /etc/initiatorname.iscsi file. For more information, see the iSCSI Host Support Kit or Attach Kit for your host, or the documentation provided by the iSCSI initiator or HBA vendor. |
|
For information about how to determine which WWPN is associated with a host, see How hosts are identified. | |
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: default, solaris, windows, hpux, aix,linux, netware, or vmware. For information about specifying the ostype of an igroup, see About igroups. 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. iSCSI example
igroup create -i -t windows win_host5_group2 FCP example | |
lun create -s size -t ostype lun_path -s indicates the size of the LUN to be created, in bytes by default. For information about LUN size, see The size of the LUN. -t ostype indicates the operating system type that determines the geometry used to store data on the LUN. For information about specifying the ostype of the LUN, see The host operating system type. lun_path is the LUN's path name that includes the volume and qtree. Examplelun create -s 5g -t windows /vol/vol2/qtree1/lun3 ResultA 5-GB LUN called /vol/vol2/qtree1/lun3 is accessible by a Windows host. Space reservation is enabled for the LUN. | |
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 1lun map /vol/vol2/qtree1/lun3 win_host5_group2 0 ResultData ONTAP maps /vol/vol1/qtree1/lun3 to the igroup win_host5_group2 at LUN ID 0. Example 2lun map /vol/vol2/lun4 aix-igroup0 ResultData ONTAP assigns the next lowest valid LUN ID to map the LUN to the igroup. After the command in this example is entered, Data ONTAP displays the following message: lun map: auto-assigned aix-igroup0=0 | |
lun show -v -v provides additional information, such as the comment string, serial number, and LUN mapping. Examplelun show -v Sample result/vol/vol1/qtree1/lun3 4g (4294967296) (r/w, online, mapped) Serial#: 0dCfh3bgaBTU Share: none Multiprotocol Type: aix Maps: aix-igroup0=0 | |
lun show -m -m provides mapping information in a tabular format. Sample resultLUN path Mapped to LUN ID Protocol ----------------------------------------------------------------- /vol/tpcc_disks/ctrl_0 aix_cluster 0 FCP /vol/tpcc_disks/ctrl_1 aix_cluster 1 FCP /vol/tpcc_disks/crash1 aix_cluster 2 FCP /vol/tpcc_disks/crash2 aix_cluster 3 FCP /vol/tpcc_disks/cust_0 aix_cluster 4 FCP /vol/tpcc_disks/cust_1 aix_cluster 5 FCP /vol/tpcc_disks/cust_2 aix_cluster 6 FCP | |
|
Determine the maximum possible size of a LUN in a volume or qtree |
lun maxsize vol-path vol-path is the path to the volume or qtree in which you want to create the LUN. ResultThe lun maxsize command displays the maximum possible size of a LUN in the volume or qtree, depending on the LUN type and geometry. It also shows the maximum size possible for each LUN type with or without Snapshot copies. Sample resultlun maxsize /vol/lunvol Space available for a LUN of type: solaris, aix, hpux, linux, or image Without snapshot reserve: 184.9g (198508019712) With snapshot reserve: 89.5g (96051658752) Space available for a LUN of type: windows Without snapshot reserve: 184.9g (198525358080) With snapshot reserve: 89.5g (96054819840) |
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01094_B0
File: c4cr-f14.htm
Last updated: 08-Dec-2005 13:25:25