For data LIFs used for NVMe over FC workloads, how are addresses assigned?

For data LIFs used for NVMe over FC workloads, how are addresses assigned?

• A. Manually configured WWNNs
• B. Automatically assigned iSCSI IQNs
• C. Manually assigned IP addresses
• D. Automatically assigned WWPNs

Answer: (D)

NVMe over Fabrics when used over Fibre Channel relies on FC port addressing. Each data LIF that handles NVMeoF FC traffic needs its own Fibre Channel port address, which is a WWPN. The system automatically assigns these WWPNs to the data LIFs so every path has a unique and fabric-recognized identifier, enabling proper login, zoning, and routing on the FC fabric. WWPNs are the correct kind of address for FC-based NVMeoF; WWNNs identify an entire node and aren’t used per-LIF, IQNs are for iSCSI, and IP addresses apply to IP-based protocols (such as NVMe over TCP or iSCSI over IP). Thus, the data LIFs for NVMeoF FC get automatically assigned WWPNs.

NVMe over Fabrics when used over Fibre Channel relies on FC port addressing. Each data LIF that handles NVMeoF FC traffic needs its own Fibre Channel port address, which is a WWPN. The system automatically assigns these WWPNs to the data LIFs so every path has a unique and fabric-recognized identifier, enabling proper login, zoning, and routing on the FC fabric. WWPNs are the correct kind of address for FC-based NVMeoF; WWNNs identify an entire node and aren’t used per-LIF, IQNs are for iSCSI, and IP addresses apply to IP-based protocols (such as NVMe over TCP or iSCSI over IP). Thus, the data LIFs for NVMeoF FC get automatically assigned WWPNs.