Skip to main content

Configure a storage VM for NVMe

Contributors netapp-aherbin netapp-barbe netapp-dbagwell netapp-ahibbard netapp-thomi
PDFs

If you want to use the NVMe protocol on a node, you must configure your SVM specifically for NVMe.

Before you begin

Your FC or Ethernet adapters must support NVMe. Supported adapters are listed in the NetApp Hardware Universe.

Example 1. Steps
System Manager

Configure an storage VM for NVMe with ONTAP System Manager (9.7 and later).

To configure NVMe on a new storage VM To configure NVMe on an existing storage VM

  1. In System Manager, click Storage > Storage VMs and then click Add.

  2. Enter a name for the storage VM.

  3. Select NVMe for the Access Protocol.

  4. Select Enable NVMe/FC or Enable NVMe/TCP and Save.

  1. In System Manager, click Storage > Storage VMs.

  2. Click on the storage VM you want to configure.

  3. Click on the Settings tab, and then click Actions icon next to the NVMe protocol.

  4. Select Enable NVMe/FC or Enable NVMe/TCP and Save.
CLI

Configure an storage VM for NVMe with the ONTAP CLI.

  1. If you do not want to use an existing SVM, create one:

    vserver create -vserver <SVM_name>

    1. Verify that the SVM is created:

      vserver show

  2. Verify that you have NVMe or TCP capable adapters installed in your cluster:

    For NVMe:

    network fcp adapter show -data-protocols-supported fc-nvme

    For TCP:

    network port show

  3. If you are running ONTAP 9.7 or earlier, remove all protocols from the SVM:

    vserver remove-protocols -vserver <SVM_name> -protocols iscsi,fcp,nfs,cifs,ndmp

    Beginning with ONTAP 9.8, it is not necessary to remove other protocols when adding NVMe.

  4. Add the NVMe protocol to the SVM:

    vserver add-protocols -vserver <SVM_name> -protocols nvme

  5. If you are running ONTAP 9.7 or earlier, verify that NVMe is the only protocol allowed on the SVM:

    vserver show -vserver <SVM_name> -fields allowed-protocols

    NVMe should be the only protocol displayed under the allowed protocols column.

  6. Create the NVMe service:

    vserver nvme create -vserver <SVM_name>

  7. Verify that the NVMe service was created:

    vserver nvme show -vserver <SVM_name>

    The Administrative Status of the SVM should be listed as up.

  8. Create an NVMe/FC LIF:

    • For ONTAP 9.9.1 or earlier, FC:

      network interface create -vserver <SVM_name> -lif <lif_name> -address <ip address> -netmask <netmask_value> -role data -data-protocol fc-nvme -home-node <home_node> -home-port <home_port>

    • For ONTAP 9.10.1 or later, FC or TCP:

      network interface create -vserver <SVM_name> -lif <lif_name> -address <ip address> -netmask <netmask_value> -service-policy <default-data-nvme-tcp | default-data-nvme-fc> -data-protocol <fcp | fc-nvme | nvme-tcp> -home-node <home_node> -home-port <home_port> -status-admin up -failover-policy disabled -firewall-policy data -auto-revert false -failover-group <failover_group> -is-dns-update-enabled false

  9. Create an NVMe/FC LIF on the HA partner node:

    • For ONTAP 9.9.1 or earlier, FC:

      network interface create -vserver <SVM_name> -lif <lif_name> -role data -data-protocol fc-nvme -home-node <home_node> -home-port <home_port>

    • For ONTAP 9.10.1 or later, FC or TCP:

      network interface create -vserver <SVM_name> -lif <lif_name> -service-policy <default-data-nvme-tcp | default-data-nvme-fc> -data-protocol <fcp | fc-nvme | nvme-tcp> -home-node <home_node> -home-port <home_port> -status-admin up -failover-policy disabled -firewall-policy data -auto-revert false -failover-group <failover_group> -is-dns-update-enabled false

  10. Verify the NVMe/FC LIFs were created:

    network interface show -vserver <SVM_name>

  11. Create volume on the same node as the LIF:

    vol create -vserver <SVM_name> -volume <vol_name> -aggregate <aggregate_name> -size <volume_size>

    If a warning message is displayed about the auto efficiency policy, it can be safely ignored.