Which statement is true about mapping an NVMe namespace for host access in ONTAP?

Which statement is true about mapping an NVMe namespace for host access in ONTAP?

• A. The NVMe namespace must be mapped to an NVMe subsystem that includes the host's NQN.
• B. The host must be added to the same igroup as LUNs.
• C. The namespace must be formatted with a file system.
• D. The namespace must have a matching WWPN.

Answer: (A)

In NVMe over Fabrics, access to a namespace is controlled by the NVMe subsystem. The host must be included in that subsystem by having its NVMe namespace’s host identifier (the NQN) registered with the subsystem. When the namespace is mapped to a subsystem that already includes the host’s NQN, the host can see and access the namespace. This is why the statement about mapping the NVMe namespace to an NVMe subsystem that includes the host’s NQN is correct. The other ideas don’t apply here: NVMe-oF access isn’t governed by iGroups like FC/Iscsi LUNs, so the host doesn’t need to be in an igroup for NVMe namespaces. A namespace isn’t required to be formatted with a filesystem at the moment of mapping; it’s a raw block device until the host formats it. And WWPNs are relevant to Fibre Channel, not NVMe over Fabrics, so a matching WWPN isn’t part of NVMe namespace mapping.

In NVMe over Fabrics, access to a namespace is controlled by the NVMe subsystem. The host must be included in that subsystem by having its NVMe namespace’s host identifier (the NQN) registered with the subsystem. When the namespace is mapped to a subsystem that already includes the host’s NQN, the host can see and access the namespace. This is why the statement about mapping the NVMe namespace to an NVMe subsystem that includes the host’s NQN is correct.

The other ideas don’t apply here: NVMe-oF access isn’t governed by iGroups like FC/Iscsi LUNs, so the host doesn’t need to be in an igroup for NVMe namespaces. A namespace isn’t required to be formatted with a filesystem at the moment of mapping; it’s a raw block device until the host formats it. And WWPNs are relevant to Fibre Channel, not NVMe over Fabrics, so a matching WWPN isn’t part of NVMe namespace mapping.