lun igroup create
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
Create a new initiator group
Availability: This command is available to cluster and Vserver administrators at the admin privilege level.
Description
This command creates a new initiator group (igroup). Use igroups to control which hosts have access to specific LUNs. When you bind an igroup to a portset, a host in the igroup can access the LUNs only by connecting to the target ports in the portset.
When you create an igroup, you can add multiple existing initiators by specifying them in a list, separating them with commas. Later, you can add or remove initiators from the initiator group. Use the lun igroup add command to add initiators. Use the lun igroup remove command to remove an initiator. Unless the -initiator
option is supplied, no initiators are added to a new igroup.
You can also bind a portset to an initiator when you create an initiator group. You can modify the portset binding of an initiator group by using the lun igroup bind command or the lun igroup unbind command.
The name you assign to an igroup is independent of the name of the host that is used by the host operating system, host files, or Domain Name Service (DNS). If you name an igroup aix1, for example, it is not mapped to the actual IP host name (DNS name) of the host.
Parameters
-vserver <Vserver Name>
- Vserver Name-
Specifies the Vserver.
-igroup <text>
- Igroup Name-
Specifies the name of the new initiator group. An initiator group name is a case-sensitive name that must contain one to 96 characters. Spaces are not allowed.
It might be useful to provide meaningful names for igroups, ones that describe the hosts that can access the LUNs mapped to them. - {
[-protocol {mixed|fcp|iscsi}]
- Protocol -
Specifies if the initiator group protocol is
fcp
,iscsi
, ormixed
. - |
[-f, -fcp <true>]
- FCP -
Specifies FCP as the protocol type of the new igroup.
- |
[-i, -iscsi <true>]
- iSCSI } -
Specifies iSCSI as the protocol type of the new igroup.
-t, -ostype <Initiator Group OS Type>
- OS Type-
Specifies the operating system type for the new initiator group. The operating system type indicates the type of host operating system used by all of the initiators in the igroup. All initiators in an igroup must be of the same operating system type. The operating system types of initiators are
-
solaris
-
windows
-
hpux
-
aix
-
linux
-
netware
-
vmware
-
openvms
-
xen
-
hyper_v
-
[-a, -portset <text>]
- Portset Binding Igroup-
Specifies that a portset is bound to the initiator.
- {
-initiator <text>,…
- Initiators -
Specifies the initiators that are attached to the new initiator group. By default, no initiators are added to the new igroup.
- |
[-child-igroups <text>,…]
- Child Igroups } -
Specifies the child initiator groups that are attached to the new initiator group. The initiator group inherits the initiators of any child igroups. An initiator group can have either initiators or child initiator groups, but not both. Initiator groups can be nested to match host cluster hierarchies. If the host cluster then changes, initiators only need to be updated in the child igroups and the parent igroups inherit the changes.
[-delete-on-unmap {true|false}]
- Delete on Last Unmap-
Specifies if this initiator group will be deleted automatically when no longer a member of a LUN mapping relationship.
[-comment <text>]
- Igroup Comment-
A description for the igroup to create. If the comment string contains white space, it must be enclosed in double quotes. The limit is 254 characters.
Examples
cluster1::> lun igroup create -vserver vs1 -igroup ig1 -protocol mixed -ostype linux -initiator iqn.2001-04.com.example:abc123
Creates initiator group ig1
on Vserver vs1
with a mixed
protocol type on a Linux operating system with the initiator iqn.2001-04.com.example:abc123
.