Beginning with ONTAP 9.8, when you provision storage, QoS is enabled by default. You can disable QoS or choose a custom QoS policy during the provisioning process or at a later time.

ONTAP System Manager

Create LUNs to provide storage for a SAN host using the FC or iSCSI protocol with ONTAP System Manager (9.7 and later).

Steps

Install the appropriate SAN host utilities on your host.
In ONTAP System Manager, click Storage > LUNs and then click Add.
Enter the required information to create the LUN.

You can click More Options to do any of the following, depending upon your version of ONTAP.

Option	Available beginning with
Assign QoS policy to LUNs instead of parent volume More Options > Storage and Optimization Select Performance Service Level. To apply the QoS policy to individual LUNs instead of the entire volume, select Apply these performance limits enforcements to each LUN. By default, performance limits are applied at the volume level.	ONTAP 9.10.1
Create a new initiator group using existing initiator groups More Options > HOST INFORMATION Select New initiator group using existing initiator groups. NOTE: The OS type for an igroup containing other igroups cannot be changed after it has been created.	ONTAP 9.9.1
Add a description to your igroup or host initiator The description serves as an alias for the igroup or host initiator. More Options > HOST INFORMATION	ONTAP 9.9.1
Create your LUN on an existing volume By default, a new LUN is created in a new volume. More Options > Add LUNs Select Group related LUNs.	ONTAP 9.9.1
Disable QoS or choose a custom QoS policy More Options > Storage and Optimization Select Performance Service Level. NOTE: In ONTAP 9.9.1 and later, if you select a custom QoS policy, you can also select manual placement on a specified local tier.	ONTAP 9.8

Option

Available beginning with

Assign QoS policy to LUNs instead of parent volume
- More Options > Storage and Optimization
- Select Performance Service Level.
- To apply the QoS policy to individual LUNs instead of the entire volume, select Apply these performance limits enforcements to each LUN.
  
  By default, performance limits are applied at the volume level.

ONTAP 9.10.1

Create a new initiator group using existing initiator groups
- More Options > HOST INFORMATION
- Select New initiator group using existing initiator groups.
  
  NOTE: The OS type for an igroup containing other igroups cannot be changed after it has been created.

ONTAP 9.9.1

Add a description to your igroup or host initiator

The description serves as an alias for the igroup or host initiator.
- More Options > HOST INFORMATION

ONTAP 9.9.1

Create your LUN on an existing volume

By default, a new LUN is created in a new volume.
- More Options > Add LUNs
- Select Group related LUNs.

ONTAP 9.9.1

Disable QoS or choose a custom QoS policy
- More Options > Storage and Optimization
- Select Performance Service Level.
  
  NOTE: In ONTAP 9.9.1 and later, if you select a custom QoS policy, you can also select manual placement on a specified local tier.

ONTAP 9.8

For FC, zone your FC switches by WWPN. Use one zone per initiator and include all target ports in each zone.
Discover LUNs on your host.

For VMware vSphere, use Virtual Storage Console (VSC) to discover and initialize your LUNs.
Initialize the LUNs and optionally, create file systems.
Verify that the host can write and read data on the LUN.

CLI

Create LUNs to provide storage for a SAN host using the FC or iSCSI protocol with the ONTAP CLI.

Steps

Verify that you have a license for FC or iSCSI.

system license show

Package           Type    Description           Expiration
 ----------------- ------- --------------------- --------------------
 Base              site    Cluster Base License  -
 NFS               site    NFS License           -
 CIFS              site    CIFS License          -
 iSCSI             site    iSCSI License         -
 FCP               site    FCP License           -

If you do not have a license for FC or iSCSI, use the license add command.
```
license add -license-code <your_license_code>
```

Enable your protocol service on the SVM:

For iSCSI:

vserver iscsi create -vserver <svm_name> -target-alias <svm_name>

For FC:

vserver fcp create -vserver <svm_name> -status-admin up

Create two LIFs for the SVMs on each node:
```
network interface create -vserver <svm_name> -lif <lif_name> -role data -data-protocol <iscsi|fc> -home-node <node_name> -home-port <port_name> -address <ip_address> -netmask <netmask>
```
This product supports a minimum of one iSCSI or FC LIF per node for each SVM serving data. However, two LIFS per node are required for redundancy. For iSCSI, it is recommended that you configure a minimum of two LIFs per node in separate Ethernet networks.
Verify that your LIFs have been created and that their operational status is online:
```
network interface show -vserver <svm_name> <lif_name>
```
Create your LUNs:
```
lun create -vserver <svm_name> -volume <volume_name> -lun <lun_name> -size <lun_size> -ostype linux -space-reserve <enabled|disabled>
```
Your LUN name cannot exceed 255 characters and cannot contain spaces.

The NVFAIL option is automatically enabled when a LUN is created in a volume.

Create your igroups:

igroup create -vserver <svm_name> -igroup <igroup_name> -protocol <fcp|iscsi|mixed> -ostype linux -initiator <initiator_name>

Map your LUNs to igroups:

lun mapping create -vserver <svm__name> -volume <volume_name> -lun <lun_name> -igroup <igroup_name>

Verify that your LUNs are configured correctly:
```
lun show -vserver <svm_name>
```
Optionally, Create a port set and bind to an igroup.
Follow steps in your host documentation for enabling block access on your specific hosts.
Use the Host Utilities to complete the FC or iSCSI mapping and to discover your LUNs on the host.

Related information