Skip to main content
NetApp Knowledge Base

NVMe Namespace Does Not Support Selective LUN Mapping in ONTAP

  1. Last updated
  2. Save as PDF
Views:
67
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

  • NetApp ONTAP 9.5 and later
  • All Flash FAS (AFF) systems
  • NVMe-oF (NVMe/FC, NVMe/TCP) protocols
  • VMware ESXi hosts

Answer

  • This is expected behavior. ONTAP does not support Selective LUN Mapping (SLM) for NVMe namespaces. All NVMe data LIFs zoned to a host are presented as available paths for each NVMe namespace.
  • Unlike SCSI/FC protocols, SLM is not available or required for NVMe, as NVMe pathing and performance rely on queue-pair parallelism rather than path count.

  • Explanation
    • ONTAP intentionally limits NVMe data LIFs to 2 per SVM per node to control overall path scale.
    • All NVMe LIFs zoned to the host are visible as active paths for the namespace.
    • NVMe performance is not impacted by fewer paths; high IOPS are achieved through NVMe queue parallelism.
    • This is not a bug or misconfiguration. This behavior is by design and not a software issue.
  • Best Practices to Manage Path Count
    • Zone only the minimum required NVMe LIFs to each ESXi host (ideally 2 per SVM per node).
    • Avoid zoning all NVMe LIFs from all nodes unless required for redundancy.
    • If additional LIFs are required for load balancing, create additional SVMs (each SVM supports 2 NVMe LIFs per node).
  • Note:NVMe performance is not dependent on path count. It uses a queue‑pair model for parallelism, allowing high IOPS with minimal paths, unlike SCSI/FC which may require multiple paths for performance.

Additional Information

Your Premium trial has endedYour Premium trial has endedYour Premium trial has ended

Your Premium trial has ended

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.