Multiple Namespace Detection in Windows NVMe Over TCP Initiator

We are evaluating the Windows NVMe Initiator and have observed an issue with namespace handling.

Our NVMe subsystem contains multiple namespaces. When we connect to the subsystem over TCP and establish connections to all namespaces, they are all shown as connected under the controller. However, only one namespace (shared block device) is exposed and accessible within Windows.

Based on our testing, it appears that the initiator may be mapping only the first namespace associated with a given Friendly Name. We were able to connect another subsystem, whose friendly name was different.

Questions:

• Is support for multiple namespaces within a single subsystem currently available in the Windows NVMe Initiator?

•  

  If so, are there any configuration requirements or known limitations related to namespace discovery and mapping?

•  

  Is the initiator expected to expose all connected namespaces as separate disks within Windows?

We would appreciate any guidance or clarification on the expected behavior.