Skip to main content

Map an NVMe namespace to a subsystem

Contributors netapp-aherbin netapp-ahibbard netapp-aaron-holt

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

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>
    Cli

    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.

  3. Map the namespace to the subsystem:

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

    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
    Cli

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