Skip to main content

Map an NVMe namespace to a subsystem

Contributors netapp-aherbin netapp-lenida netapp-ahibbard netapp-aaron-holt
PDFs

Mapping an NVMe namespace to a subsystem allows data access from your host. You can map an NVMe namespace to a subsystem when you provision storage or you can do it after your storage has been provisioned.

Beginning with ONTAP 9.17.1, if you are using a SnapMirror active sync configuration, you can add an SVM to a host as a proximal vserver while adding the host to an NVMe subsystem. Active-optimized paths for a namespace in an NVMe subsystem are published to a host only from the SVM that is configured as proximal vserver.

Beginning with ONTAP 9.14.1, you can prioritize resource allocation for specific hosts. By default, when a host is added to the NVMe subsystem, it is given regular priority. You can use the ONTAP command line interface (CLI) to manually change the default priority from regular to high. Hosts assigned a high priority are allocated larger I/O queue counts and queue-depths.

Note If you want to give a high priority to a host that was added to a subsystem in ONTAP 9.13.1 or earlier, you can change the host priority.
Before you begin

Your namespace and subsystem should already be created. If you need to create a namespace and subsystem, see Provision NVMe storage.

Map an NVMe namespace

Steps

  1. Obtain the NQN from the host.

  2. Add the host NQN to the subsystem:

    vserver nvme subsystem host add -vserver <SVM_name> -subsystem <subsystem_name> -host-nqn <Host_NQN_:subsystem._subsystem_name>

    If you want to change the default priority of the host from regular to high, use the -priority high option. This option is available beginning with ONTAP 9.14.1. Learn more about vserver nvme subsystem host add in the ONTAP command reference.

    If you want to add an SVM as a proximal-vserver to a host while adding the host to an NVMe subsystem in a SnapMirror active sync configuration, you can use the -proximal-vservers option. This option is available beginning with ONTAP 9.17.1. You can add the source or destination SVM, or both. The SVM in which you are running this command is the default.

  3. Map the namespace to the subsystem:

    vserver nvme subsystem map add -vserver <SVM_name> -subsystem <subsystem_name> -path <path>

    A namespace can only be mapped to a single subsystem. Learn more about vserver nvme subsystem map add in the ONTAP command reference.

  4. Verify that the namespace is mapped to the subsystem:

    vserver nvme namespace show -vserver <SVM_name> -instance

    The subsystem should be listed as the Attached subsystem. Learn more about vserver nvme namespace show in the ONTAP command reference.