Release notes
Configure a storage VM for NVMe
Suggest changes
-
PDF of this doc site
-
Cluster administration
-
Volume administration
-
Logical storage management with the CLI
-
-
NAS storage management
-
Configure NFS with the CLI
-
Manage NFS with the CLI
-
Manage SMB with the CLI
-
Manage file access using SMB
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-
Collection of separate PDF docs
Creating your file...
If you want to use the NVMe protocol on a node, you must configure your SVM specifically for NVMe.
Your FC or Ethernet adapters must support NVMe. Supported adapters are listed in the NetApp Hardware Universe.
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 |
|---|---|
|
|
Configure an storage VM for NVMe with the ONTAP CLI.
-
If you do not want to use an existing SVM, create one:
vserver create -vserver <SVM_name>Cli-
Verify that the SVM is created:
vserver showCli
-
-
Verify that you have NVMe or TCP capable adapters installed in your cluster:
For NVMe:
network fcp adapter show -data-protocols-supported fc-nvmeCliFor TCP:
network port showCli -
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,ndmpCliBeginning with ONTAP 9.8, it is not necessary to remove other protocols when adding NVMe.
-
Add the NVMe protocol to the SVM:
vserver add-protocols -vserver <SVM_name> -protocols nvmeCli -
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-protocolsCliNVMe should be the only protocol displayed under the
allowed protocolscolumn. -
Create the NVMe service:
vserver nvme create -vserver <SVM_name>Cli -
Verify that the NVMe service was created:
vserver nvme show -vserver <SVM_name>CliThe
Administrative Statusof the SVM should be listed asup. -
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>Cli -
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 falseCli
-
-
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>Cli -
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 falseCli
-
-
Verify the NVMe/FC LIFs were created:
network interface show -vserver <SVM_name>Cli -
Create volume on the same node as the LIF:
vol create -vserver <SVM_name> -volume <vol_name> -aggregate <aggregate_name> -size <volume_size>CliIf a warning message is displayed about the auto efficiency policy, it can be safely ignored.
