Skip to main content

Provision SAN storage

Contributors netapp-aherbin netapp-dbagwell netapp-aaron-holt netapp-revathid netapp-ahibbard
PDFs

This procedure creates new LUNs on an existing storage VM which already has the FC or iSCSI protocol configured.

About this task

This procedure applies to FAS, AFF, and current ASA systems. If you have an ASA r2 system (ASA A1K, ASA A70, or ASA A90), follow these steps to provision your storage. ASA r2 systems provide a simplified ONTAP experience specific to SAN-only customers.

If you need to create a new storage VM and configure the FC or iSCSI protocol, see Configure an SVM for FC or Configure an SVM for iSCSI.

If the FC license is not enabled, the LIFs and SVMs appear to be online but the operational status is down.

LUNs appear to your host as disk devices.

Note Asymmetric logical unit access (ALUA) is always enabled during LUN creation. You cannot change the ALUA setting.

You must use single initiator zoning for all of the FC LIFs in the SVM to host the initiators.

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.

Example 1. Steps
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).

To complete this task using System Manager Classic (available with 9.7 and earlier) refer to iSCSI configuration for Red Hat Enterprise Linux

Steps

  1. Install the appropriate SAN host utilities on your host.

  2. In System Manager, click Storage > LUNs and then click Add.

  3. Enter the required information to create the LUN.

  4. 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

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

  2. Discover LUNs on your host.

    For VMware vSphere, use Virtual Storage Console (VSC) to discover and initialize your LUNs.

  3. Initialize the LUNs and optionally, create file systems.

  4. 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.

  1. 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           -

  2. If you do not have a license for FC or iSCSI, use the license add command.

    license add -license-code <your_license_code>

  3. 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

  4. 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>

    NetApp 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.

  5. Verify that your LIFs have been created and that their operational status is online:

    network interface show -vserver <svm_name> <lif_name>

  6. 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.

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

  7. Create your igroups:

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

  8. Map your LUNs to igroups:

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

  9. Verify that your LUNs are configured correctly:

    lun show -vserver <svm_name>

  10. Optionally, Create a port set and bind to an igroup.

  11. Follow steps in your host documentation for enabling block access on your specific hosts.

  12. Use the Host Utilities to complete the FC or iSCSI mapping and to discover your LUNs on the host.

Related information